I've been using that for several days. I even had a two browser pages (one the Meteohub interface, the other a cgi/html page) open with that IP. When I tried to Refresh I got \"Problem Loading Page\".
Running ipscan.exe revealed that the IP had changed to 192.168.0.101!
192.168.0.101 is in my DHCP range.
On the \"Settings\" page the DHCP option is not ticked - I have double checked.
Looking in the system log I found:
Code: Select all
Mar 12 17:45:11 (none) local0.debug udhcpc[1310]: Sending renew...
Mar 12 17:45:27 (none) local0.info udhcpc[1310]: Lease lost, entering init state
Mar 12 17:45:27 (none) local0.debug udhcpc[1310]: Sending discover...
Mar 12 17:45:27 (none) local0.debug udhcpc[1310]: Sending select for 192.168.0.101...
Mar 12 17:45:27 (none) local0.info udhcpc[1310]: Lease of 192.168.0.101 obtained, lease time 259200
PS. Another odd thing is that I changed (i.e. manuall restored) the workgroup name in meteohub after the update and restore - but to the Windows network it is still appearing as being in workgroup HOME.
