Resources/Network: Difference between revisions

From Noisebridge
Jump to navigation Jump to search
Line 55: Line 55:
There is a router in our wireless CPE hardware (st01-noisebridge-sfo) that connects up to the Noisebridge network and terminates as 172.30.0.54 on the "Inside / Internal" network. Set your default route via this IP to try the other path.
There is a router in our wireless CPE hardware (st01-noisebridge-sfo) that connects up to the Noisebridge network and terminates as 172.30.0.54 on the "Inside / Internal" network. Set your default route via this IP to try the other path.


== Access Control==
==I want to help!==
 
Noisebridge is run by volunteers, you're welcome to help but should get to know those helping first before touching/hacking the network gear. Try introducing yourself on the [rack mailing list https://www.noisebridge.net/mailman/listinfo/rack].
Most hardware is set to use the most guessable logins and passwords possible. If you're interested in logging in, just make some guesses as to what the login can be. Use your favorite search engine. Poke around. Hack.
 
Experience the thrill of guessing a password that just works.


== Router ==
== Router ==

Revision as of 21:45, 23 February 2016

Network Troubleshooting

Are you having issues with the internet or local network? Check out the Network Troubleshooting page for more information on what you can do to make things better or possibly seek help.

Disclaimer

Please note that Noisebridge does not guarantee or provide a perfect secure experience in the space. Just like anywhere else in the world you're held responsible for your own safety and wellbeing. This also includes content you receive or transmit or provide through any mediums, such as through pen and paper, sound waves or any networks wired or wireless functioning in the space. Noisebridge is a volunteer run and operated space that provides you with infrastructure, which you use at your own risk.

Free Public Wireless Networks

Noisebridge has two open wifi networks available for your use. In most cases if you connect to the network Noisebridge your laptop/phone/device will have the best luck getting crystal clear wifi and roam between radio channels according to which provides the most reliable and fastest connection.

The wifi and internet provided is for public use. Like any public network, you should regard Noisebridge's as potentially hostile and take appropriate precautions. In order to not give the impression of providing false security, Noisebridge does not run any encrypted wifi networks.

The following networks are active:

  • Noisebridge
    • No password
    • Uplink through Monkeybrains gigabit laser
    • 802.11an 5 gHz only
  • Noisebridge Legacy 2.4 gHz
    • No password
    • Uplink through Monkeybrains gigabit laser
    • 802.11an 2.4 gHz only

Wired network

There are drops throughout the space. They are labeled with the corresponding number on the patch panel. Please don't destroy them (lol).

Local Network Address Information

DHCP is offered automatically on the network, if that doesn't work for you here's some more static information...

  • IP Range: 10.20.1.200-10.20.1.254
  • Gateway: 10.20.0.1
  • Subnet: 255.255.254.0 (a "slash" /29)
  • DNS: 10.20.0.1,208.69.43.23,208.69.40.4,8.8.8.8

Dynamic DNS is provided by the router for DHCP clients on 10.20.0.1/29 which also provides name resolution of some local machines.

Development

Network Devices & Services

2169 Mission

Uplinks

Monkeybrains Wireless Link

We have a point-to-point wireless link to Monkeybrains on the roof. It is wired into the Monkeybrains NEMA box on the roof, and from there into our own NEMA box in which we house a managed switch. From there the cable enters into the space through the ladder chute in the fox lounge and runs to the rack where it enters the switchboard at port 48. Port 48 is a second redundant run that follows the same path from the rack back to our NEMA box for future projects.

SFBroadband / City of SF / Internet Archive

We have a wireless point-to-point path up to Twin Peaks that connects up to a city-owned and volunteer-run IP transit network. Currently, we're hitting the dish off of the side and have a pretty terrible connection. For now, this network path is mostly only usable as a backup path.

There is a router in our wireless CPE hardware (st01-noisebridge-sfo) that connects up to the Noisebridge network and terminates as 172.30.0.54 on the "Inside / Internal" network. Set your default route via this IP to try the other path.

I want to help!

Noisebridge is run by volunteers, you're welcome to help but should get to know those helping first before touching/hacking the network gear. Try introducing yourself on the [rack mailing list https://www.noisebridge.net/mailman/listinfo/rack].

Router

Biketrailer is our humble router. It is an Ubiquiti Edgerouter 5-port box running EdgeOS, a fork of Vyatta (a Linux-based router distribution). While the router does provide PoE, it is non-standard passive Ubiquiti PoE which you should avoid using.

The machines currently provides

  * dhcpd
  * DNS (dnsmasq) - .noise local TLD and recursive proxy

Access is via SSH with keys and a https web interface.

Address Allocations

The reserved address allocations are:

75.101.62.88/29 from Sonic.net

We have a range within the encompassing /24: 75.101.62.{88..95}

  • .88 - biketrailer
  • .89 - pony.noisebridge.net
  • .90 - stallion.noisebridge.net
  • .91 - ChaosVPN la fonera eth0.1
  • .92 - minotaur.noisebridge.net
  • .93 - Unallocated
  • .94 - Unallocated
  • .95 - Mode-S Equipment (various port-NATings)

10.20.0.0/22 ("inside" network)

10.20.0.0 - 100 Statically-addressed things

Note: This is not a /24 subnet! The netmask is a /23.

  • .0.2 - biketrailer
  • .0.3 - pony
  • .0.4 - minotaur - console server and network troubleshooting/monitoring box
  • .0.5 - roof switch
  • .0.8 - Primary switch - Netgear GS724Tv2
  • .0.11 - West AP, DHCP mapped
  • .0.12 - Crutch AP, DHCP mapped
  • .0.22 - Pegasus
  • .0.52 - bunny (Bullion Mode-S receiver on the roof)
  • .0.53 - ronin (white Atom works with bunny, lives in Susan the Rack)
  • .0.54 - st01-noisebridge-sfo (sfwireless.org Ubiquiti Nanobridge M5 on the roof. Currently aimed at Twin Peaks.)

10.20.0.101 - 1.254

  • DHCP-assigned, user-access IP space

IPv6

Note: This is not currently implemented. The addresses are correct, though. Someday...

We have IPv6 support on the DSL circuit via a tunnel provided by sonic.net. The tunnel address is 2001:05a8:0:1::0ac6/127 , if it needs to be reconfigurated.

2001:5a8:4:5630::/60

This is the IPv6 subnet assigned to us by sonic. We configure the first /64 in this /60 so that autoconfiguration works. biketrailer hands out IPv6 router advertisements for this subnet directly, and your machine will SLAAC its way to ipv6 goodness. They're directly routable, but unsolicited incoming traffic is blocked by the firewall to protect the users. This means you can't run an IPv6 server on our IPv6 subnet, but you can connect to other machines on the IPv6 Internet just fine.

Machine Rack

The rack of machines and switches is counted by U, from the top, starting from "1".

"U"/Unit Device
1-2 patch panel
3 Netgear G724Tv2 switch
5 Shelf with Bikeshed and POE injectors
7 Minotaur
Bottom APC UPS