Re: cvs commit: src/sbin/ifconfig Makefile ifconfig.8 iflagg.c iftrunk.c src/share/man/man4 Makefile lagg.4 trunk.4 src/sys/modules Makefile src/sys/modules/if_lagg Makefile src/sys/modules/if_trunk Makefile src/sys/conf NOTES files ...
- From: Andrew Thompson <thompsa@xxxxxxxxxxx>
- Date: Thu, 19 Apr 2007 09:07:16 +1200
Please note the following change. trunk was only in HEAD for a week so
the few people who tried it out already need to be aware of the name
change.
Andrew
On Tue, Apr 17, 2007 at 12:35:11AM +0000, Andrew Thompson wrote:
thompsa 2007-04-17 00:35:11 UTC_______________________________________________
FreeBSD src repository
Modified files:
sbin/ifconfig Makefile ifconfig.8
share/man/man4 Makefile
sys/modules Makefile
sys/conf NOTES files
sys/sys priv.h
sys/net ieee8023ad_lacp.c ieee8023ad_lacp.h if.c
if_ethersubr.c if_var.h
Added files:
sbin/ifconfig iflagg.c
share/man/man4 lagg.4
sys/modules/if_lagg Makefile
sys/net if_lagg.c if_lagg.h
Removed files:
sbin/ifconfig iftrunk.c
share/man/man4 trunk.4
sys/modules/if_trunk Makefile
sys/net if_trunk.c if_trunk.h
Log:
Rename the trunk(4) driver to lagg(4) as it is too similar to vlan trunking.
The name trunk is misused as the networking term trunk means carrying multiple
VLANs over a single connection. The IEEE standard for link aggregation (802.3
section 3) does not talk about 'trunk' at all while it is used throughout IEEE
802.1Q in describing vlans.
The lagg(4) driver provides link aggregation, failover and fault tolerance.
Discussed on: current@
freebsd-net@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"
- Prev by Date: Re: rtentry and rtrequest
- Next by Date: Re: rtentry and rtrequest
- Previous by thread: rtentry and rtrequest
- Next by thread: wpi driver.
- Index(es):
Relevant Pages
- Re: uplinks and trunks
... We are not on any vlans yet just a flat layer 2 for now. ... only trunk vlans
that are needed and only have vlans that are ... switchport trunk native vlan2 on the uplink
port and I ended up losing ... (comp.dcom.sys.cisco) - Not seeing all VLANS
... The 2 2960's are not seeing all the VLANs and I can't work out why ... Port
Vlans allowed on trunk ... switchport trunk encapsulation dot1q ... (comp.dcom.sys.cisco) - Re: uplinks and trunks
... We are not on any vlans yet just a flat layer 2 for now. ... only trunk vlans
that are needed and only have vlans that are needed ... switchport trunk native vlan2 on
the uplink port and I ended up losing all ... (comp.dcom.sys.cisco) - Re: 802.1q tagging/untagging on Catalyst 2950
... 'vtp mode server' in order to create vlans for use on other switches. ... >
trunk port, all the frames the switch sends on that trunk have no VLAN ... > switchport
nonegotiate ... > Administrative private-vlan trunk encapsulation: ... (comp.dcom.sys.cisco) - Trunking vlan on 6500-Help Please.
... Here is what I have a core 6500 with an MSFC that is trunking all the ... want
to do is trunk vlan 442 to the 3550 without causing any problems. ... Here is the command
that I am using set trunk 8/12 vlan 142 type ... vlans will try and trunk over this..
... (comp.dcom.sys.cisco)
