Hmm, sorry for not being clear, you are not supposed to type the "#". I use this as a prompt indicator for being root. I've updated the commands in the post above.
your meteohub screenshot telling an
IP: 192.168.1.68
but your router config screen says you assigned
IP: 192.68.1.69
for the meteohub
What now?
What is the IP config of the router. Does it have an IP: 192.168.1.254 ??
And if so,
what does a ping 192.168.1.254
on the meteohub console show or bring up?
Or in other words.
Basic troubleshooting:
ping loopback ping 127.0.0.1
ping own IP-Address ping 192.168.1.68
ping gateway ping 192.168.1.254
ping external WAN-Address ping ...
ping external DNS-Server ping ...
the last two IP-Addresses you should get from your router.
DSL or PPPoE info ...
Last edited by wfpost on Thu Feb 03, 2011 12:36 am, edited 2 times in total.
if you ping the external WAN and DNS from a PC of your network.
Does this work okay?
(in theory ping replies could be blocked at the WAN and DNS Server)
Just as a test: Can you setup your meteohub to use DHCP, to see if this is working?
As it looks right now, I tend to believe that there is a DNS issue.
Since you cazn post messages, I guess your PC is working fine. What is the DNS server that your PC is using, can you list the output of the following command:
On windows open a DOS box:
Start - Run - cmd - <enter>
ipconfig /all
I think, it´s not DNS-, but a router issue.
Although, if DNS is not working, meteohub wouldn´t find out the external WAN-IP.
Nevertheless the internet connection should work, because all IP-traffic is routed to the gateway address and your router then anyway must route those packets towards the WAN-LINK.
As the local pings work, I tend to say meteohub networking stack is okay.
Local gateway is reachable, but external WAN not respondinbg looks to me like the external traffic for meteohubs IP is somewhat broken or blocked.
Is the Firewall of the Router enabled? If so, could you disable it temporarily.
Normally only incoming packets are blocked depending on the firewall rules.
But maybe outcoming traffic is blocked somewhere with your firewall config.