FieldDayConfiguration

We will be using static routes, as most people have this concept nailed down. Since deployment of a routing protocol could prove to be messy for our first event, this is just how it will be Next field day will be a bit more complex, so i promise we will use a routing protocol then.

Our "routers" will be PC based. I would like suggestions as to how we can rate limit unauthorized clients, and leave our authorized gear (VoIP phones and streaming video) alone. We also need to filter some annoying applications such as audiogalaxy, etc. that could possibly kill our network. I hate to hound down on specific applications, but with an unknown number of people showing up with who-knows-what on their laptops, it would be nice to save our bandwidth for other purposes.

Regardless of who we use for outbound connectivity, it will end up being under 6mbits. This should leave lots of room for our 'local' services. If somebody gets wacky and donates a 100mbit connection, we should crank it down to leave us with ample wlan pipe for local stuff.

A proposal for this would be nice. - CaseyHalverson

Network Diagram

Network Diagram (jpg)

This is a model of what should be constructed.

Hardware

RG-1000s should be placed at each site to serve as an access point. These RG-1000s should also be running DHCP service.

Soekris4521 machines, which have arrived, will serve as routers. Someone needs to find or create a nice image we can fit on a flash. This unix-based disk should contain WLAN card drivers, routing abilities, basic filtering, running NoCat on ethernet interface, etc. I'm guessing the LinuxRouterProject would be a start, but someone research this.

IP Assignments

For IpAssignment, we will make use of the MobileNode block, which is 10.19.192-255

• 10.19.200.0/24 - Interface allocation block

  • 10.19.200.0/30 - SWN and SwnRelayPoint interfaces

    • 10.19.200.1- SWN

    • 10.19.200.2 - SwnRelayPoint

  • 10.19.200.4/30 - SwnRelayPoint and AlkiPark interfaces

    • 10.19.200.5 - SwnRelayPoint

    • 10.19.200.6 - AlkiPark

  • 10.19.200.8/30 - AlkiPark and MagnoliaPark interfaces

    • 10.19.200.9 - AlkiPark

    • 10.19.200.10 - MagnoliaPark

  • 10.19.200.12/30 - AlkiPark and VolunteerPark interfaces

    • 10.19.200.13 - AlkiPark

    • 10.19.200.14 - VolunteerPark

• 10.19.201.0/24 - AlkiPark

  • 10.19.201.1 - Router
  • 10.19.201.2-32 - Reserved for static hosts
  • 10.19.201.33-254 - DHCP Pool

• 10.19.202.0/24 - MagnoliaPark

  • 10.19.202.1 - Router
  • 10.19.202.2-32 - Reserved for static hosts
  • 10.19.202.33-254 - DHCP Pool

• 10.19.203.0/24 - VolunteerPark

  • 10.19.203.1 - Router
  • 10.19.203.2-32 - Reserved for static hosts
  • 10.19.203.33-254 - DHCP Pool

MagnoliaPark Routing Table

Site AlkiPark

Site VolunteerPark

Site SwnRelayPoint

(location still to be determined, will route between seattle wireless network and alki)

Site SeattleWirelessNodeVictim

(this will probably end up being tom's seattle wireless node, or perhaps eric's)

Services

• primary DNS: 10.19.201.3 (Alki)
• secondary DNS: 10.19.202.3 (Magonlia)
• dhcp server: 10.19.*.4

• fobbit VoipBlaster machine: 10.19.*.5

• video servers?