This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
technical_logs:east_side_marios [2010/11/03 21:19] gabe |
technical_logs:east_side_marios [2013/09/28 16:06] (current) |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== February 6, 2011 ====== | ||
+ | Wifidog reported that the node's been down for a while. Only 127.0.0.1 was in /etc/resolv.conf, so I did what the instructions below said and it started working. <shrug> | ||
+ | |||
====== November 3, 2010 ====== | ====== November 3, 2010 ====== | ||
Wifidog reported that the node is down. I was able to ping it via OpenVPN ('ping 192.168.222.77' from the auth server), so I sshed in (ssh root@192.168.222.77' from the auth server), and ran 'wdctl status'. It took a long time to run, and came back saying that the wifidog gateway doesn't have Internet connectivity. When I've seen this in the past, it's been because the router doesn't have a valid DNS server. Indeed, 'ping yahoo.com' returned nothing, but 'ping 4.2.2.2' did. So I forced it to use the opendns servers, by:<code> | Wifidog reported that the node is down. I was able to ping it via OpenVPN ('ping 192.168.222.77' from the auth server), so I sshed in (ssh root@192.168.222.77' from the auth server), and ran 'wdctl status'. It took a long time to run, and came back saying that the wifidog gateway doesn't have Internet connectivity. When I've seen this in the past, it's been because the router doesn't have a valid DNS server. Indeed, 'ping yahoo.com' returned nothing, but 'ping 4.2.2.2' did. So I forced it to use the opendns servers, by:<code> |