+ Post New Thread
Results 1 to 5 of 5
Wired Networks Thread, Expanding our IP range - possibly a stupid question in Technical; Ok...we have 3 sites, all currently with a class C /24 address range: Site A - 192.168.1.0/24 Site B - ...
  1. #1

    Join Date
    Jul 2006
    Location
    London
    Posts
    2,962
    Thank Post
    159
    Thanked 152 Times in 116 Posts
    Rep Power
    49

    Expanding our IP range - possibly a stupid question

    Ok...we have 3 sites, all currently with a class C /24 address range:

    Site A - 192.168.1.0/24
    Site B - 192.168.5.0/24
    Site C - 192.168.10.0/24

    Each giving 254 hosts per site. None have run out yet, but site A is the most likely to (site B & C very unlikely)

    By supernetting, and changing the subnet mask to /23 I can expand to 510 hosts per subnet right? So 192.168.0.1 - 192.168.1.254 in site A? But if I do this for site A, would I have to do ir for the other sites and any future sites/VLANs too? Or could the others stay on /24?

    Or would an easier solution be to have both 192.168.1.0/24 and 192.168.2.0/24 for site A and route between them?

  2. #2

    Join Date
    May 2012
    Posts
    26
    Thank Post
    1
    Thanked 7 Times in 6 Posts
    Rep Power
    6
    If it is the same site and the same scope I would change it to a /23. If you can segment your network for servers, printers, wireless, etc I would create a separate VLAN, but a /23 network is acceptable for computers. Any more than that and I would recommend segmenting for performance.

    If you change your subnet to a /23 you would have 192.168.1.0-192.168.2.255 (1.0 being the network address and 2.255 being the broadcast address).

    The other sites could all stay at /24. This change would not effect their networks. You will have to change all the subnet masks for your devices at Site A either manually or via DHCP (don't forget printers, servers, statically assigned devices). And you will have to update the routes between your sites to reflect the network change. Are you routed statically, eigrp, ospf, etc?
    Last edited by SuperfluousAdjective; 4th December 2012 at 03:01 PM.

  3. #3

    Join Date
    Jul 2006
    Location
    London
    Posts
    2,962
    Thank Post
    159
    Thanked 152 Times in 116 Posts
    Rep Power
    49
    Thanks for that.

    I guess I will weigh up the options - change the subnet or VLAN....certainly isn't needed quite yet, it was more I was wondering about the compatibility with the other sites.

    Tbh it might actually be less work to create a VLAN for clients on 192.168.2.0/24

    Also in answer to your question, we're routed statically

  4. #4

    FN-GM's Avatar
    Join Date
    Jun 2007
    Location
    UK
    Posts
    15,843
    Thank Post
    876
    Thanked 1,679 Times in 1,459 Posts
    Blog Entries
    12
    Rep Power
    444
    I would just make another vlan than making your current ranges larger. It will help with broadcast traffic.

  5. #5

    Join Date
    May 2012
    Posts
    26
    Thank Post
    1
    Thanked 7 Times in 6 Posts
    Rep Power
    6
    Quote Originally Posted by sidewinder View Post
    Thanks for that.

    I guess I will weigh up the options - change the subnet or VLAN....certainly isn't needed quite yet, it was more I was wondering about the compatibility with the other sites.

    Tbh it might actually be less work to create a VLAN for clients on 192.168.2.0/24

    Also in answer to your question, we're routed statically
    Just as a side note if you create a separate vlan you would have to make sure to manually forward DHCP traffic back to your DHCP server (with an additional scope) within your layer 3 device. Not difficult, but thought I'd mention it in case you found it useful. That's pretty much the only catch of adding a vlan on a basic network. Obviously the broadcast traffic will not span across the two networks so make sure to mitigate any issues with that. And with only three routers it isn't too big of a deal to update a statically routed network and the commands for your devices should be easy to find or replicate by looking at the running config.
    Last edited by SuperfluousAdjective; 4th December 2012 at 05:00 PM.

SHARE:
+ Post New Thread

Similar Threads

  1. Extending our current ip range
    By dsk in forum Wireless Networks
    Replies: 17
    Last Post: 20th February 2009, 01:32 PM
  2. Expanding our core switch?
    By sidewinder in forum Wireless Networks
    Replies: 10
    Last Post: 19th October 2007, 11:19 AM
  3. Replies: 9
    Last Post: 12th August 2007, 01:35 PM
  4. Extending IP Range
    By Grommit in forum Windows
    Replies: 12
    Last Post: 17th November 2006, 04:59 PM
  5. Replies: 2
    Last Post: 12th October 2006, 12:44 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •