Jump to content
  • Announcements

    • spinynorman

      Mandriva Official Documentation

      Official documentation for extant versions of Mandriva can be found at doc.mandriva.com.   Documentation for the latest release may take some time to appear there. You can install all the manuals from the main repository if you have Mandriva installed - files are prefixed mandriva-doc.
    • paul

      Forum software upgrade   10/29/17

      So you may have noticed the forum software has upgraded !!!
      A few things that have changed. We no longer have community blogs (was never really used) We no longer have a portal page.
      We can discuss this, and decide whether it is needed (It costs money) See this thread: Here
Johnny Ljunggren

Routing 192.168.0.0/16 net

Recommended Posts

Hello

 

Is it possible to route C nets?

 

I'm trying to get the IT department to add some routes so that our lab machines get access to a server in another network segment. However they are refusing and telling me they need to add routes for this one by one, and find it to be too much work. I want all networks 192.168.X.0 where X is 100-254 to go one way and the others to go wherever they need.

 

Are they right that C nets cannot be routed like

ip route 192.168.2.0 255.255.255.0 192.168.1.254

ip route 192.168.0.0 255.255.0.0 192.168.1.253

 

or something to that effect?

 

regards

Johnny

Share this post


Link to post
Share on other sites

Of course you can route the whole subnet, the problem might be that they might already be using the same IP range, and maybe is why they suggested doing it by host, rather than the whole subnet.

Share this post


Link to post
Share on other sites

I know it is possible to route the whole net. And it is correct that parts of the ip range is already in use, that is why I added the 192.168.2.0 route in the example.

There are only a few networks in use alread, and they are all below 192.168.100.0.

 

More schematic:

 

<IT servers> <-----> <IT Cloud> <----> <IT Switch> <-------> LAB Switch <------> LAB machines

 

I want the lab machines (192.168.100+ ) to access a couple of IT servers. LAB machines have default gw through LAB switch. LAB switch has default gw through IT Switch. The IT Switch connects to the IT servers through the IT cloud - which consists of any numbers of routers/routing switches.

 

My idea was to set gw on all the different IT switches so that traffic end up at the lab switch, unless specifically routed elsewhere on any of the switches.

 

Hmmm, not sure if this made things any clearer though :)

Share this post


Link to post
Share on other sites

Not really any clearer :)

 

But yes, if some of the subnets are in use on the other side, this will be why they want to add them at host level, and not by the whole subnet and it is a bit of work, but not that much depending on number of hosts, etc, and where they have to put the routes - typically probably just one router.

 

Unless they are layer 3 switches, it won't matter in changing the gateway on the switches. They won't be doing any routing for you.

 

You could always try if you have a spare machine with two network cards, making your own router and put it between your lab switch and IT switch so that the lab machines can access the IT server that you need. Just an idea, it might solve the problem without having to involve the IT department. Then you can control all the routes yourself from your lab :)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×