VLAN setup and VLAN routing basics

I'm confused about VLAN routing. I'm using a 3Com 3870 (L3) switch to subnet my LAN from one /24 to 4 /24s. I've created the the 3 additional VLANs with their member ports (Membership is "untagged") . I've created 4 IP Interfaces using one VLAN per interface configured with the 4 /24 networks.
What I'm shooting for is:
VLANs 2,3, & 4 to see VLAN 1, but not each other.
Servers, DHCP, DNS etc. will all be on VLAN1. (VLAN 1 preexists as the Management VLAN with all ports as "untagged" members except those defined for VLANs 2,3,4)

This will be my core switch/router when the implementation is done.

The Router interface shows 4 valid routes that correspond to each subnet defined by the IP interfaces. What additional (static) route entries do I have to create to get the aforementioned configuration? I've tried several "stabs" at creating routes but the switch rejects them. "Failed to set route", which I take to mean I've entered some senseless data.

Input fields are:
Destination: host or network to route to
Subnet Mask:
Default Gateway: defined as the "next hop"
Metric: ?

First ; do I have my VLANs/IP Interfaces set up properly? - I think I do.
Foremost, what should my routing table look like?

I feel like I'm missing something simple. Would setting the IP interface for VLAN1 to a /22 help?

I've read all the VLAN/VLAN routing articles on this site and more...and It's just not sinking in.

If the router is showing the routes what more do you need?

Once packets get to the router the router knows where to send them because it has the routes.

The restriction of vlan access? That would be done with an access list typically, and not with the route.

Make sure your default gateways are set correctly on each subnet. Maybe thats throwing it off...

Thanks for the reply Todd,

All of the documentation I've read emphasizes that, by default, VLANs do no see each other. And IP routing must be enabled to facilitate this.

The router table shows 4 entries that have the status of 'local'.
Destination SubMask Metric Gateway Status State
192.168.0.0 /24 1 - - Local Valid
192.168.1.0 /24 1 - - Local Valid
192.168.2.0 /24 1 - - Local Valid
192.168.3.0 /24 1 - - Local Valid

It looks as if the router knows all of the networks but VLAN1 cannot ping anything on VLAN2 vice versa, etc, etc. ad infinitum.

As far as default gateways go, you can see from above that the routing table does not specify a default for any of the local route statements. These route statements are linked to each IP interface - so if I take an IP interface down - unplug the ethernet jack form the VLAN port, the route statement goes away.
Other than static route entries there is no where I would specify a default gateway for each subnet. ...and I'm not even sure what they would be? I can config a single default gateway for the router - but in a test environment I'm not sure what that would be either!

Do I create another VLAN and config the IP Interface as a /22 and make that Interface the default gateway? Can I just use the default VLANs IP interface as the default gateway?

I'm migrating from a single broadcast domain - so I'm used to flat topologies.

Ok i was a little off on what you wanted to know, this might help out more.

Each network is going to need a default gateway setup, in simple terms the default gateway is the router's interface on a specific network segment... yours might be...
192.168.0.1
192.168.1.1
192.168.2.1
192.168.3.1
This is an IP address on each network segment (vlan) that devices send traffic bound for another network (vlan). SO...

If pc01 (ip address 192.168.0.5) wants to talk to pc02 (ip address 192.168.1.5) it sees that ip address is not local so it send it to the default gateway (the router) the router recieves the packets and forwards it out to the correct network (vlan).

I don't know how to configure that on a 3Com switch... Maybe someone else can help out???

i've tried vlan using packet tracer..

when using the same ip on router..i can ping it..
but i cannot configure for the different ip
let say R1 and R2 with 192.168.10.1 and 192.168.10.2
i want R3 with the 192.168.30.X

here is the packet tracer that i practise..

&lt;a href=" www.fileden.com/files/2006/8/15/169199/3...1-01-08.pkt</a> ;

[/url]

thanks

The router needs to have multi - sub - interfaces configured one for each network you want to route to and from.

THIS IS NOT EXACT SYNTAX... I can't remember it right now, and i'm at work and can't dig it up...

int fa0/0

*don't put and ip address*

int fa0/0.1
encapsulation dot1q
ip address 192.168.1.1

int fa0/0.2
encapsulation dot1q
ip address 192.168.2.1

On the switch the you need to configure it as a trunk port.

I think I'm forgetting a step, but i'm at work and can't bang through it... Hopefully this gets you going.