Skip site navigation (1)Skip section navigation (2)

Site Navigation

PRs for tag 'lagg'

This is an experimental report containing PRs for tag 'lagg' as of 5-30-2014. GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '[<tagname>]' to the Synopsis field. Consider this a prototype of a better search function.

This report is generated statically.

Please give feedback on this report to Thanks.

PRs for tag 'lagg':
p2014/04/25kern/189003asomers[lagg] Page fault in lacp_req() while the lagg is being destroyed
o2014/01/21kern/185967net[lagg] [patch] Link Aggregation LAGG: LACP not working in 10.0
o2013/09/08kern/181931net[vlan] [lagg] vlan over lagg over mlxen crashes the kernel
o2013/06/19kern/179733net[lagg] [patch] interface loses capabilities when protocol changes
o2013/02/15kern/176167net[ipsec][lagg] using lagg and ipsec causes immediate panic
o2011/07/06kern/158694net[ix] [lagg] ix0 is not working within lagg(4)
o2011/05/19kern/157182net[lagg] lagg interface not working together with epair interface on bridge
p2011/04/30kern/156743thompsa[lagg] [patch] if_lagg should not treat vlan-tagged frames as LACP frames
o2011/04/06kern/156226net[lagg]: failover does not announce the failover to switch
o2010/04/15kern/145728net[lagg] Stops working lagg between two servers.
f2010/01/09kern/142518net[em] [lagg] Problem on 8.0-STABLE with em and lagg
o2009/09/24kern/139117net[lagg] + wlan boot timing (EBUSY)
o2009/07/24kern/137089net[lagg] lagg falsely triggers IPv6 duplicate address detection
o2008/04/30kern/123279thompsa[lagg] order of operations dependancy in bringing up lagg interface breaks at-boot configuration
o2008/04/21kern/122954net[lagg] IPv6 EUI64 incorrectly chosen for lagg devices
f2008/04/15kern/122780net[lagg] tcpdump on lagg interface during high pps wedges netcode
16 problems total.

Bugs can be in one of several states:

o - open
A problem report has been submitted, no sanity checking performed.
a - analyzed
The problem is understood and a solution is being sought.
f - feedback
Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution.
p - patched
A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open.
r - repocopy
The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion.
s - suspended
The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended.
c - closed
A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned.