Hub falsely reporting no IP connection

[paulecrisp]

When logging on to the management interface of my Meteohub installation, the summary page includes the message "WAN IP: no internet access". I don't know what this means. It doesn't mean that the device is inaccessible as I can log on both locally and 'remotely'.

There is something wrong however, because the Meteohub has stopped updating my meteoplug account. Meteoplug reports no data received since 09/10/12 though the 'instruments' page seems to be reporting values

I have tried rebooting the Sheevaplug host and powercycling the router with no improvement. Any suggestions?

Paul

[admin]

Meteohub does define a timout when trying to detect the WAN IP. So when you get no WAN connection it is not there,
or Meteohub gave up on waiting.

[Holsteinson]

I have 2 SheevaPlug in different locations that were working ok but internet was disconnected for a week due to a flooding and now there is internet again but there is no way to access via browser to the Sheevaplugs or see them with IP scanner over the network.

I tried unplugging the network cable and reconnecting, then I tried a unplugging from AC the sheevaplug waited 5 minutes and reconnected but nothing.

What can I do to regain these sheevaplug connection to the network?

[Holsteinson]

I used a new Meteohub SD card from a new Sheevaplug and put it into one of the non communicating to the network Sheevaplug and it worked great so it seems that there is a kind of Meteohub software bug that has locked the response to the network, how can I reset it?

[Holsteinson]

NEED HELP PLEASE with this problem!!

[wvdkuil]

NEED HELP PLEASE with this problem!!

There is another ip address which is always usable. The emergency address 192.168.1.77
Did you try to connect to meteohub using the emergency address by typing 192.168.1.77 into your browser?

This is from the documentation:

Start Meteohub

You can now reach the Meteohub system by your desktop's/laptop's browser at the emergency IP 192.168.1.77 ("http://192.168.1.77") and if you have a DHCP server in your LAN you also can find your Meteohub at the address given by the DHCP server. User name is "meteohub", password is "meteohub". To reach the emergency IP with your browser you probably have to do reconfigure the IP address of your desktop/laptop as described in #Setup of unmodified NSLU2 in your LAN (explains how to bring you desktop into the same subnet as Meteohub). Having reached the Meteohub web interface you can set the IP persistently.

Success Wim

[bsedor]

I am experiencing the same issue. The emergency IP doesn't work and when I acan my network the Meteohub does not show up?

Any suggestions?

Bob

[wvdkuil]

I am experiencing the same issue. The emergency IP doesn't work and when I acan my network the Meteohub does not show up?
Any suggestions?
Bob

These "unreachable" Meteohub situations arise from new modems / routers were the Meteohub is still on the "old" adress range. You use the emergency 192.168.1.77 address to reset the Meteohub to go in DHCP mode again.

B U T: The emergency IP is ONLY accesible when your PC has a static IP adress in the same range for instance 192.168.1.2 as the emergency address.

You have to set that first in your PC or Mac before trying to connect to the Meteohubs emergency IP address.

After you have set your PC to that static address you "created" a small extra network on top of your normal network.
This network consists of two devices, the Meteohub on 192.168.1.77 and your PC.
When you now scan the network for devices in the 192.168.1 range it will show the two devices in it.
You can reach the Meteohub using your browser and reset the Meteohub normal IP adress. You have to restart your Meteohub and it will then show up on your normal DHCP network.

You can reset your PC to get normal IP adresses via DHCP again.

It always works this way, Wim

[wvdkuil]

Today I found another reason for not finding the Meteohub.

I have two SSID's on my router which, according to the router settings, are 1 integrated network.
When I scan the network all devices either directly cable-connected or connected to one of the WLAN-SSID's are visible.

But not if it is a Meteohub device.

That one is ONLY visible if the scan is done on the same SSID as the Meteohub is on.
For one historical reason or another one Meteohub was connected to the least used SSID and I could not see its IP-address today or connect to it using SMB or the browser. And it was uploading its data correctly, so it was operational.

When I switched my Mac to the other SSID the Meteohub was found by the scanner immidiatly AND could be connected to.

Wim

[Holsteinson]

I tried the emergency IP and NOTHING, need these 2 stations urgently online again help

[Holsteinson]

I am experiencing the same issue. The emergency IP doesn't work and when I acan my network the Meteohub does not show up?
Any suggestions?
Bob

These "unreachable" Meteohub situations arise from new modems / routers were the Meteohub is still on the "old" adress range. You use the emergency 192.168.1.77 address to reset the Meteohub to go in DHCP mode again.

B U T: The emergency IP is ONLY accesible when your PC has a static IP adress in the same range for instance 192.168.1.2 as the emergency address.

