Resources/Network

From Noisebridge
< Resources
Revision as of 20:36, 15 August 2014 by Rubin110 (Talk | contribs)

Jump to: navigation, search

Contents

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.

Wireless networks

Free Open Unsecure Wifi

Noisebridge generally has two or more unencrypted open wifi access points available for your use. If you can see the "noisebridge-a" network, congratulations, you have an 802.11a-compatible card and should use this network as it is better faster and stronger than the others. If you cannot see noisebridge-a, either it is not working or you do not have an 802.11a card. You probably have an 802.11g card. Hopefully you can see the "noisebridge" network, which is the one you should use in that case. Like any public network, you should regard noisebridge's as potentially hostile and take appropriate precautions.

The following networks are active at 2169 now:

  • Noisebridge
    • No password
    • Uplink through Sonic.net and Monkeybrains
    • 802.11gn 2.4 gHz and 802.11an 5 gHz, your wifi device decides which network is the best for it and roams accordingly
  • Noisebridge 5g
    • No password
    • Uplink through Sonic.net and Monkeybrains
    • 802.11an 5 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).

DNS

Dynamic DNS is provided by the nat machine for DHCP clients on 172.30.0.30/22. Resolution of machines with static addresses is done by ipv4 or ipv6 mDNS and dynamic DNS entries on the nat machine from the DHCP service.

Development

Network Devices & Services

2169 Mission

Uplinks

DSL Circuit

There is a Sonic.net Fusion ADSL2+ DSL connection in the building. The physical circuit comes in from the MPOE in the basement and runs across the roof of the basement and up the side of the building into the DJ booth (Tea Room), then over to the Wall o' Tubes. The CPE is a Motorola 2210 ADSL2+. The admin password is the serial number, written on the bottom.

The addressing configuration is a little unusual. It's 75.101.62.0/24 and we've been allocated a /29 within that block: 75.101.62.88 - 75.101.62.95. Note that we get to use all 8 addresses; the broadcast and network address are 75.101.62.255 and 75.101.62.0 respectively. The gateway is 75.101.62.1.

The default CPE settings are not correct for our circuit configuration. From a factory reset, do the following to configure the CPE:

  1. Configure a computer for 192.168.1.253/24.
  2. Connect the computer to the DSL CPE.
  3. Power cycle the DSL CPE.
  4. Connect to 192.168.1.254 using your web browser.
  5. You will be prompted to set a password, use the serial number on the bottom of the DSL CPE.
  6. Get into expert mode.
  7. Under configure->connections, set the following:
    1. VPI: 0
    2. VCI: 35
    3. Protocol: Bridged Ethernet LLC/SNAP
    4. Bridging: on
  8. Under configure->DHCP server, set the following:
    1. DHCP Server Enabled: unchecked
  9. Save and reboot.

Motorola 2210 User Guide

Monkeybrains Wireless Link

We have a point-to-point wireless link to Monkeybrains on the roof. It comes down through the Dirty Shop skylight and runs in to the server closet.

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.

Access Control

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

Bikeshed is our humble router. It is a Soekris running Vyatta(a Linux-based router distribution).

The machines currently provides

  * dhcpd
  * DNS (dnsmasq) - .noise local TLD and recursive proxy
  * Automatic loadbalancing and ailover between Sonic DSL and monkeybrains

Access is via SSH with keys.

Salient configuration

  • It is configured to fail over between DSL and Monkeybrains as conditions warrant.
  • It is configured with traffic shaping to prevent individual users from sucking up all the tubes.

If you have questions about these particular points of configuration, email rack. Nothing is particularly complicated.

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 - bikeshed
  • .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)

172.30.0.0/22 ("inside" network)

172.30.0.0 - 127 Statically-addressed things

Note: This is not a /25 subnet! The netmask is a /22.

  • .2 - bikeshed, soekris router (runs Vyatta Linux and iptables/netfilter)
  • .3 - free
  • .4 - minotaur - console server and network troubleshooting/monitoring box
  • .5 - goat - Internal network testing VM on stallion
  • .6 - treechopper, Laserjet 5Si MX (working, not hosed)
  • .7 -
  • .8 -
  • .9 -
  • .10 - stallion - VM hosting server
  • .11 - ChaosVPN la fonera internal interface (br-lan)
  • .12 -
  • .13 -
  • .14 -
  • .15 - Primary switch - Netgear GS724Tv2
  • .16 -
  • .17 -
  • .18 -
  • .19 -
  • .20 -
  • .21 -
  • .26 -
  • .30 - Pony, main sandbox server
  • .31 -
  • .32 -
  • .33 -
  • .34 -
  • .35 - Cisco IP Phone
  • .36 - Red Payphone (Linksys PAP2)
  • .37 -
  • .41 -
  • .42 -
  • .43 -
  • .44 -
  • .48 -
  • .49 -
  • .50 -
  • .51 -
  • .52 - bunny (Bullion Mode-S receiver on the roof)
  • .53 - ronin (white Atom works with bunny, lives in Susan the Rack)
  • .54 - st01-noisebridge-sfo (sfwireless.org Ubiquiti Nanobridge M5 on the roof. Currently aimed at Twin Peaks.)
  • .55 -
  • .56 -

172.30.0.128/25, 172.30.1.0/24, 172.30.2.0/24, 172.30.3.0/24

  • DHCP-assigned, user-access IP space

172.30.4.0/24 (Tor-ified network)

Note that 172.30.4.1 transparently proxies TCP connections via privoxy to tor.

  • .1 - "torbridge" interface on pony
  • .2 - "noisebridge-tor" access point.
  • .10 - .254 -- Tor-ified clients (served by DHCP)

172.31.0.0/24

This is a separate NAT-ed network for Monkeybrains-only traffic. It's served by "bikeshed".

  • .1 - wlan0.bikeshed.noise
  • .100 - .199 -- DHCP pool for clients.

10.100.4.0/23 ChaosVPN Range

  • Network in the ChaosVPN
    • Has yet to be setup. In the future, we may join the network so that we can route to other hackerspaces
  • ChaosVPN Wiki

IPv6

We have IPv6 support on the DSL circuit via a tunnel provided by sonic.net. Some details on how to get the OpenBSD-based flashrd distribution on the routers to tunnel correctly can be found on the Flashrd page.

Note that using IPv6 in some situations can result in people knowing what model of computer you have and the network card's serial number, because of the way IPv6 stateless address configuration works. If this is a concern, tell your computer not to use IPv6. Ask around Noisebridge if you need help or want more details.

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

This is the IPv6 subnet assigned to us by sonic. We only use the bottom /64 of this /60 so automatic address configuration works right; the other 15/16s of the address space are intentionally wasted. r00ter hands out IPv6 router advertisements for this subnet directly. 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. If you really need to run an IPv6 server for some reason, consider using Teredo.

OOB Management

Everything is connected to Minotaur.

Device Where Settings
bikeshed ops /dev/ttyS2 115200

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

Switch Ports

Primary switch

Netgear G724Tv2

VLANs:

  • VLAN 1: Internal network, 1-17
  • VLAN 2: Monkeybrains, 18-19
  • VLAN 3: Sonic, 20-24
Personal tools