Additional Subnet or Supernet?
Posted on 2011-09-16
We currently have a bit of a situation on our hands, as we only have 20 or so available IPs left in our network, and we're currently expanding into an office across the parking lot from our current office. My question is twofold, first, what would be the best practice for making additional addresses available? I've heard supernetting isn't a good idea because of the constraints of Ethernet when you have anything more than 254 hosts, and I'm also a bit reluctant to supernet because I'll have to go to all the statically configured machines to adjust their subnet masks. The current range for distribution on our Windows Server 2003 DHCP server is 10.30.0.90 to 10.30.0.200 with an exclusion zone in the middle from 10.30.0.160 to 169. I suppose I could make the new range 10.30.0.90 to 10.30.1.254, and then add exclusion zones to that, but is that a good idea? Or would I be better served by using an additional subnet with another router? We currently have a SonicWall TZ 170 Enhanced, and I'm not 100% sure how I would configure that, or what kind of additional router I should get. If I do go for another subnet, do I need another DHCP server? Does it need to be placed somewhere else? Are there any considerations for DNS?
Secondly, as far as connectivity goes, we currently have a point to point wireless connection between the two buildings. I didn't put this in and I'm a bit uncomfortable with it. As we expand, I think we may run into bandwidth issues. So my next question is, if I run fiber from one building to another, are there any special considerations? Is it like Ethernet where I can plug one fiber capable switch into another and then run it into our Ethernet switches? Any recommendations on what kind of switch/cabling to get?
Thanks for any help!