Searched hist:"6 c23e6cc" (Results 1 – 1 of 1) sorted by relevance
| /freebsd/sys/net/ |
| H A D | if_ethersubr.c | 6c23e6cc Mon Feb 14 08:29:42 GMT 2005 Ruslan Ermilov <ru@FreeBSD.org> If no vlan(4) interfaces are configured for the interface, and the
driver did VLAN decapsulation in hardware, we were passing a frame
as if it came for the parent (non-VLAN) interface. Stop this from
happening.
Reminded by: glebius
Security: This could pose a security risk in some setups
6c23e6cc Mon Feb 14 08:29:42 GMT 2005 Ruslan Ermilov <ru@FreeBSD.org> If no vlan(4) interfaces are configured for the interface, and the
driver did VLAN decapsulation in hardware, we were passing a frame
as if it came for the parent (non-VLAN) interface. Stop this from
happening.
Reminded by: glebius
Security: This could pose a security risk in some setups
6c23e6cc Mon Feb 14 08:29:42 GMT 2005 Ruslan Ermilov <ru@FreeBSD.org> If no vlan(4) interfaces are configured for the interface, and the
driver did VLAN decapsulation in hardware, we were passing a frame
as if it came for the parent (non-VLAN) interface. Stop this from
happening.
Reminded by: glebius
Security: This could pose a security risk in some setups
6c23e6cc Mon Feb 14 08:29:42 GMT 2005 Ruslan Ermilov <ru@FreeBSD.org> If no vlan(4) interfaces are configured for the interface, and the
driver did VLAN decapsulation in hardware, we were passing a frame
as if it came for the parent (non-VLAN) interface. Stop this from
happening.
Reminded by: glebius
Security: This could pose a security risk in some setups
6c23e6cc Mon Feb 14 08:29:42 GMT 2005 Ruslan Ermilov <ru@FreeBSD.org> If no vlan(4) interfaces are configured for the interface, and the
driver did VLAN decapsulation in hardware, we were passing a frame
as if it came for the parent (non-VLAN) interface. Stop this from
happening.
Reminded by: glebius
Security: This could pose a security risk in some setups
6c23e6cc Mon Feb 14 08:29:42 GMT 2005 Ruslan Ermilov <ru@FreeBSD.org> If no vlan(4) interfaces are configured for the interface, and the
driver did VLAN decapsulation in hardware, we were passing a frame
as if it came for the parent (non-VLAN) interface. Stop this from
happening.
Reminded by: glebius
Security: This could pose a security risk in some setups
6c23e6cc Mon Feb 14 08:29:42 GMT 2005 Ruslan Ermilov <ru@FreeBSD.org> If no vlan(4) interfaces are configured for the interface, and the
driver did VLAN decapsulation in hardware, we were passing a frame
as if it came for the parent (non-VLAN) interface. Stop this from
happening.
Reminded by: glebius
Security: This could pose a security risk in some setups
6c23e6cc Mon Feb 14 08:29:42 GMT 2005 Ruslan Ermilov <ru@FreeBSD.org> If no vlan(4) interfaces are configured for the interface, and the
driver did VLAN decapsulation in hardware, we were passing a frame
as if it came for the parent (non-VLAN) interface. Stop this from
happening.
Reminded by: glebius
Security: This could pose a security risk in some setups
|