> I expect the worst behavior to simply translate into a mute interface > with or without VLAN but...
Actually, I upgraded to 2.6.15-rc3 plus your patches, and the behaviour is simply exactly the same. (I've only compiled one 2.6.15-rc3 kernel, so I can't have possibly booted the wrong one.) Tcpdump on a tagged port with the velocity driver: # tcpdump -n -i eth0 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 03:54:26.437624 802.1d unknown version 03:54:28.438430 802.1d unknown version 03:54:30.438488 802.1d unknown version 03:54:32.442433 802.1d unknown version 03:54:33.446611 LACPv1, length: 110 03:54:34.554444 802.1d unknown version 03:54:36.445276 802.1d unknown version 03:54:38.448251 802.1d unknown version 03:54:40.448322 802.1d unknown version 03:54:42.451189 802.1d unknown version 10 packets captured 20 packets received by filter 0 packets dropped by kernel While listening on the same port with a Tulip-based 100baseT card: # tcpdump -n -i eth1 tcpdump: WARNING: eth1: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes 03:55:28.295843 vlan 2, p 0, arp who-has 192.35.100.95 (ff:ff:ff:ff:ff:ff) tell 192.35.100.92 03:55:28.492928 802.1d unknown version 22:55:28.546414 vlan 2, p 0, arp who-has 192.35.100.1 (ff:ff:ff:ff:ff:ff) tell 192.35.100.23 03:55:28.739570 vlan 2, p 0, arp who-has 192.35.100.1 (ff:ff:ff:ff:ff:ff) tell 192.35.100.110 03:55:28.748937 vlan 2, p 0, arp who-has 192.35.100.1 (ff:ff:ff:ff:ff:ff) tell 192.35.100.86 03:55:29.739545 vlan 2, p 0, arp who-has 192.35.100.1 (ff:ff:ff:ff:ff:ff) tell 192.35.100.110 03:55:29.748873 vlan 2, p 0, arp who-has 192.35.100.1 (ff:ff:ff:ff:ff:ff) tell 192.35.100.86 03:55:30.126945 vlan 2, p 0, IP 192.35.100.23.41946 > 198.69.104.19.53: 28350+ PTR? 59.100.35.192.in-addr.arpa. (44) 03:55:30.174782 vlan 2, p 0, arp who-has 192.35.100.1 tell 192.35.100.3 03:55:30.494294 802.1d unknown version 03:55:30.739527 vlan 2, p 0, arp who-has 192.35.100.1 (ff:ff:ff:ff:ff:ff) tell 192.35.100.110 03:55:30.748865 vlan 2, p 0, arp who-has 192.35.100.1 (ff:ff:ff:ff:ff:ff) tell 192.35.100.86 03:55:30.872635 vlan 2, p 0, arp who-has 192.35.100.1 (ff:ff:ff:ff:ff:ff) tell 192.35.100.38 03:55:31.174739 vlan 2, p 0, arp who-has 192.35.100.1 tell 192.35.100.3 03:55:31.228356 vlan 2, p 0, arp who-has 192.35.100.1 tell 192.35.100.59 03:55:31.739538 vlan 2, p 0, arp who-has 192.35.100.1 (ff:ff:ff:ff:ff:ff) tell 192.35.100.110 03:55:31.748865 vlan 2, p 0, arp who-has 192.35.100.1 (ff:ff:ff:ff:ff:ff) tell 192.35.100.86 03:55:31.755004 vlan 2, p 0, arp who-has 192.35.100.95 (ff:ff:ff:ff:ff:ff) tell 192.35.100.92 03:55:31.872379 vlan 2, p 0, arp who-has 192.35.100.1 (ff:ff:ff:ff:ff:ff) tell 192.35.100.38 19 packets captured 38 packets received by filter 0 packets dropped by kernel Basiclly, all the vlan packets disappear, even during promiscuous receive. Thanks for trying, though! I'm running your patches untagged at the moment with no obvious problems. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