You have to set that first in your PC or Mac before trying to connect to the Meteohubs emergency IP address.

After you have set your PC to that static address you "created" a small extra network on top of your normal network.
This network consists of two devices, the Meteohub on 192.168.1.77 and your PC.
When you now scan the network for devices in the 192.168.1 range it will show the two devices in it.
You can reach the Meteohub using your browser and reset the Meteohub normal IP adress. You have to restart your Meteohub and it will then show up on your normal DHCP network.

You can reset your PC to get normal IP adresses via DHCP again."

I TRIED everything on the manual including the emergency IP with my network as indicated and even did an IP Scanner and there Sheeva is not shown, listed or accessed No I have 4 SHEEVA that were working ok for 1 or more years, that I have access through the web browser and updated several times the METEOHUB software and now they are not available with the emergency IP nor are they reporting in weather networks as they were doing for ovrer a 1 year This is obviously a major bug in Meteohub or SHEEVA server, 4 units can not stop working in the same way ??

[admin]

When I update my SheevaPlug with latest Meteohub version 4.9y it works fine.

This is a strong indication that the problem is somewhere in your network setup
and when the Meteohubs do reboot as a side effect of the update these network
problems in your LAN become obvious.
Are the Meteohubs set to DHCP or are you using static IPs?
Which IPs do they signal by LED blinking?
When you are using WiFi, step back to LAN to check correct setting of SSID etc.

[wvdkuil]

. . . 4 units can not stop working in the same way ??
[/b][/size]

Oh yes, they can, have done and will do in the future.
And if it was only ONE device which was missing, I would have thought "maybe the hardware failed".
But at your site there are 4 devices missing. All after a flooding/ network failure.

They are probably still working fine.
They can not access the internet as there network settings are incorrect.
The main reason for "not reacheble" units is that your PC and the units you can not "'see" are in different logical networks. They all should be moved to the same logical network.
Example 1
192.168.0.x with a netmask of 255.255.255.0
All normal network devices which for which the IP-address starts with 192.168.0 and have the netmask set to 255.255.255.0 will "see" each other. All other devices will not show up in a scan or in your network envirionment on your PC.
So if your PC is set to 192.168.0.100 with a mask of 255.255.255.0
and a "missing' device is set to an IP of 192.168.0.101 but with a different netmask of 255.255.255.128
they will be undetectable for each other.

If all devices in your network are using the same DHCP server which hands out dynamic IP-addresses in the same range with the same netmask, all devices will see each other.

You told

. . . disconnected for a week due to a flooding and now there is internet again

Probably the network-adressing settings before and after the flooding are not using the same numbering / netmask scheme.
Probably the missing devices are set to the pre-flooding network adress-range/netmask with a FIXED ip-address.
And by design devices with different "logical" addresses although on the same "phisical" network, can not and will not see each other.

So please start from scratch.
Connect your PC and ONE Sheeva plug to a stand-alone network hub/switch separate from your normal network.
Your network then only consists of your PC and the Sheeva plug.
NO other devices should be connected, just to eliminate other causes of this strange behaviour.
And especially no multiple Sheeva plugs at the same moment. They will all try to use the .77 emergency address which will let them all fail.

Take your PC and switch from DHCP addressing to fixed IP and set the IP-address/netmask to 192.168.1.100 / 255.255.255.0
Start your browser and type 192.168.1.77
Now the Meteohub should show up. Always does, always done in the past.

Reset the Meteohub to DHCP, SAVE the new settings, and reconnect the network cable to the complete network.
After rebooting that device will show up within your normal network.

Repeat these steps for every other "unreachable" meteohub devices.

Succes, Wim

[Holsteinson]

Thanks for the detailed step by step connection setup and testing Tried it but still no connection with the Sheevaplug with Meteohub. simply doesnt recognize them

[wvdkuil]

Thanks for the detailed step by step connection setup and testing Tried it but still no connection with the Sheevaplug with Meteohub. simply doesnt recognize them

Two points are essential:

Use a cabled network, NO wifi.
So also the laptop used should have its wifi switched of and using a lan cable!

Do not attach anything else to the network hub,
Only 1 sheeva plug and 1 computer and a power cable should be attached to the hub.

You should
1. set the ip address of the laptop/computer to 192.168.1.1 as described above,
Now you can not acces anything on the laptop. No internet whatsoever.
If you can browse or mail, the laptop is still connected to another network.

2. run a network scanner to see any devices on that local network 192.168.1.???
There should be only two devices displayed, the laptop at 192.168.1.1 and another device.

Wim