User Tools

Site Tools


technical_logs:st._louis_bar_grill

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

technical_logs:st._louis_bar_grill [2011/07/20 08:23]
gabe
technical_logs:st._louis_bar_grill [2013/09/28 16:06]
Line 1: Line 1:
-====== July 20, 2011 ====== 
-Wifidog reported the node down, but I was able to connect to it through the VPN. Wifidog was running, but DNS wasn't resolving. 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. 
  
-====== 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 ====== 
-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. 
- 
-====== August 21, 2007 ====== 
-Installed by Gabe.  Channel 1.  It's in the office. ​ WAN port of the wireless router is plugged into a D-Link wired router which is in turn plugged into their 'net connection. 
technical_logs/st._louis_bar_grill.txt · Last modified: 2013/09/28 16:06 (external edit)