Networking

From SkullSpace Wiki
Revision as of 00:10, 18 January 2012 by Ayecee (talk) (→‎Servers)
Jump to navigation Jump to search

~ please keep an updated copy of this page printed out and posted in the server room, so we have access to documentation even if the network / internet has issues ~

Network status

Skullspace internal network is fine but needs better organization and documentation, see tasks section. Internet connection has occasional issues when the SkSp or AW routers have trouble getting an IP, this is being troubleshooted.

high-level description

Internet is furnished by VOI, goes to the internet switch where multiples routers and servers connect. There is a Linksys router for the main Skullspace network; this connects to a 24-port gigabit switch which has a few sub-switches in different rooms. There are APs around skullspace with the "skullspace" SSID and some near the fire escape connected to dishes outside.

Internet feeds

Primary: Internet from VOI (wifi-based Ubiquity NB5, tested 60mbit down 20mbit up to Speedtest.net Winnipeg) comes from a drop in the middle of the space, connects to line #?? below the drop, goes to the server room where its PoE is; afterwards goes to the primary internet switch. We have permission to use a few IPs (currently being assigned by DHCP, but that may change - that's why they have the small white Microtik router) and a 'reasonable' amount of bandwidth.

Network hardware

All switches and their interconnects are gigabit (a few exceptions below), so two machines doing 100mbit of transfer won't fill any pipes on the way.

  • Linksys WRT54G2 as main router. G wireless has been tested to 33mbit. Port forwarding rules are noted later in this page. Also used as switch (100mbit only) LAN ports connected to the main switch.
  • A Cisco 4924 (:A0) as the main switch, by default everything connects here.
  • A Cisco 4924 (:??) a spare
  • Netgear GS108T as the workshop switch
  • D-Link DWL-7100AP as a testing 2ghz/5ghz wireless AP in the workshop
  • A Belkin F5D8236 wireless-N router in the lounge room is setup as an AP and switch (100mbit only), connected to the main SkSp network
  • Belkin F5D5141-5 Gigabit switch in the lounge.
  • Intel 510T - currently unused
  • Cisco 2950 #1 and #2 - currently unused

Wiring

Please follow the standard below when labeling any new lines. LSB is closest to the RJ45.

num in binary R/G Description
00 RRR (000) Workshop pole
01 RRG (001) wirelss APs (1of3)
02 RGR (010) Workbench south
03 RGG (011) Workbench North
04 GRR (100) Classroom west
05 GRG (101) Drink machine
06 RRG (110) Lounge north
07 GGG (111) Lounge south/switch/router
08 GRRR (1000) Electrical room/Assentworks (1of2)
09 GRRG (1001) Electrical room/Assentworks (2of2)
10 GRGR (1010) War Room 1of2
11 GRGG (1011) War Room 2of2

The above runs were conservative - in many cases only a single drop because we were low on cat5, when I'd have preferred to put 2 drops to be prepared for the future - but they still total up to 2000ft of cable, and ~15hrs of wiring work.

Tasks

  • discover why the routers aren't getting IPs occasionally
  • finish mapping and labeling ethernet lines
  • terminate lines correctly in a panel once we're sure server room is stable
  • run 12? lines cleanly from networking rack to the blue racks.
  • label networking equipment (IPs etc) and servers, update this page for the latter
  • seperate security/camera network from Skullspace network
  • organize secondary internet feed, better router and switch for it

King's Head Pub AP

A popular meeting space in Winnipeg, 1 block away from Skullspace, which doesn't have wifi - but we can see the rear of its brick building from Skullspace. So we used a donated Cisco Aironet 1100AP, modified it for external antenna connection, ran some LMR400 cable outside the fire escape door and up the fire escape ladder, and pointed a 19dbi dish towards the pub. SSID is SkullSpace-dish-aimedatKingsHead, ask a member for the password. It doesn't work at all in the south main-floor area, but it does have coverage in most parts of the north main-floor area. Speedtests: 1 to 4mbit down on a laptop with a good wireless card (Atheros N). I tried to replace the Cisco 802.11B card in the AP with a 802.11G upgrade card (AIR-MP21G-A-K9), but it became almost impossible to connect - likely because Cisco was becoming involved with Broadcom at the time that G card was made, who's known for the low sensitivity and receiver quality of their chipsets.

