Networking

• Please keep an updated copy of this page printed out and posted in the server room, so there is access to documentation even if the network / internet is down
• Also see IT Policies

Network status

Skullspace internal network is fine but needs better organization and documentation, see tasks section. Occasional issues connecting to the main skullspace SSID. 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 main 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 SSIDs beginning with "skullspace" and some near the fire escape connected to dishes outside, with different SSIDs.

Internet feeds

Primary: Internet from VOI (wifi-based Ubiquity NB5, tested 60mbit down 20mbit up to Speedtest.net Winnipeg, with large packets) 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.

• Netgear WNDR3700 as the main router, donated by Project Bismark. Port forwarding rules are noted later in this page. Also used as switch. It had a problem (routed packets fine but services like DHCP/DNS/web server didn't work) so was taken out of the network to test.
• Linksys WRT54G2 as a classroom AP. G wireless has been tested to 33mbit. WAN port may sometime have packet loss.
• Linksys WRT350N with DD-WRT v24SP2 firmware as a spare main router when the Netgear has issues
• A Cisco 4924 (:A0) as the main switch, by default everything connects here.
• A Cisco 4924 (:??) a spare switch
• Netgear GS108T as the workshop switch
• D-Link DWL-7100AP as a testing 2ghz/5ghz wireless AP in the workshop, still unproven
• 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. May have had packet loss before.
• 2 Cisco Aironet 1100 APs modified with pigtails to connect to outside dishes
• Belkin F5D5141-5 switch in the lounge.
• Intel 510T switch - currently unused. Old, only telnet management
• Cisco 2950 switches #1 and #2 - currently unused, will setup as internet-side switches
• MT RB450? (small white box) VOI's router

Wiring

Please follow the standard below when labeling any new lines. LSB is closest to the RJ45. Unless otherwise noted, all wires below originate from the main rack. All wiring should be cat5 or better, T568B standard (orange-first).

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

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

Tasks

• discover why the routers aren't getting IPs occasionally
• discover why there's occasional issues connecting to the main SSID on Netgear router.
• 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
• separate security/camera network from Skullspace network
• organize secondary internet feed, better router and switch for it
• put read-only and full-access passwords on devices

Wireless Networks

SSID	speeds	password	description
skullspace	N2.4/5.x	(normal)	main network; Netgear AP in server room
skullspace[25]ghz_test	A/G	(normal)	D-link AP in workshop, being tested
skullspace_lounge_test	N2.4	(normal)	Belkin AP in lounge, being tested
skullspace_classroom	G	(normal)	Linksys AP in classroom
Skullspace-dish-aimedatKingsHead	B	(normal)	east-pointed dish on fire escape ladder.
Skullspace-dish-aimedatSeccuris	B	(normal)	south-pointed dish on fire escape ladder that no one uses

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). Attempted 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, the latter is known for the low sensitivity and receiver quality of their chipsets.

Plans to increase coverage:

• upgrade 19dbi to 24dbi antenna - only issue is 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 - would be a good idea.
• check that the antenna and LMR cable/connections are running at full efficiency - this is old gear from a garage.

Signal in the North-main floor area is currently -82 to -87 when connection is possible, with all of the above it'd be good 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.

Main router Port Forwarding entries

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

Name	Port range	Protocol	Dest IP	Enabled?	Notes
russvent	3784	Both	.99	Y	-
mumd	22	TCP	.10	Y	-
russtot	993	TCP	.99	Y	-

internal IP usage

• 192.168.1.1 main Netgear router
• 192.168.1.3 Belkin F5D8236 Router in Lounge area
• 192.168.1.4 Cisco 1100AP (King's Head)
• 192.168.1.6 Intel 510T switch
• 192.168.1.7 Cisco 1100AP (south)
• 192.168.1.8 HP 300x? 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.21 Linksys AP in classroom
• 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

VOI IP usage

VOI gave us 206.220.196.48/28, you must reserve IPs here before using them. You'll need to plug into the new VOI-Static switch which I'll setup Thursday (feb 16) night.

• 206.220.196.49 - VOI MT RB750? Router.
• 206.220.196.50 - main sksp router soon
• 206.220.196.51 - main AW router soon
• 206.220.196.52 - Vobster SkullSpace Service
• 206.220.196.53 - Vobster Nepharia Service
• 206.220.196.54 - Andrew's VM server
• 206.220.196.55 - Andrew's VM server
• 206.220.196.56
• 206.220.196.57
• 206.220.196.58
• 206.220.196.59
• 206.220.196.60
• 06.220.196.61
• 06.220.196.62

Servers & Internet-connected devices

Main Skullspace router is always set to WAN MAC 00:01:01:01:01:01. IP is currently 206.220.194.202.

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

Name	Model/setup	IPs and MACs	Description/contact
Russ' Netbook	White Acer Netbook	192.168.1.99 / 00-23-8b-3f-f2-52	russmilne at gmail, do not open - short in hinges
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
Andrew's prime hunter 2	Dell Poweredge 1600SC	206.220.194.187 / 00:c0:9f:24:c0:2a	andrew AT andreworr DOT ca
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 ?
Alex's shiny server	Shiny case	206.220.194.204 / 00:50:8d:b4:1a:4c	alexwebr (a) gmail.com
Alex' Dell server	Dell Dimension 8250	206.220.194.166 / 00:50:5d:6c:5e:92	alexwebr (a) gmail.com
Stef's server	Whitebox PC?	206.220.194.143 / 1c:6f:65:c9:5f:e1	stefan.penner asign gmail.com
Mak's server	Dell PowerEdge R200	00:03:47:23:d4:f9/206.220.194.186 00:22:19:d4:eb:ea/206.220.194.250 00:22:19:d4:eb:eb/206.220.194.253	mak (a) kolybabi.com