Re: Vlan Digest, Vol 8, Issue 17

Response within,

On Fri, 2005-04-22 at 12:00 -0700, [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: tagging packets (Peter Stuge)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Fri, 22 Apr 2005 03:19:44 +0200
> From: Peter Stuge <[email protected]>
> Subject: Re: [VLAN] tagging packets
> To: [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=us-ascii
> 
> On Thu, Apr 21, 2005 at 12:43:25PM -0400, Patrice Seyed wrote:
> > Hi,
> > 
> > I am using a 2.4.21-4 kernel so it has 8021q compiled in as a module.
> > My purpose of using vlan is to tag packets with a specific vlan id,
> > which are destined for particular vlans, 2258 and 20 (both set up on
> > the switch), from the interface level; here being eth0:0 to go to
> > vlan 20 and eth0:1 destined for vlan 2258. Is there a way to do this
> > with vconfig? I don't see options for doing this in the docs. 
> > 
> > Also when I followed the instructions on creating a vlan at
> > http://scry.wanfear.com/~greear/vlan/howto.html the command:
> > 
> > vconfig add eth0 2
> > 
> > 
> > creates an interface/vlan called eth0.2 and not vlan002. (I just want
> > to ask if this is expected behavior). 
> 
> You can control the interface naming scheme with vconfig too. Run
> vconfig without parameters and check the set_name_type command, but
> the naming scheme is only important if you have multiple VLANs with
> the same id connected to different NICs in the Linux system, if you
> only have one "set" of VLAN ids, any naming scheme will work.
> 
> You have the DEV_PLUS_VID_NO_PAD scheme active, which makes ethx.vid
> style interfaces.
> 
> Run
> vconfig add eth0 20
> vconfig add eth0 2258
> 
> and the VLANs 20 and 2258 will be reachable on the respective
> interfaces created.

Thanks for the tips, still not quite getting it to go. Does vconfig
handle ip aliasing ok? As you may have noticed eth0:0 and eth0:1 are the
same interface but "virtual" interfaces so i can have 2 ip addresses.

When i tried (per the howto and considering the aliasing):
ifconfig eth0:0 0.0.0.0 up
It complained:
SIOCSIFFLAGS: Cannot assign requested address
SIOCSIFFLAGS: Cannot assign requested address

at this point there are no interfaces besides lo showing in "ifconfig
-a". 

and also when i tried:
vconfig add eth0:0 20
it complained:
ERROR: trying to add VLAN #20 to IF - :eth0:0: - error: invalid argument


-Patrice
> 
> 
> //Peter
> 
> ------------------------------
> 
> _______________________________________________
> Vlan mailing list
> [email protected]
> http://www.lanforge.com/mailman/listinfo/vlan
> 
> 
> End of Vlan Digest, Vol 8, Issue 17
> ***********************************