Plans to increase coverage:

  • upgrade 19dbi to 24dbi antenna - I have some, but they're huge and a lot of windload to put on the fire escape ladder (especially if they ice up in the winter), would prefer a roofmount pad. We'd need to calculate that the smaller beamwidth of the higher-gain antennas doesn't lose coverage of the edges of the King's Head - this math would be size of Kings's Head building x distance = degrees of view?
  • add antenna receive diversity - again, the second antenna would be better on an additional (spaced farther apart horizontally) roofmount pad; vertical diversity on the fire escape ladder wouldn't help as much.
  • move antenna - currently the view (all the way up the fire escape ladder) to the front of King's Head is blocked by a concrete building. 5-10ft south on a roofmount would be ideal.
  • add an amplifier or a higher-power radio. The Cisco puts out 100mw, have a 500mw amplifier. Since this isn't an omni but a highly directional antenna, we could maybe classify it under the rule that allows 24dbi gain and 24dbm power output (500mw is 27dbm, but we're losing 3 db in the 40ft of LMR cable and connections, which brings us nicely to 24dbm).
  • ground the fire escape ladder - I'm careful about grounding all antenna structures.
  • check that the antenna and LMR cable/connections are running at full efficiency - this is old gear from my garage and I can't guarantee that they were.

Signal in the North-main floor area is currently -82 to -87 when connection is possible, with all of the above I'd hope to get it to mid-70s numbers which should allow for pretty good coverage, considering we're a block away and going through thick brick/concrete.


Linksys Port Forwarding entries

If ever we need to reset the Linksys, these will be put back in, so keep them updated.

  • webcam1 port 31337 tcp to 192.168.1.250
  • webcam2 port 9001 both to 192.168.1.250
  • webcam3 port 31338 tcp to 192.168.1.251
  • webcam4 port 80 tcp to 192.168.1.124
  • MUMD port 22(SSH) tcp to 192.168.1.10
  • Russtot port 993 tcp to 192.168.1.99
  • Russvent port 3748 tcp/udp to 192.168.1.99

IP usage

  • 192.168.1.1 Linksys Router in server room
  • 192.168.1.2 Reserved
  • 192.168.1.3 Belkin N Router in Lounge area
  • 192.168.1.4 Cisco AP (King's Head)
  • 192.168.1.5 Reserved
  • 192.168.1.6 Intel 510T switch
  • 192.168.1.7 Cisco AP (south)
  • 192.168.1.8 HP parallel print server
  • 192.168.1.9 MUMD host distro
  • 192.168.1.10 MUMD latest Ubuntu (currently natty 11.04)
  • 192.168.1.11 MUMD Debian 6.0 (wheezy)
  • 192.168.1.12 Samsung CLP-310N printer
  • 192.168.1.13 MUMD Debian stable, system services
  • 192.168.1.15 Cisco 2950 switch
  • 192.168.1.16 Netgear GS108T workshop switch
  • 192.168.1.17 Cisco 4924 Switch-1 (main)
  • 192.168.1.18 Cisco 4924 Switch-2
  • 192.168.1.20 D-link DWL-7100AP for testing
  • 192.168.1.42 Andrew's server - internal interface
  • 192.168.1.69 Ayecee's server - internal interface
  • 192.168.1.99 Russ' netbook
  • 192.168.1.100-199 Linksys DHCP space
  • 192.168.200-220 Network lab address space
  • 192.168.1.250 Old crappy cameras (currently offline)
  • 192.168.1.251 New Camera
  • 192.168.1.252 Cameras


Servers

Name Model/setup IPs and MACs Description/contact
Ayecee's HP Proliant ML350 4U external: 206.220.194.196 / 00:0b:cd:4d:e3:a4 dhcp internal: 192.168.1.69 / 00:08:02:ed:cc:a0 LOM: 192.168.1.70 / 00:0b:cd:2f:e0:17 ayecee AT gmail DOT com
Andrew's Prime Hunter Dell PowerEdge 1750 1U 206.220.194.144 / 00:11:43:59:f8:da andrew AT andreworr DOT ca Details on it's prime hunting progress here: http://www.primegrid.com/show_host_detail.php?hostid=229945
Ben's White case w/ front game port 206.220.194.212 / 00:4f:49:0b:f7:fb ben@benbergman.ca
Mark's MUMD Ghetto case, no lights connected 192.168.1.9-11,13 / 00-0e-a6-7d-41-e6 mark at parit . ca ?
Andrew's prime hunter 2 Dell Poweredge 1600SC 206.220.194.187 / 00:c0:9f:24:c0:2a andrew AT andreworr DOT ca
Alex's shiny server Shiny case 206.220.194.204 / 00:50:8d:b4:1a:4c ????
Alex' Dell server Dell Dimension 8250 206.220.194.166 / 00:50:5d:6c:5e:92 ????
????? DVEO rackmount box ?????/????? ????

Keys

The following members have keys to the server room:

  • Ron Bowes
  • Andrew Orr
  • Mak Kolybabi
  • Colin Stanners

If you'd like a key, and you have a reason, let me know and I'll make sure you get one! --Ron

Retrieved from "https://wiki.skullspace.ca/index.php?title=Networking&oldid=1267"