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

Site Navigation

PRs for tag 'vlan'

This is an experimental report containing PRs for tag 'vlan' as of 4-20-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 'vlan':
o2014/04/03kern/188245net[vlan] Critical vlan problem with OpenBGP
o2014/03/11kern/187451net[vlan] [carp] Some vlans in bridge + carp result in hung server
o2013/11/14kern/183970net[ofed] [vlan] [panic] mellanox drivers and vlan usage causes kernel panic and reboot
o2013/09/08kern/181931net[vlan] [lagg] vlan over lagg over mlxen crashes the kernel
o2012/02/19kern/165296net[vlan] [patch] Fix EVL_APPLY_VLID, update EVL_APPLY_PRI macro
o2011/04/14kern/156408net[vlan] Routing failure when using VLANs vs. Physical ethernet interfaces.
o2011/03/09kern/155420net[vlan] adding vlan break existent vlan
o2011/01/16conf/154062net[vlan] [patch] change to way of auto-generatation of vlan devices based on the chosen parent device
o2010/11/11kern/152141net[vlan] [patch] encapsulate vlan in ng_ether before output to if
f2010/05/08kern/146394net[vlan] IP source address for outgoing connections
o2010/05/06kern/146358net[vlan] wrong destination MAC address
p2010/01/18kern/142927thompsa[vlan] [patch] handle parent interface link layer address changes in if_vlan(4)
o2009/12/21kern/141843jfv[em] [vlan] Intel txcsum and assigned vlan invoke wrong dst MAC in TCP packets
f2009/11/17kern/140634net[vlan] destroying if_lagg interface with if_vlan members causing 100% usage by ifconfig
o2008/08/27kern/126874net[vlan]: Zebra problem if ifconfig vlanX destroy
o2008/03/06kern/121437net[vlan] Routing to layer-2 address does not work on VLAN interface
o2007/10/23kern/117423net[vlan] Duplicate IP on different interfaces
17 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.