Resources/Network/272 Capp Planning - Revision history

Kevinbagel: /* 2024 rebuild */

2024-07-30T00:54:36Z

2024 rebuild

← Older revision		Revision as of 17:54, 29 July 2024
Line 17:		Line 17:
	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. <div class="mw-collapsible mw-collapsed"> 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.		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. <div class="mw-collapsible mw-collapsed"> 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.
	</div><br>		</div><br>

			===Possible Alternatives===
			Netgate makes pfsense appliances at similar pricepoints to EdgeRouter.
			{\| class="wikitable" style="margin:auto"
			!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
			\|}

Mcint: /* Goals */ fix tm

2024-07-28T02:13:50Z

Goals: fix tm

← Older revision		Revision as of 19:13, 27 July 2024
Line 3:		Line 3:
	== 2024 rebuild ==		== 2024 rebuild ==
	===Goals===		===Goals===
	* Just works ~~:TM:~~, hard to break, LAN management. (see 2020 buildout)		* Just works ™, hard to break, LAN management. (see 2020 buildout)

	===Work in progress===		===Work in progress===

2607:F598:B0C0:207:A961:EF0D:7D9F:91E4: /* 2024 rebuild */

2024-07-23T02:57:32Z

2024 rebuild

← Older revision		Revision as of 19:57, 22 July 2024
Line 8:		Line 8:
	* Dig into EdgeRouter 4. Extract, replace USB.		* Dig into EdgeRouter 4. Extract, replace USB.
	** Put distinguishing external labels on routers. And create pages / sections for them on the wiki.		** Put distinguishing external labels on routers. And create pages / sections for them on the wiki.

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

Mcint: start 2024 planning

2024-07-22T22:37:39Z

start 2024 planning

← Older revision		Revision as of 15:37, 22 July 2024
Line 1:		Line 1:
	{{network}}		{{network}}

			== 2024 rebuild ==
			===Goals===
			* Just works :TM:, hard to break, LAN management. (see 2020 buildout)

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


			====Motivating problem====
			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. <div class="mw-collapsible mw-collapsed"> 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.
			</div><br>



			<hr>

			== 2020 move buildout ==
	https://pad.riseup.net/p/nbrack		https://pad.riseup.net/p/nbrack

Lxpk at 05:27, 24 December 2021

2021-12-24T05:27:00Z

← Older revision		Revision as of 22:27, 23 December 2021
Line 1:		Line 1:
	{{~~resources~~}}		{{network}}

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

Lxpk at 05:24, 24 December 2021

2021-12-24T05:24:05Z

← Older revision		Revision as of 22:24, 23 December 2021
Line 1:		Line 1:
			{{resources}}

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

Bfb at 06:03, 26 August 2020

2020-08-26T06:03:16Z

← Older revision		Revision as of 23:03, 25 August 2020
Line 23:		Line 23:
	# Recruit volunteers to help with the above		# Recruit volunteers to help with the above
	# Perform laster migration with MonkeyBrains (2169 offline/272 online date)		# Perform laster migration with MonkeyBrains (2169 offline/272 online date)

			=== 25 August 2020 - 272 Capp Rack Planning notes ===

			==== Stuff to do ====
			# Meet MB to move laser on Sunday 8/30 at 12:00
			# Permission from LL to drop cable through roof

			===== BOM for build out =====
			# 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)
			# Gen2 Cloud Key
			# 2x1000ft boxes CAT6a
			# Punchdown tool
			# Keystone Patch Panel - 24-Port CAT6A Unshielded 1U Patch Panel 19-Inch Loaded w/Tool-less Keystone Jacks Rackmount or Wallmount
			# Ubiquiti 42 port switch fanless
			# 3 in-wall APs

Bfb at 06:04, 10 July 2020

2020-07-10T06:04:28Z

← Older revision		Revision as of 23:04, 9 July 2020
Line 1:		Line 1:
	https://pad.riseup.net/p/nbrack		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 ===		=== 09 July 2020 - 272 Capp Rack Planning notes ===

Bfb: Created page with "https://pad.riseup.net/p/nbrack === 09 July 2020 - 272 Capp Rack Planning notes === NB Rack Philosophy - as simple as possible. Next Rack Guild meeting to occur 23 July 202..."

2020-07-10T05:54:56Z

Created page with "https://pad.riseup.net/p/nbrack === 09 July 2020 - 272 Capp Rack Planning notes === NB Rack Philosophy - as simple as possible. Next Rack Guild meeting to occur 23 July 202..."

New page

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

=== 09 July 2020 - 272 Capp Rack Planning notes ===

NB Rack Philosophy - as simple as possible.

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

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