Commit Graph

14 Commits

Author SHA1 Message Date
Andrew Thompson
f2ff5b0672 Break the last part to its own sentence rather than a run-on.
Suggested by:	dougb
2012-02-23 23:37:29 +00:00
Andrew Thompson
3122b9120c Add a sysctl/tunable default value for the use_flowid sysctl in r232008. 2012-02-23 21:56:53 +00:00
Andrew Thompson
6f9c725237 Document the net.link.lagg.X.use_flowid sysctl from r232008. 2012-02-22 22:29:23 +00:00
Andrew Thompson
95bfa2fc22 Make it clear that fec is just an alias 2012-02-22 22:09:17 +00:00
Xin LI
145e5188c9 Clarify that lagg(4) sends/receives on active port, not the master port.
Note that this still seems to be a little bit confusing as the concept of
"master" is different from what people would expect on a networking
equipment.
2010-10-19 17:49:55 +00:00
Xin LI
7adc700072 Document net.link.lagg.failover_rx_all.
MFC after:	1 week
2010-10-08 21:29:48 +00:00
Christian Brueffer
f885252242 Fix typo. 2009-03-29 21:08:48 +00:00
Sam Leffler
50959dc8d4 remove bogus nwid use; that's a compat shim for netbsd 2009-03-29 18:14:45 +00:00
Sam Leffler
c01c776a52 fix wired-wireless failover example and remove incorrect
comment about WPA not working
2009-03-29 18:05:04 +00:00
Gabor Kovesdan
b0a4e26843 - This driver will first appear in FreeBSD 6.3, not 7.0
Submitted by:	thompsa
MFC after:	0 days
2008-01-08 15:36:06 +00:00
Andrew Thompson
de75afe64f - Propagate the largest set of interface capabilities supported by all lagg
ports to the lagg interface.
- Use the MTU from the first interface as the lagg MTU, all extra interfaces
  must be the same.

This fixes using a lagg interface for a vlan or enabling jumbo frames, etc.

Approved by:	re (kensmith)
MFC After:	3 days
2007-07-30 20:17:22 +00:00
Christian Brueffer
e8ade79df5 Bump date for the previous revision and the driver renaming. 2007-04-17 07:09:23 +00:00
Christian Brueffer
caf51cfbf4 To avoid confusion, mention that the driver was originally called trunk
in OpenBSD.
2007-04-17 07:08:18 +00:00
Andrew Thompson
18242d3b09 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@
2007-04-17 00:35:11 +00:00