[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-vlan
Subject:    [VLAN] Release 0.0.11 is now posted.
From:       Ben Greear <greearb () candelatech ! com>
Date:       2000-04-23 21:37:48
[Download RAW message or body]

Sumary:
	*  WARNING:  The ioctl structure changed, so you'll need to (re)compile
	   the new vconfig or nasty things will happen to you...
	*  Took out link-aggregation hack.
	*  Default behavior is to only accept VLAN pkts from the device (port)
	   the VLAN is bound to.  This has not been adequately tested due to
	   my limited setup.
	*  Added ability to dynamically switch between 4 different naming schemes.
	   Basically, you can get:  vlan0005, vlan5, eth0.5 eth0.0005
           (see below for the details)  Adding others won't be hard.
	   Default is still vlan0005
	*  Allow dynamic switching between 4096 VLANs per box, and 4096 VLANs
	   per ethernet device.  The default is per box, and the current values
	   can be read out of /proc/net/vlan/config
	*  Allow mapping of VLAN QOS -> sk_buff->priority on ingress.
	   Allow mapping of sk_buff->priority -> VLAN QOS on egress.  Note
	   that due to the difference in significant bits, the mapping may
	   not be symetric.  This was not tested well either, please let me
	   know what you find...
	*  Using Patrick's patch, the 2.3 patch is now compatible with 2.3.99pre-5
	   I did see something wierd though:  Could ping A to B, and all was well,
	   but B could not ping A.  However, could telnet from B to A!!  Later,
	   everything started working....  Even when it wasn't working, according
	   to tcpdump, the packets were going to and fro, and were not corrupted.
	   So, there may be a problem, but I'll be damned if I can figure out
	   what it is!!

Here's the new vconfig usage:


    Usage: add             [interface-name] [vlan_id]
           rem             [vlan-name]
           set_dflt        [interface-name] [vlan_id]
           add_port        [port-name]      [vlan_id]
           rem_port        [port-name]      [vlan_id]
           set_egress_map  [vlan-name]      [skb_priority]   [vlan_qos]
           set_ingress_map [vlan-name]      [skb_priority]   [vlan_qos]
           set_name_type   [name-type]
           set_bind_mode   [bind-type]

    * The [interface-name] is the name of the ethernet card that hosts
      the VLAN you are talking about.
    * The port-name is the name of the physical interface that a VLAN
      may be attached to.
    * The vlan_id is the identifier (0-4095) of the VLAN you are operating on.
    * skb_priority is the priority in the socket buffer (sk_buff).
    * vlan_qos is the 3 bit priority in the VLAN header
    * name-type:  VLAN_PLUS_VID (vlan0005), VLAN_PLUS_VID_NO_PAD (vlan5),
                  DEV_PLUS_VID (eth0.0005), DEV_PLUS_VID_NO_PAD (eth0.5)
    * bind-type:  PER_DEVICE  # Allows vlan 5 on eth0 and eth1 to be unique.
                  PER_KERNEL  # Forces vlan 5 to be unique across all devices.

Enjoy, and let me know how it treats you!
Ben

-- 
Ben Greear (greearb@candelatech.com)  http://www.candelatech.com
Author of ScryMUD:  scry.wanfear.com 4444        (Released under GPL)
http://scry.wanfear.com               http://scry.wanfear.com/~greear

_______________________________________________
VLAN mailing list  -  VLAN@Scry.WANfear.com
http://www.WANfear.com/mailman/listinfo/vlan
VLAN Page:  http://scry.wanfear.com/~greear/vlan.html

[prev in list] [next in list] [prev in thread] [next in thread]