Network/Reboot

From Sudo Room
Jump to navigation Jump to search

Taking notes for creating a new network as part of the Sudo Room Reboot, including upgrading to a bigger space!

Plan

In order to focus on good service and user experience, will plan to first deploy a "bootstrapped" wireless network, then plan and coordinate a proper wired network.

Phase 1: Bootstrapped Wireless Network

In this phase, the focus will be on wireless network service with one powerful wireless router, set up wherever the internet connection is. We'll extend the network by using wireless repeaters that have ethernet interfaces. We'll be able to take the broadcast network from the primary router, repeat it to other parts of the building with these repeaters, and ultimately connect switches to the repeaters' ethernet interfaces to extend the network throughout the building.

Wishlist

  • 1 - Really powerful wireless router
  • ~10 - Wireless Access Points (APs)
  • ~5 - Low-power Switches

Plan

Turns out there are a few wireless devices available from Sudo Mesh that aren't very helpful for the Mesh/Firmware, so we can use them with OpenWRT for this purpose. Especially helpful are the Ubiquiti Bullet 2HP routers, which simply have just barely enough memory to be operational, but are ultimately not practical for Sudo Mesh's purposes.

Ubiquiti Bullet 2HP

  1. Reset router, following the instructions here: Mesh/WalkThrough#Bullet
  2. Install OpenWRT firmware, using this image: http://downloads.openwrt.org/attitude_adjustment/12.09/atheros/generic/openwrt-atheros-ubnt2-jffs2-64k.bin
    1. Unfortunately need to use an old version of OpenWRT ("Attitude Adjustment" 12.09) since the community has stopped supporting this device (too low memory).
  3. Configure as repeater
    1. Simplest option is to use the LuCI interface to add the existing wireless network as a "Client" and additionally add the Bullet router's own network as "Master", as shown in this video: https://www.youtube.com/watch?v=3rbsh2zxPnk
    2. (Optional) consider alternative methods for repeating a network listed below:
      1. Wireless Distribution System (WDS) http://wiki.openwrt.org/doc/howto/clientmode#wds.-.wireless.distribution.system
        1. WDS is possible with atheros chipset devices, but the internet-providing Access Point needs to be running OpenWRT as well.
        2. In case wired devices don't work with the current configuration (based on video above), will need to use this option in order to get desired result:
          1. "Any wired devices connected via Ethernet to the LAN ports on the remote client bridge device should now be transparently bridged into the main network over the wireless link."
      2. Routed Client Mode http://wiki.openwrt.org/doc/howto/clientmode#routed.client.mode
      3. Bridged Client Mode (brcm-2.4 only) http://wiki.openwrt.org/doc/howto/clientmode#bridged.client.mode.brcm-2.4.only
        1. Not compatible with Bullet router.
      4. Bridged Client Mode (with relayd) http://wiki.openwrt.org/doc/howto/clientmode#bridged.client.mode.with.relayd
        1. Compatible with Bullet router, but requires installing new dependencies, for limited memory device. May need to remove unused packages to make room for this—seems like it could provide better performance than the client/master solution.

Phase 2: Proper Wired Network

As soon as a basically functioning and stable bootstrapped wireless network is deployed, we will begin the next phase, deploying a proper wired network for the whole building. The emphasis will be on modularity, reliability, maintainability, quality materials, and forward-thinking design of the network that will definitively meet the practical needs of the building by providing ubiquitous network connectivity.

Once this network is functional, we'll simply add wireless access points to replace the bootstrapped wireless network.

Wishlist (in progress)

Note: If this 'wish list' becomes a reality will get us with a solid backbone network; for a good amount of years to come. Anyway, We are listing two racks, a 2 and 4 post racks. But, if $ is an issue then I suggest that we make the effort to get one 4 post rack with square holes. This 4 post rack would be able to handle switches and rack servers as well. Also essential, if chosen to have a CAT6A backbone, connectors, patch panels, cables should be CAT6A. Otherwise if one of those items is CAT5 or CAT5e, then the network will go for the lowest Category available. -Wiring Scheme to be used: T568B. -Sudo and all Omni Collective members participation is very welcome; ask/answer/suggest/comment/etc.


TOC

  • Switch Rack
  • Server Rack
  • Patch Panel for Switch Rack (2RU)
  • Patch Panel for Server Rack (1RU)
  • Category 6A Jack Modules
  • RJ45 Connectors
  • Mini-Com Surface Mount Box
  • Network CAT6A Bulk Cable
  • Network CAT6A Patch Cable
  • Vertical Cable Management Trays
  • Horizontal Cable Management Tray
  • Miscellaneous

TOTAL (approx): $

Switch Rack:

    • Quantity: 1
    • Item: Panduit 2 Post Modular NET FRAMEâ„¢ Rack
    • Manufacturer: Panduit.com
    • Part Number: NFR84
    • Item details: Rack and Accessories
    • Price: $529.97
    • Accessories: Not included in price shown above, we need to discuss which ones should we getting.

