Node name: NodeLuckLabSW
Live Date: August 2007
Sponsor: Gary Geist
Contact: RussellSenior <russell AT personaltelco DOT net>
7675 SW Capitol Hwy
Portland, OR 97219
(503) 244-2537
http://www.luckylab.com/html/story.html
Network Configuration
- spot
- Device: tplink,tl-wdr3600-16m
OpenWrt: r28012+1-31f1dabb4b97
- IPv4: 10.11.11.193/26
- wlan0
- SSID: "www.personaltelco.net"
BSSID: F4:F2:6D:48:AC:BD
- Channel: 1
- wlan1
- SSID: "www.personaltelco.net"
BSSID: F4:F2:6D:48:AC:BE
- Channel: 40
- wlan2
- SSID: "www.personaltelco.net/ap0"
BSSID: F6:F2:6D:48:AC:BD
- Channel: 1
- wlan3
- SSID: "www.personaltelco.net/ap0"
BSSID: F6:F2:6D:48:AC:BE
- Channel: 40
- ap1
- Device: meraki,mr24
OpenWrt: r26162-6bb2551343
- IPv4: 10.11.11.194/26
- wlan0
- SSID: "www.personaltelco.net"
- BSSID: 00:02:6F:E6:56:0C
- Channel: 1
- wlan1
- SSID: "www.personaltelco.net"
- BSSID: 00:02:6F:E6:50:28
- Channel: 40
- wlan2
- SSID: "www.personaltelco.net/ap1"
- BSSID: 02:02:6F:E6:56:0C
- Channel: 1
- wlan3
- SSID: "www.personaltelco.net/ap1"
- BSSID: 02:02:6F:E6:50:28
- Channel: 40
- ap2
- Device: meraki,mr24
OpenWrt: r26162-6bb2551343
- IPv4: 10.11.11.195/26
- wlan0
- SSID: "www.personaltelco.net"
BSSID: 88:DC:96:0A:9A:91
- Channel: 6
- wlan1
- SSID: "www.personaltelco.net"
BSSID: 88:DC:96:0A:AE:9F
- Channel: 48
- wlan2
- SSID: "www.personaltelco.net/ap2"
BSSID: 8A:DC:96:0A:9A:91
- Channel: 6
- wlan3
- SSID: "www.personaltelco.net/ap2"
BSSID: 8A:DC:96:0A:AE:9F
- Channel: 48
Installers / Organizers
Maintenance and System Log
2007-12-04: checking out an outage (discovered from the wifidog authserver status page), discovered the isp had apparently changed to integra (i think it was qwest.net before). Updating information. --RussellSenior
- 2007-12-07: installed a router to isolate luckylab's internal network, removed the iptables rules from /etc/init.d/firewall that we used to try to protect them, since they are now redundant. also renumbered our device to 192.168.1.3 and had integra install a port forward to spot.
2008-04-01: checked out an outage (discovered from the wifidog authserver status page), found radio on but dhcp was not working. power cycled and it came back up. also called and requested the tcp port 22 forward to 192.168.1.3 again, i'd had trouble previously. --RussellSenior
2008-08-13: Just fixed up the LuckyLab network for safety and plugged our access point back in after a two week outage. Seems to be working, will watch.
2008-12-09: Was asked to come fix their internal network again. Turns out (I think) to be a problem with multiple DHCP servers and gateways on their Point-of-Sale system network. Separated the internal lan from the POS network and it was working. We were seeing some packet loss through the Linksys router we'd installed for the internal network. Things plugged back in and working when I left. --RussellSenior
2009-07-21: Got a complaint about wifidog at this node today. Took the opportunity to bring the family out for pizza and drop in a WgtCab. --RussellSenior
2009-09-16: During WeeklyMeeting20090916, noted problem seen elsewhere on Integra services, the "dumb" DHCP server on the Zhone/Paradyne DSL modem (when nat'ing) hands out addresses starting at .2. When some devices are configured with low-numbered static addresses and others are dynamic, this eventually causes a difficulty where addresses clash. Discovered that this was another such case. Called Integra and had them modify the DHCP range for the DSL modem to 192.168.1.32 through .240, which should provide ample buffer for likely chosen static addresses. Our device here is at 192.168.1.3. --RussellSenior
2012-11-22: Updated firmware to r34240. Also, the DHCP configuration has changed, we are the DMZ host, at 192.168.1.101 or something (with a fixed DCHP assignment). There have been outages recently, which Erin reports are only cured by rebooting the modem and their routers. It appears that the speed is flapping, from 256kbps to 1780kbps or so. That may be the source of their trouble. --RussellSenior