Nano not reachable some time after (re)boot **solved**

This section covers the Meteobridge PRO, PRO2, NANO SD, Raspberry Pi and VM platforms exclusively

Moderator: Mattk

Post Reply
wouterk
Junior Boarder
Junior Boarder
Posts: 20
Joined: Sun Oct 17, 2010 9:30 am

Nano not reachable some time after (re)boot **solved**

Post by wouterk »

Hi,

Recently I noticed a ping to my nano did not work and also the web interface was not accessible. Still it seemed to work.
After a reboot a ping worked again and I could access the web interface.
But after a period of time, seems within an hour, a ping does not work and the web interface is not accessible anymore.

Did not change any of the configuration of the nano.Multiple reboots did not work.
The nano is running FW 5.2

Anyone an idea how to solve this?

Thank you.
Last edited by wouterk on Tue Nov 30, 2021 8:02 am, edited 1 time in total.
Mattk
Platinum Boarder
Platinum Boarder
Posts: 1387
Joined: Mon Sep 22, 2014 3:24 am

Re: Nano not reachable some time after (re)boot

Post by Mattk »

Are you trying to access the NANO from the initial WiFi setup IP? 192.168.169.1
wouterk
Junior Boarder
Junior Boarder
Posts: 20
Joined: Sun Oct 17, 2010 9:30 am

Re: Nano not reachable some time after (re)boot

Post by wouterk »

No, after a reboot it is accessible with the configured IP address it gets from the dhcp reservation.
Mattk
Platinum Boarder
Platinum Boarder
Posts: 1387
Joined: Mon Sep 22, 2014 3:24 am

Re: Nano not reachable some time after (re)boot

Post by Mattk »

Ok then, have you tried configuring a static IP?
wouterk
Junior Boarder
Junior Boarder
Posts: 20
Joined: Sun Oct 17, 2010 9:30 am

Re: Nano not reachable some time after (re)boot

Post by wouterk »

Happy to do so but I can see that it is still active on that ipaddress.
Attachments
Screenshot 2021-11-28 at 11.16.40.png
Screenshot 2021-11-28 at 11.16.40.png (33.95 KiB) Viewed 1430 times
wouterk
Junior Boarder
Junior Boarder
Posts: 20
Joined: Sun Oct 17, 2010 9:30 am

Re: Nano not reachable some time after (re)boot

Post by wouterk »

An hour ago I made the ipaddress static but now I can not reach it by its web interface.
On a ping I get no answer.
Seems that it happens after 30 mins.
Mattk
Platinum Boarder
Platinum Boarder
Posts: 1387
Joined: Mon Sep 22, 2014 3:24 am

Re: Nano not reachable some time after (re)boot

Post by Mattk »

All I can do is suggest "things" as this does appear a local issue to your Nano and network.

This shutdown within 30 minutes stuff tends to maybe have hallmarks of something to do with the WiFi setup or the Nano's own WiFi network used for initial configuration? The Nano does shut down its own WiFi network after a specific time from boot but I thought it was a bit less than 30 minutes?

So your WiFi signal is good then? Nano within distance of the Router etc?
When you "Saved" the setup config, does the test option indicate the network is ok? Then do a "Save and Apply and Reboot" to make the settings sticky and effective?
wouterk
Junior Boarder
Junior Boarder
Posts: 20
Joined: Sun Oct 17, 2010 9:30 am

Re: Nano not reachable some time after (re)boot

Post by wouterk »

Thanks for your suggestions and help.

Maybe I was not clear in my explanation. It does not shutdown. All the services and uploads and stuff are still working.
Updates to a sql-DB are still getting uploaded; no hiccups.

But the weather34 PWS site on the nano itself is not responding as is it own admin web interface.
Also ping and smb are not working anymore.
Seems that some basic network functions are nog responsive anymore.

Wifi signal is good. Distance is about 5 meters to the access point.
wouterk
Junior Boarder
Junior Boarder
Posts: 20
Joined: Sun Oct 17, 2010 9:30 am

Re: Nano not reachable some time after (re)boot

Post by wouterk »

Using multiple accesspoints I defined a separate SSID for the Nano.
Configured Wifi on the Nano to use that specific SSID and is running now for a little more then two hours in which it stays accessible.
Ping is still working, smb is accessible, admin web interface and PWS page are accessible also.
Hopefully this is it. If it is I am not sure why it occurs now. Nothing changed on the Nano (position or config) or the accessppoints (position or config)
Post Reply