1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Routing and subnetting

Discussion in 'Networking (Hardware & Software)' started by skylab, 2008/01/17.

  1. 2008/01/17
    skylab

    skylab Inactive Thread Starter

    Joined:
    2008/01/17
    Messages:
    1
    Likes Received:
    0
    Hi everyone, I have an issue i'd like some help with, i've never had to do this before and i'd like to get it right, i have a client who runs what use to be a small network and so we had set it up using the following address configuration 198.168.50.0/255.255.255.0 giving the ip address range from 0-255 using 2 to 254 , well he has now run out of address and i'd like to move him to the 191.168.0.0/255.255.192.0 subnet which should allow him for lots of room in the future.. how ever i cannot take his current network down i'm thinking of simply setting up the new clients on this network and using something like the linux router project to route traffic between the two i dont know if i'm going right so i'd like some suggestions and maybe a pointer in the right direction


    skylab.
     
  2. 2008/01/18
    ReggieB

    ReggieB Inactive Alumni

    Joined:
    2004/05/12
    Messages:
    2,786
    Likes Received:
    2
    Same sort of thing is discussed in this thread:

    http://www.windowsbbs.com/showthread.php?t=69380

    Yes. You can set up a router to allow traffic to be routed between the two subnets. Simplest thing is just to add the new subnet to the default gateway router - you shouldn't need another router. You will need to add a second IP address (on the new subnet) to the internal interface of the router.

    Personally, I'd strongly recommend you use 10.0.0.0/255.255.0.0 as that gives far more flexibility than a 192.168 address.

    So add 10.0.0.1 as a second IP address on your default gateway address. Reset DHCP to give out addresses on the 10.0.0.0 subnet instead of the 192.168.50.0 address. Set the router DHCP scope option to point at 10.0.0.1 as the default gateway. Then any statically defined systems over to 10.0.0.0 address - updating the local DNS addresses to suit. Also update DHCP scope options to point at new location for services such as WINS and DNS. You should also regularly check WINS and DNS during the transfer process, to make sure mappings are correct, and modify any that don't match the current set up.
     

  3. to hide this advert.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.