This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
technical_logs:the_3_brewers [2010/03/23 13:43] gabe |
technical_logs:the_3_brewers [2011/03/26 12:47] gabe |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== March 26, 2011 ====== | ||
+ | Same thing again. I edited /etc/init.d/S50dnsmasq and changed the line that read "nameserver 127.0.0.1" to "nameserver 208.67.222.222" and then added another line below it, "nameserver 208.67.220.220". (Those are opendns servers.) I then edited /etc/resolv.conf with those same two lines, and it started working right away. | ||
+ | |||
+ | ====== December 3, 2010 ====== | ||
+ | Exactly the same issue as March 23. lan_dns was set correctly, but only 127.0.0.1 was listed in resolv.conf. I added the others, and it started working right away. | ||
+ | |||
====== March 23, 2010 ====== | ====== March 23, 2010 ====== | ||
Wifidog reported the router down. I was able to SSH in over OpenVPN. Looks like it simply wasn't resolving DNS (a problem I've seen several times now on various hotspots in the past few months). I manually added DNS servers to /etc/resolv.conf and nvram lan_dns, and it started working right away. | Wifidog reported the router down. I was able to SSH in over OpenVPN. Looks like it simply wasn't resolving DNS (a problem I've seen several times now on various hotspots in the past few months). I manually added DNS servers to /etc/resolv.conf and nvram lan_dns, and it started working right away. |