"22dcc3c1" (history) in projects: freebsd

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched hist:"22 dcc3c1" (Results 1 – 3 of 3) sorted by relevance

/freebsd/sbin/ifconfig/
H A D	ifbridge.c	22dcc3c1 Wed Jun 13 18:58:04 GMT 2007 Andrew Thompson <thompsa@FreeBSD.org> Add the vlan tag to the bridge route table. This allows a vlan trunk to be bridged, previously legitimate traffic was not passed as the bridge could not tell that it was on a different Ethernet segment. All non-tagged traffic is treated as vlan1 as per IEEE 802.1Q-2003 22dcc3c1 Wed Jun 13 18:58:04 GMT 2007 Andrew Thompson <thompsa@FreeBSD.org> Add the vlan tag to the bridge route table. This allows a vlan trunk to be bridged, previously legitimate traffic was not passed as the bridge could not tell that it was on a different Ethernet segment. All non-tagged traffic is treated as vlan1 as per IEEE 802.1Q-2003 22dcc3c1 Wed Jun 13 18:58:04 GMT 2007 Andrew Thompson <thompsa@FreeBSD.org> Add the vlan tag to the bridge route table. This allows a vlan trunk to be bridged, previously legitimate traffic was not passed as the bridge could not tell that it was on a different Ethernet segment. All non-tagged traffic is treated as vlan1 as per IEEE 802.1Q-2003 22dcc3c1 Wed Jun 13 18:58:04 GMT 2007 Andrew Thompson <thompsa@FreeBSD.org> Add the vlan tag to the bridge route table. This allows a vlan trunk to be bridged, previously legitimate traffic was not passed as the bridge could not tell that it was on a different Ethernet segment. All non-tagged traffic is treated as vlan1 as per IEEE 802.1Q-2003 22dcc3c1 Wed Jun 13 18:58:04 GMT 2007 Andrew Thompson <thompsa@FreeBSD.org> Add the vlan tag to the bridge route table. This allows a vlan trunk to be bridged, previously legitimate traffic was not passed as the bridge could not tell that it was on a different Ethernet segment. All non-tagged traffic is treated as vlan1 as per IEEE 802.1Q-2003 22dcc3c1 Wed Jun 13 18:58:04 GMT 2007 Andrew Thompson <thompsa@FreeBSD.org> Add the vlan tag to the bridge route table. This allows a vlan trunk to be bridged, previously legitimate traffic was not passed as the bridge could not tell that it was on a different Ethernet segment. All non-tagged traffic is treated as vlan1 as per IEEE 802.1Q-2003 22dcc3c1 Wed Jun 13 18:58:04 GMT 2007 Andrew Thompson <thompsa@FreeBSD.org> Add the vlan tag to the bridge route table. This allows a vlan trunk to be bridged, previously legitimate traffic was not passed as the bridge could not tell that it was on a different Ethernet segment. All non-tagged traffic is treated as vlan1 as per IEEE 802.1Q-2003 22dcc3c1 Wed Jun 13 18:58:04 GMT 2007 Andrew Thompson <thompsa@FreeBSD.org> Add the vlan tag to the bridge route table. This allows a vlan trunk to be bridged, previously legitimate traffic was not passed as the bridge could not tell that it was on a different Ethernet segment. All non-tagged traffic is treated as vlan1 as per IEEE 802.1Q-2003
/freebsd/sys/net/
H A D	if_bridgevar.h	22dcc3c1 Wed Jun 13 18:58:04 GMT 2007 Andrew Thompson <thompsa@FreeBSD.org> Add the vlan tag to the bridge route table. This allows a vlan trunk to be bridged, previously legitimate traffic was not passed as the bridge could not tell that it was on a different Ethernet segment. All non-tagged traffic is treated as vlan1 as per IEEE 802.1Q-2003 22dcc3c1 Wed Jun 13 18:58:04 GMT 2007 Andrew Thompson <thompsa@FreeBSD.org> Add the vlan tag to the bridge route table. This allows a vlan trunk to be bridged, previously legitimate traffic was not passed as the bridge could not tell that it was on a different Ethernet segment. All non-tagged traffic is treated as vlan1 as per IEEE 802.1Q-2003 22dcc3c1 Wed Jun 13 18:58:04 GMT 2007 Andrew Thompson <thompsa@FreeBSD.org> Add the vlan tag to the bridge route table. This allows a vlan trunk to be bridged, previously legitimate traffic was not passed as the bridge could not tell that it was on a different Ethernet segment. All non-tagged traffic is treated as vlan1 as per IEEE 802.1Q-2003 22dcc3c1 Wed Jun 13 18:58:04 GMT 2007 Andrew Thompson <thompsa@FreeBSD.org> Add the vlan tag to the bridge route table. This allows a vlan trunk to be bridged, previously legitimate traffic was not passed as the bridge could not tell that it was on a different Ethernet segment. All non-tagged traffic is treated as vlan1 as per IEEE 802.1Q-2003 22dcc3c1 Wed Jun 13 18:58:04 GMT 2007 Andrew Thompson <thompsa@FreeBSD.org> Add the vlan tag to the bridge route table. This allows a vlan trunk to be bridged, previously legitimate traffic was not passed as the bridge could not tell that it was on a different Ethernet segment. All non-tagged traffic is treated as vlan1 as per IEEE 802.1Q-2003 22dcc3c1 Wed Jun 13 18:58:04 GMT 2007 Andrew Thompson <thompsa@FreeBSD.org> Add the vlan tag to the bridge route table. This allows a vlan trunk to be bridged, previously legitimate traffic was not passed as the bridge could not tell that it was on a different Ethernet segment. All non-tagged traffic is treated as vlan1 as per IEEE 802.1Q-2003 22dcc3c1 Wed Jun 13 18:58:04 GMT 2007 Andrew Thompson <thompsa@FreeBSD.org> Add the vlan tag to the bridge route table. This allows a vlan trunk to be bridged, previously legitimate traffic was not passed as the bridge could not tell that it was on a different Ethernet segment. All non-tagged traffic is treated as vlan1 as per IEEE 802.1Q-2003 22dcc3c1 Wed Jun 13 18:58:04 GMT 2007 Andrew Thompson <thompsa@FreeBSD.org> Add the vlan tag to the bridge route table. This allows a vlan trunk to be bridged, previously legitimate traffic was not passed as the bridge could not tell that it was on a different Ethernet segment. All non-tagged traffic is treated as vlan1 as per IEEE 802.1Q-2003
H A D	if_bridge.c	22dcc3c1 Wed Jun 13 18:58:04 GMT 2007 Andrew Thompson <thompsa@FreeBSD.org> Add the vlan tag to the bridge route table. This allows a vlan trunk to be bridged, previously legitimate traffic was not passed as the bridge could not tell that it was on a different Ethernet segment. All non-tagged traffic is treated as vlan1 as per IEEE 802.1Q-2003 22dcc3c1 Wed Jun 13 18:58:04 GMT 2007 Andrew Thompson <thompsa@FreeBSD.org> Add the vlan tag to the bridge route table. This allows a vlan trunk to be bridged, previously legitimate traffic was not passed as the bridge could not tell that it was on a different Ethernet segment. All non-tagged traffic is treated as vlan1 as per IEEE 802.1Q-2003 22dcc3c1 Wed Jun 13 18:58:04 GMT 2007 Andrew Thompson <thompsa@FreeBSD.org> Add the vlan tag to the bridge route table. This allows a vlan trunk to be bridged, previously legitimate traffic was not passed as the bridge could not tell that it was on a different Ethernet segment. All non-tagged traffic is treated as vlan1 as per IEEE 802.1Q-2003 22dcc3c1 Wed Jun 13 18:58:04 GMT 2007 Andrew Thompson <thompsa@FreeBSD.org> Add the vlan tag to the bridge route table. This allows a vlan trunk to be bridged, previously legitimate traffic was not passed as the bridge could not tell that it was on a different Ethernet segment. All non-tagged traffic is treated as vlan1 as per IEEE 802.1Q-2003 22dcc3c1 Wed Jun 13 18:58:04 GMT 2007 Andrew Thompson <thompsa@FreeBSD.org> Add the vlan tag to the bridge route table. This allows a vlan trunk to be bridged, previously legitimate traffic was not passed as the bridge could not tell that it was on a different Ethernet segment. All non-tagged traffic is treated as vlan1 as per IEEE 802.1Q-2003 22dcc3c1 Wed Jun 13 18:58:04 GMT 2007 Andrew Thompson <thompsa@FreeBSD.org> Add the vlan tag to the bridge route table. This allows a vlan trunk to be bridged, previously legitimate traffic was not passed as the bridge could not tell that it was on a different Ethernet segment. All non-tagged traffic is treated as vlan1 as per IEEE 802.1Q-2003 22dcc3c1 Wed Jun 13 18:58:04 GMT 2007 Andrew Thompson <thompsa@FreeBSD.org> Add the vlan tag to the bridge route table. This allows a vlan trunk to be bridged, previously legitimate traffic was not passed as the bridge could not tell that it was on a different Ethernet segment. All non-tagged traffic is treated as vlan1 as per IEEE 802.1Q-2003 22dcc3c1 Wed Jun 13 18:58:04 GMT 2007 Andrew Thompson <thompsa@FreeBSD.org> Add the vlan tag to the bridge route table. This allows a vlan trunk to be bridged, previously legitimate traffic was not passed as the bridge could not tell that it was on a different Ethernet segment. All non-tagged traffic is treated as vlan1 as per IEEE 802.1Q-2003