Multiple Internal networks

[alanhs]

Hi, I wonder if someone could point me in the right direction on this?

I have to build a configuration for a Cisco router that will allow my internal machines to live on a number of separate networks, e.g. a bunch of machines on 192.168.1.x and another bunch on 192.168.2.x etc. Using Secondary addresses on the internal interface is possible, but I am not really sure its the correct solution. This is a new setup so I have complete control of the choices on how to do this.

Thanks for any insight you can provide!
Alan

 

[ADB100]

Use routing......

This is a pretty dumb question and I'll apologise in advance Alan, but if you can't grasp this then you shouldn't really be in 'complete control' of a networking solution (again sorry but you posted the question).

A router (Cisco or any other vendor) ROUTES IP packets based on the destination IP address. In simple terms if a packet comes into an interface then it examines the destination address and decides where to forward it. To do this it has (or builds) a routing table with destination network addresses (subnets, supernets or a default route) and next-hops (or in some cases interfaces).

In your scenario I would suggest a Layer-3 switch(es) to handle your multiple networks and possible more switches to attach your workstations and then either a firewall (ASA) or a router with the Firewall feature set as the edge router to the Internet. The routing configuration will be pretty simple as would the Internet connection (NAT/PAT & Inspection rules etc).

Secondary IP addressing is (and always has been) a workaround solution and NOT something you would put it from day one.

Andy

 

[tjbradford]

I think the question can only answered if we know which cisco router it is and are you using that regardless.

this will give you different design's depending on what it is capable of and if your happy to bin it for a higher spec'ed model ?