|
← Revision 4 as of 2008-06-23 23:11:40
Size: 1941
Comment:
|
← Revision 5 as of 2008-06-23 23:16:48 →
Size: 1943
Comment: updated the dhcp provided ipaddr
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 33: | Line 33: |
| * Internet IP: 76.27.243.11 (configured by DHCP) | * Internet IP: 76.105.159.165 (configured by DHCP) |
| Line 39: | Line 39: |
| * 2008-06-23: responded to an outage report. Cacti graphs imply the outage has been for several months, since the end of February-ish, but that's not certain. It looks as if it was triggered by an upstream dynamic IP address change, which rendered the upstream connection useless for some reason (shouldn't dhclient or equivalent handle that??). The outage when then compounded by /var filling up. The biggest culprit was /var/lib/logcheck/dead-letter, which apparently filled up with undeliverable logs of various services complaining about not having a network or the disk being full or something. Blew the logs away. Then also had a problem with nocatauth getting confused about the local network and guessing it was the openvpn tunnel. I think JasonMcArthur fixed that up and it was back in business. Signal was weak outside, pinged the node hosts about maybe re-evaluating the gear there. --RussellSenior | * 2008-06-23: Responded to an outage report. Cacti graphs imply the outage has been for several months, since the end of February-ish, but that's not certain. It looks as if it was triggered by an upstream dynamic IP address change, which rendered the upstream connection useless for some reason (shouldn't dhclient or equivalent handle that??). The outage when then compounded by /var filling up. The biggest culprit was /var/lib/logcheck/dead-letter, which apparently filled up with undeliverable logs of various services complaining about not having a network or the disk being full or something. Blew the logs away. Then also had a problem with nocatauth getting confused about the local network and guessing it was the openvpn tunnel. I think JasonMcArthur fixed that up and it was back in business. Signal was weak outside, pinged the node hosts about maybe re-evaluating the gear there. --RussellSenior |
Node name: Division 34
Status: Active
Live Date: February 9, 2004
Contact: KeeganQuinn
Hot Pepper Studios
3377 SE Division St # 104
Portland, OR 97202
(503) 230-2058
Equipment
Software
DebianLinux stable
NoCatAuth captive portal
Network Configuration
- ESSID: www.personaltelco.net
- Channel:
- BSSID: 00:0C:41:18:53:B5
- Hostname: lester
- Internet IP: 76.105.159.165 (configured by DHCP)
- PTPnet Network: 10.11.3.129/26
Notes
2008-06-23: Responded to an outage report. Cacti graphs imply the outage has been for several months, since the end of February-ish, but that's not certain. It looks as if it was triggered by an upstream dynamic IP address change, which rendered the upstream connection useless for some reason (shouldn't dhclient or equivalent handle that??). The outage when then compounded by /var filling up. The biggest culprit was /var/lib/logcheck/dead-letter, which apparently filled up with undeliverable logs of various services complaining about not having a network or the disk being full or something. Blew the logs away. Then also had a problem with nocatauth getting confused about the local network and guessing it was the openvpn tunnel. I think JasonMcArthur fixed that up and it was back in business. Signal was weak outside, pinged the node hosts about maybe re-evaluating the gear there. --RussellSenior
History
- By summer 2004, we expect this node to expand it's signal coverage throughout the Division 34 building and across the street to Pix Patisserie.
Fall 2004: coverage throughout Division 34 building. Still working out the connection to Pix. - RossOlson