From Interlock Rochester Wiki
I would like to take the lead on this. I want to ask at the next meeting what people's needs are for network(s) and bandwidth [I know personally I'd like to play with some high bandwidth VoIP stuff, so the more bandwidth we can afford the better, imo] and see if what we have outlined on the Infrastructure page meshes with what everyone else was thinking. ---- BW 20:20, 2 December 2009 (UTC)
Care to tag-team this? --Fvox13 14:05, 3 December 2009 (UTC)
Help is always appreciated, Carl mentioned wanting to help as well. ---- BW 15:04, 3 December 2009 (UTC)
Ben, looks like you've got a good handle on this. Nicely detailed proposals. Thanks for stepping up to lead this.
The chief thing that springs to mind with regard to the RFC1918 address space allocations is that consumer level devices, which I think it's safe to say we'll have on hand at one time or another, typically use at least two of those ranges preferentially. Apple Airport base stations tend to use addresses in the 10.0.0.0/8 range, and non-Apple devices often plop themselves down in the 192.168.0.0/16 range.
My suggestion, then, is to use 172.16.0.0/12 range for all of our private networks. That way, if something shows a 192.168.x.y or 10.x.y.z address, we'll know right away that it's coming from something other than our stuff.
In that light, I propose 172.20.x.y for the production network, partitioned further as you suggest (perhaps spacing things out by 10s in the third octet instead of by 1s, to give some room in between), 172.30.x.y for the warzone. The mnemonic I have in mind for this is that .20 is an "even" multiple of 10, even meaning "smooth" and smooth being what one wants from a production environment. In contrast, .30 is an "odd" multiple of 10, odd being exciting, unusual, or even dangerous, depending on one's perspective, but certainly what one would expect from a "warzone". In between these two we'd have 172.25.x.y, which would be the playground--not expected to be at all dangerous, but you must be this tall to enter this ride.
The 10.0.0.0/8 space is pretty big, even if Apple does use part of it. From what I recall and can tell from a quick search, they tend to use 10.0.1.x addresses. I think it might be a good convention to pick some portion of the 10.0.0.0/8 space and then to recommend that people use it for setting up their own independent test networks, eg, if they are building a private network on a single hardware host to use with a collection of virtual machines on that host. If their stuff stays on their own network, no big deal. If they screw up somehow and one of their devices ends up on our network, again, it'll be easy to tell because it is in this distinct 10.0.0.0 region. I think 10.100.0.0 would be easy to remember to use, and well away from Apple's use.
Within 192.168.0.0, I've seen use all over the range. Some devices I've had use 192.168.0.x range. Some 192.168.254.x. The Linksys NSLU2 "slugs" use 192.168.1.77. And those are just the ones I'm familiar with and can recall off the top of my head. So, I think we just leave this for use with those devices.
Anyway, that's my suggestion, based on my experience. You may have experience with devices that tend to default to 172.16.0.0 too, making this a less useful scheme, for instance.
Deejoe 16:07, 5 December 2009 (UTC)
Thanks much for the feedback Deejoe. I like your ideas. I don't know of any devices that are using the 172.x.x.x range by default so that all sounds good.
Also, Fvox13, good point about Cat6a. Lets shoot for Cat6 with the expectation that we will probably end up with a bunch of cat5e and limited cat6, which we'll probably want to use for core equipment that doesn't have other interconnects. ---- BW 00:37, 6 December 2009 (UTC)
I am going to put the questions about the environment and power over into this talk section, so we can try and clean up the main page a little bit more. Cmd3187 18:22, 8 December 2009 (UTC)
- What is the capacity of the power system the space on?
- Is it shared with other tenants?
- What kind of emergency power/lighting does the building have?
- Is it our responsibility or the landlord's to increase/change electrical capacity?
- Do we have access to the electrical panel or disconnect/fuses from within the space?
- Can we run our own conduit/wall boxes? (Wall conduit to comply with fire code)
- How is the space heated in the winter?
- How is the space cooled in the summer?
- What is the RG&E budget for the space (assuming it can give some indication of the cost of heating/cooling)?
- Will humidity be a problem?