Re: Configure InterVLAN

On Mar 27, 9:11 am, News Reader <u...@xxxxxxxxxxx> wrote:
hhs:

Here is a response I post a day or two ago to a similar question (the IP
addresses relate to the other person's scenario), in a different newsgroup:

VLANs are isolated from one another. To communicate between VLANs, you
must use interVLAN routing.

You configure a trunk port (e.g.: 802.1Q) on the switch and connect it
to a router that has been configured with sub interfaces (e.g.: one
sub-interface configured as 192.168.142.1, the other 192.168.143.1).
These addresses would be the default gateway addresses of their
respective VLANs.

Lets say your VLAN IDs were 142 and 143, and you wanted to access a
server on VLAN 143, from a host on VLAN 142.

The host determines that the server is not on the same network by
applying the network mask to both addresses, and doing a comparison. The
host forwards a packet to it's default gateway (192.168.142.1). The
switch tags the packet with VLAN ID 142 (e.g.: 4 byte 802.1Q header) and
forwards it over the trunk to the router.

The router receives the packet, strips of the VLAN tag, looks at its
routing table and determines that it does have a route to the server via
sub-interface 192.168.143.1. The packet is tagged by the router with
VLAN ID 143, and forwarded over the trunk. The switch strips off the
VLAN tag, and forwards the packet to the server.

When the server responds, it uses its mask comparison to conclude that
the host is on another network, and that it therefore needs the
assistance of its default gateway which is at 192.168.143.1. It sends a
response packet to the host. This packet will be tagged by the switch
with VLAN ID 143, and forwarded to the router. The router will strip off
the tag, do a route lookup, re-tag the packet with VLAN ID 142 and
forward it out the trunk (via sub-interface 192.168.142.1). The switch
will remove the tag and forward it to the host.

Note that a "single" packet being sent between the host and server, has
to traverse the trunk "twice".

Host to router, then router to server.

The penalty for using VLANs, is the increased utilization of the
physical link between the switch and the router (i.e. the trunk).

Best Regards,
News Reader

hhs wrote:
Dear All,

I wonder, is it possible to configure different VLAN to talk to each
other without a Router? Is that possible by doing a layer 3 switch?

Thanks,

Definitely agree with News Reader, although having a layer 3 switch
keeps all that within the same network device (at least at a small
level). As soon as you include routers and trunking, News Reader is
100% right, which also starts to show the reasoning behind the trend
towards distributed layer 3 and the slow elimination of vlan trunking
in large enterprises (other than between access switch pairs for
redundant connections to individual servers).
.

Relevant Pages

  • Re: router causing ssh etc. slowdown?
    ... >> port on their public IP from a host on their own LAN. ... Let's say host A starts a TCP connection from its ... The router sends the SYN packet to ...
    (Fedora)
  • Re: NetGear RP614 wont stealth port 12345, 54321
    ... The probing host may then ... that's how one can say it; technically: if a port is called ... your Computer can just throw away the incoming packet without ... the packet comes via NET to router, who knows, whom to send the packet ...
    (comp.security.firewalls)
  • Re: Configure InterVLAN
    ... Lets say your VLAN IDs were 142 and 143, and you wanted to access a server on VLAN 143, from a host on VLAN 142. ... The host determines that the server is not on the same network by applying the network mask to both addresses, ... forwards it over the trunk to the router. ... The router receives the packet, strips of the VLAN tag, looks at its routing table and determines that it does have a route to the server via sub-interface 192.168.143.1. ...
    (comp.dcom.sys.cisco)
  • Re: A question about Multiple Routers with a Single MLS Catalyst
    ... have MLS-capable router, and MLS-capable switch, first packet goes through ... the router, and then router sends "instructions" to the switch how to handle ... Host-A is still located in the Red VLAN and Host-B is still ...
    (comp.dcom.sys.cisco)
  • Large IP Block = Lots of ARP traffic
    ... and is routed by a single router. ... so each host is seeing a TON of ARP traffic. ... the amount of ARP it had to do I could stretch the life of the router. ... Wouldnt every VLAN still see every ARP because they go out to ...
    (comp.dcom.sys.cisco)