SOLVED!!!! iConnect - NO WEB INTERFACE - CLOSED ALL PORTS

[kupe]

Hello,


I would lite to try meteohub SW, but my problem is:

-i insltalled meteohub SW
-power LED start flashing, after a while the LED turn off,
-IP is given by DHCP server + 192.168.1.77 - works fine (it is signal, that meteohub is booted up ?)

PROBLEM
-no http port is open, only port 111

Nmap scan report for 192.168.1.100
Host is up (0.00014s latency).
Not shown: 999 closed ports
PORT STATE SERVICE
111/tcp open rpcbind
MAC Address: 00:D0:B8:XX:XX:XX (Iomega)

Starting Nmap 5.21 ( http://nmap.org ) at 2012-06-24 09:47 CEST
Nmap scan report for 192.168.1.77
Host is up (0.00015s latency).
Not shown: 999 closed ports
PORT STATE SERVICE
111/tcp open rpcbind
MAC Address: 00:D0:B8:XX:XX:XX (Iomega)

and therefor I couldnt connect to my meteohub.


How to log into iConnect meteohub ?
How to "open" port 80-http web interface?
What can I do now ?


Please, any idea?


Please, help me to resolve this problem.


thank you very much !

[wfpost]

try this :

http://192.168.1.77:7777

also by default meteohub is trying to get its first IP from a DHCP server.
So your router should have a meteohub client in its DHCP client list.
With this IP port 80 as normal http port ist open ...

BTW: reading the manual is not prohibited

[kupe]

I scanned IP of my iconnect, but there was only one open port - 111. Any other (including 7777) was not opened.

On my DHCP server i have defined static IP-MAC association (to 192.168.1.100) and it works. I can find the device, but I am not able to find interface.

It is my first "meteohub" adventure.



Thank you for any tips.



Peter

[kupe]

After reinstallation of meteohub are every ports CLOSED !

but the devices is able to ping only



PING 147.232.190.116 (147.232.190.116) 56(84) bytes of data.
64 bytes from 147.232.190.116: icmp_req=1 ttl=64 time=0.158 ms
64 bytes from 147.232.190.116: icmp_req=2 ttl=64 time=0.132 ms
64 bytes from 147.232.190.116: icmp_req=3 ttl=64 time=0.132 ms
64 bytes from 147.232.190.116: icmp_req=4 ttl=64 time=0.132 ms
64 bytes from 147.232.190.116: icmp_req=5 ttl=64 time=0.130 ms




nmap 147.232.190.116

Starting Nmap 5.21 ( http://nmap.org ) at 2012-06-24 12:44 CEST
Nmap scan report for omega.bozenka.tuke.sk (147.232.190.116)
Host is up (0.00016s latency).
All 1000 scanned ports on ethernet-hdd.bozenka.tuke.sk (147.232.190.116) are closed
MAC Address: 00:D0:B8:XX:XX:XX (Iomega)

Nmap done: 1 IP address (1 host up) scanned in 0.27 seconds



i try to change IP to main server (public IP) - no change. no open port on private IP (192...) either no open port on public IP ...





heeeeeeeellllllllllllppppppppppppppp please


Thank you

PS: something very interesting

[wfpost]

are you sure your installation was done correctly?
I do not have an iConnect, but are you sure you correctly wrote the installlation image file to your disc?

[kupe]

I have made an image of the image file ...

under linux

iConnect
Iomega iConnect needs a specially prepared USB stick to patch the iConnect with and to be used as system and data volume for Meteohub operation later on.
compressed USB stick image (Version 4.9)
http://www.meteohub.de/files/mhiconnect-stick-v4.9.rar

by direction at:
http://wiki.meteohub.de/Setup_iConnect

image make by: dd if=mhiconnect-stick-v4.9.img of=/dev/sdb bs=1M
(sdb is my USB flash drive)

after writing to USB... reset + red light + boot from usb...

all blue led near USB ports on iconnect turn on, then turn off, device reboot...

device pings successfully

but no web...


is necessary other (the second one) usb with other software? (is this - upper describeed enough ??? )



thank you

[wvdkuil]

192.168.1.77 is an always accessibele adres for Meteohub so it is NOT given out by your routers DHCP.
But what is the ip adress of your PC?
Does it also starts with 192.168.1.? If not you are on a different subnet and then it is quit difficult to acces the Meteohub.

[kupe]

Hi wvdkuil ,

network setup is OK and working. All devices are in 192.168.1.0/24 subnet. There is not problem.

I think, that the problem is in iConnect device - or in my bad installation process. However device boots successfully, and answer ping reply OK. I try this pirst time and there is a problem - lox experience in meteohub and iConnect.



thank you for your tip



Please other one ?

[wvdkuil]

network setup is OK and working. All devices are in 192.168.1.0/24 subnet. There is not problem.

The ping you showed earlier had another adress range 147.232.190.116?
Did you succesfully ping at 192.168.1.77?

Is there a DHCP adress given by your router or DHCP server?
192.168.1.77 is the extra adress Meteohub uses always so it is not a DHCP adress.

Maybe there is an IP adress conflict.
So disconnect Meteohub and scan again for 192.168.1.77. If it is found there are to devices using this adress.

Keep up the spirit, we will try to help.

[kupe]

I am sorry,

I didnt tell to everybody some issue... IP addressing is correct. i tied many variants. I work as an IT junior admin and therefore are some variants of IP ... i try many variants of IP, private/public... there (in IP and configuring of netvork) is not mistake...


i try to set up IP of my PC 192.168.1.5 ... to connect to iConnect 192.168.1.77 byt nothing ...only ping reply...


After boot, vhen ping reply are successfull received ... still BLUE POWER LED is off - it is very interesting. something is wrong. meteohub system is probably booted, because IP 192.168.1.77 is alive - pings, but no web interface

[wvdkuil]

1. Multiple units using same IP?
Did you disconnect the iConnect and than ping for 192.168.1.77?
That should fail. If you get a reply there is another device using that adress.
Also:
Try to connect only one pc and the iconnect (cross over cable or small unintelligent stand alone switch).
Give PC an adress in the same 192.168.1.x range and try to communicate.

2. DHCP ?
What is your DHCP server telling you.
Is there a dynamic adress given to the mac-adress of the iConnect box?

3. Read the Blinks
Try this: (from the manual!)

When boot is going to finish the power LED turns into steady blue. After a while (a minute or so) the power LED goes off and starts a LED blink sequence, that signals the IP of the Meteohub. When signaling is finished, power LED changes to steady blue again.
The IP consists of four numbers in the range of 0 to 255 separated by dots. Meteohub signals each of the four numbers by sending for each digit a seqence of short red blinks, where the number of blinks in the sequence represents the digit (1 = one blink, ..., 0 = ten blinks). Dots between numbers are represented by a blue blink. The example below explains how blinking for IP 192.168.0.23 would look like. Meaning of symbols is
"_" stands for power LED off
"R" stands for power LED red
"B" stands for power LED blue

Sequence for 192.168.0.23 will look like this:
192. ___R___R_R_R_R_R_R_R_R_R___R_R___B
168. ___R___R_R_R_R_R_R___R_R_R_R_R_R_R_R___B
0. ___R_R_R_R_R_R_R_R_R_R___B
23 ___R_R___R_R_R

So maybe you can find another ipadress. At least is should blink the 192.168.1.77 adress. If not: Meteohub is not installed.

4. Is the box broken?
Did you connect the iConnect to your network and tested it before you tried to install Meteohub? It could be broken.
From the manual:
Revert to a regular iConnect
When you decompress this mage and put it via ImageWriter onto an USB stick and follow procedure as lined out in paragraph "Patch the iConnect", you will revert your Meteohub iConnect system into a regular iConnect again.

[wfpost]

it is very interesting. something is wrong. meteohub system is probably booted, because IP 192.168.1.77 is alive - pings, but no web interface

not necessarily, because with this headless units you can´t really say what´s going on.

Could it be that iConnect is also using the 192.168.1.77 as its default IP as the old NSLU2?

From what I understand the iConnect stays in its default configuration if it is not properly patched like the old NSLU2.
Could it be that you did not properly press the reset button long enough during boot time??

Locate the reset pin hole at the rear of the iConnect. Take a paper clip and bend it open, as it will be used to press reset button behind pin hole at the rear. Insert paper clip end into the reset pin hole and press slightly. You should feel a soft "click" indicating that you hit and pressed the reset button behind the hole.
Keep the reset button pressed while connecting the power cord to the iConnect again. Keep the reset button pressed until blue flashing power LED changes to red. This will take about 15 seconds. Red power LED indicates iConnect has been successfully booted into "update mode".

[kupe]

Thank you for you post.

I pressed eneugh long - i wait for turning led on - red light. after that i release reset button and "installation processs" starts. after that all led over all USB turn on, turn off - reboot, and IP 192.168.1.77 starts working. pinging.

nothing else.

and therefore i said, that the installation is ok... (?) not sure.

[kupe]

PROBLEM SOLVED:

everything was OK, but I dont have any 4GB USB stick and therefore I try it with 1 GB and with 8 GB. there was an problem.

Finally i try to use SUSE image writer studio to make iConnect "boot" image.


it works, but nothing EXTRA. better choice is te923 from http://te923.fukz.org/ (but is difficult to compile it on iConnect)

[wfpost]

ha ha , guess who recommended the suse image writer

I don´t think te923 is the better choice and meteohub is far more powerful, but to each his own