Server Rack:

Patch Panel for Switch Rack (2RU):

Patch Panel for Server Rack (1RU):

Category 6A Jack Modules:

    • Quantity: 1 (Package of 24)
    • Item: Category 6A, RJ45, 10 Gb/s, 8-position, 8-wire universal Bulk Packaged
    • Manufacturer: Panduit.com
    • Part Number: CJ6X88TGAW-24
    • Item details: Details Here Installation Instructions Here
    • Price: $

RJ45 Connectors:

    • Quantity: 20
    • Item: 8-position, 8-wire modular plug, for use with 28 AWG, Category 6, UTP copper cable.
    • Manufacturer: Panduit.com
    • Part Number: SP628-C
    • Item details: Details Here Installation Instructions Here
    • Price: $

Mini-Com Surface Mount Box:

    • Quantity: 20
    • Item: Mini-Com® surface mount box accepts up to two Mini-Com® Modules. Includes built-in removable blank to add a second module. Dimensions: 1.06"H x 1.95"W x 3.65"L (27.0mm x 49.5mm x 92.7mm)
    • Manufacturer: Panduit.com
    • Part Number: CBX2AW-AY
    • Item details: Details Here Installation Instructions Here
    • Price: $

Network CAT6A UTP Bulk Cable:

    • Quantity: 1000 Feet
    • Item: Category 6A UTP Copper Cable
    • Manufacturer: Panduit
    • Part Number: CMP
    • Item details: Details Here
    • Price: $325

NOTE: We also accept CAT5e donations for non-backbone use.

Network CAT6A UTP Patch Cable:

    • Quantity: 24
    • Item: Category 6A UTP Copper Cable
    • Manufacturer: Panduit.com
    • Part Number:
    • Item details: 4'-6' Length
    • Price:

NOTE: We also accept CAT5e donations.

Vertical Cable Management Trays

    • Quantity: 2
    • Item:
    • Manufacturer: Panduit.com
    • Part Number:
    • Item details:
    • Price: $

Horizontal Cable Management Tray

    • Quantity: 1
    • Item:
    • Manufacturer: Panduit.com
    • Part Number:
    • Item details:
    • Price: $

Miscellaneous

  • Cagenuts and screws (IMPORTANT TO HAVE, SWITCHES AND SERVERS NEED THEM TO SCREW THEM INTO THE RACKS)
  • Wire ties
  • A roll of Velcro
  • Anything else???

TOOLS: I have a set that we can use.

Questions/Answers/Comments

Date: Tue, 17 Jun 2014: I've not done the walk-through yet because of the somewhat restricted access to the whole building, so no photos.

1.- Based on the current equipment and envisioning the future of Sudo-SudoMesh(-Omni) what size room do we need?

2.- How is the potential room airflow?

3.- How is temperature of the room, now and during the Summer?

4.- Are there electrical outlets nearby?

5.- Do we have enough Amps in that area?

6.- If not, do we need to install a circuit breaker box with scalability?

7.- Room's accessibility?

8.- Security: Who and when people have access to it when no Sudoers are present?

9.- What type of racks, 2 or 4 of both size rack? or no this of rack? Someone mentioned a wall mount rack in the open?

10.- If 2 or 4 post rack, should we get CAT6A ready? This means that at least the backbone wiring, Patch panel, and connectors need to be CAT6A.

Questions from others fellow hackers:

11.- What do you think about Someone's suggestion of going for a wall rack instead Selecting a Wall Mount Rack?

12.- Can we find someone to bend chicken-wire into the tracks we need to hang from the ceiling?

SERVER ROOM UPDATES

2014/07/05: Today Luis, Matt, and I did the walk in the building, and so far the only place that seems the most appropriate to have the server room is the room by the bar.

This area is the most ideal in the whole building because the air flow, temperature, electricity proximity, and also because it is where the Internet access enters the building.

Since this area is not is not part of the SudoRoom space, we will have to talk about it with the rest of the Sudo-Mesh group and the group approves it, then we would have to present the idea at our Omni Collective meeting for approval.

If approved by the Omni Collective, we would need to build:

  • A 2" or so high floor (two by fours and plywood would do, I believe.
  • A 55" x 65" cage with chicken wire walls and a door.

If this place is NOT approved by the OOC then perhaps we should consider building the Server Room in the SudoRoom Space. High temperature and noise levels are the main issues.

If others have ideas/comments/or want to be part of this process please jump in. You may contact Matt, Luis, or myself (Daniel).

This update and all other Network/Reboot project is found at: https://sudoroom.org/mediawiki/index.php?title=Network/Reboot

Definitions

Retrieved from "https://sudoroom.org/mediawiki/index.php?title=Network/Reboot&oldid=8384"