Resources/Network/272 Capp Planning

From Noisebridge Wiki
< Resources | Network
Revision as of 04:56, 10 February 2026 by Maintenance script (talk | contribs) (Imported from Noisebridge wiki backup)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Noisebridge | About | Visit | 272 | Manual | Contact | Guilds | Stuff | Events | Projects | Meetings | Donate E
Resources | Where to find things | Network | AV | Audio | Library | Servers | Printers | Sustenance E
Network | Network Troubleshooting | Machine Rack | Planning | (Edit)

2024 rebuild[edit]

Goals[edit]

  • Just works ™, hard to break, LAN management. (see 2020 buildout)

Work in progress[edit]

  • Dig into EdgeRouter 4. Extract, replace USB.
    • Put distinguishing external labels on routers. And create pages / sections for them on the wiki.

Past Config[edit]

https://github.com/noisebridge/infrastructure/blob/master/backups/routers/biketrailer.noisebridge.net


Motivating problem[edit]

EdgeRouters seem to have given out, 2, in the downstairs rack. Should provide 1) traffic forwarding as LAN gateway, 2) DHCP leases, 3) local DNS. They seem to be flaky most notably and undeniably in (2) DHCP leases. We should report metrics about client numbers on local dashbaords.

This would also help diagnose if we need to shorten DHCP leases or use a larger subnet, perhaps a /23 instead of just /24, currently 10.21.1.0/24, where 10.20.0.0/24 are statically assigned for permanent NB devices, including wifi infra, and computers installed. Could use 10.21.0.0/22, with 10.21.2.0/23 and 10.21.0.0/23 as the split. DHCP is easy to move. Would be nice to have DHCP client ids on NB LAN infrastructure, and track the MACs, so DNS can dynamically follow. I think this has been working, but it's important to get right in rebuild.


Possible Alternatives[edit]

Netgate makes pfsense appliances at similar pricepoints to EdgeRouter.

Model CPU RAM IMIX VPN HA Metric Export
EdgeRouter 4 4-Core 1 GHz, MIPS64 1 GB DDR3 RAM NA NA VRRP SNMP
Netgate 1100 2-core ARM64 Cortex-A53 @ 1.2 GHz 1 GB DDR4 RAM 472 Mbps 90 Mbps CARP Any exporter client


2020 move buildout[edit]

https://pad.riseup.net/p/nbrack

https://discuss.noisebridge.info/t/272-capp-network-planning/1685/11

09 July 2020 - 272 Capp Rack Planning notes[edit]

NB Rack Philosophy - as simple as possible.

Next Rack Guild meeting to occur 23 July 2020 22:00 PDT

Stuff to do[edit]

  1. Take inventory of what's usable at 2169
    1. APs are very old
    2. Spare EdgeRouter
    3. Pegasus
    4. UPS
  2. Plan laser migration with MonkeyBrains
    1. Where will the new network drop go? This will inform the rack location
  3. Scout 272 Capp for where the phone lines run in. This is likely where Sonic fiber would come in as well.
  4. Install rack and 2nd switch
  5. Run cable for wifi APs, in-wall APs, etc.
  6. Procure needed hardware beyond what can be reused from 2169 (APs, rack cabinate, etc.)
  7. Recruit volunteers to help with the above
  8. Perform laster migration with MonkeyBrains (2169 offline/272 online date)

25 August 2020 - 272 Capp Rack Planning notes[edit]

Stuff to do[edit]

  1. Meet MB to move laser on Sunday 8/30 at 12:00
  2. Permission from LL to drop cable through roof
BOM for build out[edit]
  1. 12U rack - depth must match switch 11.2" - swing out preferred - Tripp Lite 12U Wall Mount Rack Enclosure Server Cabinet, 16.5" Deep, Switch-Depth (SRW12U)
  2. Gen2 Cloud Key
  3. 2x1000ft boxes CAT6a
  4. Punchdown tool
  5. Keystone Patch Panel - 24-Port CAT6A Unshielded 1U Patch Panel 19-Inch Loaded w/Tool-less Keystone Jacks Rackmount or Wallmount
  6. Ubiquiti 42 port switch fanless
  7. 3 in-wall APs
Retrieved from "http://beyla.local/index.php?title=Resources/Network/272_Capp_Planning&oldid=4400"