Re: Vlan Digest, Vol 7, Issue 3

"yerra srihari rao" <[email protected]>
Newsgroups gmane.linux.drivers.vlan
Message-ID <[email protected]> 
  Hi all,
I am new to vlan.I have some doubts with respect to vlan.
1) what is native vlan.
 2)I want to know IVR[Inter vlan Rounting].How this works .I have understood the how comunication happens within vlans.If possible tell me the URL regarding this.

Thanks and Regards.
Srihari.



On Sun, 20 Mar 2005 [email protected] wrote :
>Send Vlan mailing list submissions to
> 	[email protected]
>
>To subscribe or unsubscribe via the World Wide Web, visit
> 	http://www.lanforge.com/mailman/listinfo/vlan
>or, via email, send a message with subject or body 'help' to
> 	[email protected]
>
>You can reach the person managing the list at
> 	[email protected]
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of Vlan digest..."
>
>
>Today's Topics:
>
>    1. RE: VLAN ID range in Hexadecimal (Vishwas Manral)
>    2. RE: VLAN ID range in Hexadecimal (JOJAN)
>    3. RE: VLAN ID range in Hexadecimal (Vishwas Manral)
>    4. Unable to see Cisco Native VLAN on a BSD box (Johan Henes)
>    5. RE: Unable to see Cisco Native VLAN on a BSD box (Wojciech Tryc)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Fri, 18 Mar 2005 21:24:53 -0800
> From: "Vishwas Manral" <[email protected]>
>Subject: RE: [VLAN] VLAN ID range in Hexadecimal
>To: "Linux 802.1Q VLAN" <[email protected]>
>Message-ID:
> 	<[email protected]>
>Content-Type: text/plain;	charset="iso-8859-1"
>
>Cyprian,
>
>Vlan Id Ranges from 0 to 4095 = 0 to (2^12 - 1). In Hexadecimal it is equivalent to 0x0 to 0xFFF. You can probably use a calculator to do these basic calculations.
>
>Thanks,
>Vishwas
>________________________________________
> From: [email protected] [mailto:[email protected]] On Behalf Of Cyprian Clement
>Sent: Saturday, March 19, 2005 12:55 AM
>To: Linux 802.1Q VLAN
>Subject: [VLAN] VLAN ID range in Hexadecimal
>
>Hello Community,
>
>does anyone know the standard number of digits reserved for vlan in hexadecimal?. i.e. is it 3-digit or 4-digit number or more in hexadecimal?. All in is currently you can define up to 4096 vlans.
>
>As always, thanks in advance.
>
>Regards,
>
>Cyprian.
>-------------
>Send instant messages to your online friends http://uk.messenger.yahoo.com
>
>
>
>------------------------------
>
>Message: 2
>Date: Sat, 19 Mar 2005 13:18:09 +0530
> From: JOJAN <[email protected]>
>Subject: RE: [VLAN] VLAN ID range in Hexadecimal
>To: "'Linux 802.1Q VLAN'" <[email protected]>
>Message-ID: <[email protected]>
>Content-Type: text/plain;	charset="iso-8859-1"
>
>with 0 and FFF reserved, you can have only 4094 VLANs.
>
>-----Original Message-----
> From: [email protected]
>[mailto:[email protected]]On Behalf Of Vishwas Manral
>Sent: Saturday, March 19, 2005 10:55 AM
>To: Linux 802.1Q VLAN
>Subject: RE: [VLAN] VLAN ID range in Hexadecimal
>
>
>Cyprian,
>
>Vlan Id Ranges from 0 to 4095 = 0 to (2^12 - 1). In Hexadecimal it is
>equivalent to 0x0 to 0xFFF. You can probably use a calculator to do these
>basic calculations.
>
>Thanks,
>Vishwas
>________________________________________
> From: [email protected] [mailto:[email protected]] On
>Behalf Of Cyprian Clement
>Sent: Saturday, March 19, 2005 12:55 AM
>To: Linux 802.1Q VLAN
>Subject: [VLAN] VLAN ID range in Hexadecimal
>
>Hello Community,
>
>does anyone know the standard number of digits reserved for vlan in
>hexadecimal?. i.e. is it 3-digit or 4-digit number or more in hexadecimal?.
>All in is currently you can define up to 4096 vlans.
>
>As always, thanks in advance.
>
>Regards,
>
>Cyprian.
>-------------
>Send instant messages to your online friends http://uk.messenger.yahoo.com
>
>
>_______________________________________________
>Vlan mailing list
>[email protected]
>http://www.lanforge.com/mailman/listinfo/vlan
>
>
>---------------------------------------------------------------------------
>        "This e-mail and any files transmitted with it are for the sole use
>of the intended recipient(s) and may contain confidential and privileged
>information. If you are not the intended recipient, please contact the
>sender by reply e-mail and destroy all copies of the original message.
>
>        Any unauthorized review, use, disclosure, dissemination, forwarding,
>printing or copying of this email or any action taken upon this e-mail is
>strictly prohibited and may be unlawful."
>---------------------------------------------------------------------------
>
>
>------------------------------
>
>Message: 3
>Date: Sat, 19 Mar 2005 01:05:58 -0800
> From: "Vishwas Manral" <[email protected]>
>Subject: RE: [VLAN] VLAN ID range in Hexadecimal
>To: "Linux 802.1Q VLAN" <[email protected]>
>Message-ID:
> 	<[email protected]>
>Content-Type: text/plain;	charset="iso-8859-1"
>
>Good point. Actually VLAN 1 is reserved for internal use in most of the systems.
>
>-Vishwas
>
>-----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf Of JOJAN
>Sent: Saturday, March 19, 2005 1:18 PM
>To: 'Linux 802.1Q VLAN'
>Subject: RE: [VLAN] VLAN ID range in Hexadecimal
>
>with 0 and FFF reserved, you can have only 4094 VLANs.
>
>-----Original Message-----
> From: [email protected]
>[mailto:[email protected]]On Behalf Of Vishwas Manral
>Sent: Saturday, March 19, 2005 10:55 AM
>To: Linux 802.1Q VLAN
>Subject: RE: [VLAN] VLAN ID range in Hexadecimal
>
>
>Cyprian,
>
>Vlan Id Ranges from 0 to 4095 = 0 to (2^12 - 1). In Hexadecimal it is
>equivalent to 0x0 to 0xFFF. You can probably use a calculator to do these
>basic calculations.
>
>Thanks,
>Vishwas
>________________________________________
> From: [email protected] [mailto:[email protected]] On
>Behalf Of Cyprian Clement
>Sent: Saturday, March 19, 2005 12:55 AM
>To: Linux 802.1Q VLAN
>Subject: [VLAN] VLAN ID range in Hexadecimal
>
>Hello Community,
>
>does anyone know the standard number of digits reserved for vlan in
>hexadecimal?. i.e. is it 3-digit or 4-digit number or more in hexadecimal?.
>All in is currently you can define up to 4096 vlans.
>
>As always, thanks in advance.
>
>Regards,
>
>Cyprian.
>-------------
>Send instant messages to your online friends http://uk.messenger.yahoo.com
>
>
>_______________________________________________
>Vlan mailing list
>[email protected]
>http://www.lanforge.com/mailman/listinfo/vlan
>
>
>---------------------------------------------------------------------------
>        "This e-mail and any files transmitted with it are for the sole use
>of the intended recipient(s) and may contain confidential and privileged
>information. If you are not the intended recipient, please contact the
>sender by reply e-mail and destroy all copies of the original message.
>
>        Any unauthorized review, use, disclosure, dissemination, forwarding,
>printing or copying of this email or any action taken upon this e-mail is
>strictly prohibited and may be unlawful."
>---------------------------------------------------------------------------
>
>_______________________________________________
>Vlan mailing list
>[email protected]
>http://www.lanforge.com/mailman/listinfo/vlan
>
>
>
>
>------------------------------
>
>Message: 4
>Date: Sat, 19 Mar 2005 16:00:07 +0100
> From: "Johan Henes" <[email protected]>
>Subject: [VLAN] Unable to see Cisco Native VLAN on a BSD box
>To: "Linux 802.1Q VLAN" <[email protected]>
>Message-ID: <[email protected]>
>Content-Type: text/plain; charset="iso-8859-1"
>
>  Hi !
>I have set up a dot1q trunk between a Cisco switch and an OpenBSD 3.1 box. Everything works beautifully except of VLAN 1 which is default Native VLAN on the Cisco switch. I am not able to see traffic on this interface on the BSD box until I change Native VLAN on the switch to something else. This of course solves the problem, but I am just curious - is this correct behaviour ??
>
>I know that Native VLAN is untagged, but if I connect a Cisco router instead of the BSD box, Also VLAN 1 (native vlan) is reachable via a VLAN-subinterface on the router....
>
>(And I do of course see the traffic on the physical interface. it is just that i want it to go to the vlan-interface :-)
>
>Best regards,
>
>Johan
>-------------- next part --------------
>An HTML attachment was scrubbed...
>URL: http://www.lanforge.com/pipermail/vlan/attachments/20050319/b09944c8/attachment-0001.htm
>
>------------------------------
>
>Message: 5
>Date: Sat, 19 Mar 2005 10:24:00 -0500
> From: "Wojciech Tryc" <[email protected]>
>Subject: RE: [VLAN] Unable to see Cisco Native VLAN on a BSD box
>To: "Linux 802.1Q VLAN" <[email protected]>
>Message-ID:
> 	<[email protected]>
>Content-Type: text/plain; charset="us-ascii"
>
>VLAN 1 on Cisco is their default VLAN, thus only untagged frames will be
>processed (I believe). Your OpenBSD box creates Tagged frames on VLAN 1
>so it doesn't work. You could use assigned the IP address to the
>interface on top of creating subinterfaces (VLANs), then it should work
>as the non-vlan interface would send untagged packets.
>Am I Correct?
>Wojtek
>
>   _____
>
> From: Johan Henes [mailto:[email protected]]
>Sent: Saturday, March 19, 2005 10:00 AM
>To: Linux 802.1Q VLAN
>Subject: [VLAN] Unable to see Cisco Native VLAN on a BSD box
>
>
>  Hi !
>
>I have set up a dot1q trunk between a Cisco switch and an OpenBSD 3.1
>box. Everything works beautifully except of VLAN 1 which is default
>Native VLAN on the Cisco switch. I am not able to see traffic on this
>interface on the BSD box until I change Native VLAN on the switch to
>something else. This of course solves the problem, but I am just curious
>- is this correct behaviour ??
>
>I know that Native VLAN is untagged, but if I connect a Cisco router
>instead of the BSD box, Also VLAN 1 (native vlan) is reachable via a
>VLAN-subinterface on the router....
>
>(And I do of course see the traffic on the physical interface. it is
>just that i want it to go to the vlan-interface :-)
>
>Best regards,
>
>Johan
>
>-------------- next part --------------
>An HTML attachment was scrubbed...
>URL: http://www.lanforge.com/pipermail/vlan/attachments/20050319/7f217983/attachment-0001.htm
>
>------------------------------
>
>_______________________________________________
>Vlan mailing list
>[email protected]
>http://www.lanforge.com/mailman/listinfo/vlan
>
>
>End of Vlan Digest, Vol 7, Issue 3
>**********************************

_______________________________________________
Vlan mailing list
[email protected]
http://www.lanforge.com/mailman/listinfo/vlan
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.