technical_logs:st._louis_bar_grill
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
technical_logs:st._louis_bar_grill [2009/11/29 15:52] gabe |
technical_logs:st._louis_bar_grill [2010/02/20 12:55] gabe |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== February 20, 2010 ====== | ||
| + | Exactly the same problem as Nov 29 2009. The DNS servers were still in the lan_dns value in nvram, but weren't in the /etc/resolv.conf. I added them, and the router was then able to resolve DNS addresses. | ||
| + | |||
| ====== November 29, 2009 ====== | ====== November 29, 2009 ====== | ||
| Wifidog reported that it went down 3 days ago. I connected via VPN. Wifidog was still running ('wdctl status'), but was reporting that it couldn't connect to the auth server. I tried pinging the auth server ('ping auth.wirelesstoronto.ca') and it couldn't resolve the address. I changed the DNS server in both /etc/resolv.conf ('vi /etc/resolv.conf') and in the router config ('nvram set lan_dns='4.2.2.2 128.100.100.128') and it started working. | Wifidog reported that it went down 3 days ago. I connected via VPN. Wifidog was still running ('wdctl status'), but was reporting that it couldn't connect to the auth server. I tried pinging the auth server ('ping auth.wirelesstoronto.ca') and it couldn't resolve the address. I changed the DNS server in both /etc/resolv.conf ('vi /etc/resolv.conf') and in the router config ('nvram set lan_dns='4.2.2.2 128.100.100.128') and it started working. | ||
technical_logs/st._louis_bar_grill.txt ยท Last modified: 2013/09/28 16:06 (external edit)
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 3.0 Unported
