Invalid 802.1q vlan id using em0 (Intel PRO/1000T) on 4.5
The vlan id for my em0 interface is not reading properly after upgrading to 4.5. Tcpdump shows some wild vid values in the traffic when using em0: * This traffic should be on vlan2 (lan) 00:21:70:c5:3d:4f ff:ff:ff:ff:ff:ff 8100 64: 802.1Q vid 512 pri 0 arp who-has 10.107.208.1 tell 10.107.208.50 * This traffic should be on vlan3 (egress vlan) 00:1e:be:fe:f3:05 ff:ff:ff:ff:ff:ff 8100 64: 802.1Q vid 768 pri 0 arp who-has 98.196.101.152 tell 98.196.100.1 00:1e:be:fe:f3:05 ff:ff:ff:ff:ff:ff 8100 64: 802.1Q vid 768 pri 0 arp who-has 98.196.88.115 tell 98.196.88.1 * This traffic should be on vlan4, it is correct: 00:02:b3:ed:68:89 01:00:5e:7f:ff:fa 8100 308: 802.1Q vid 4 pri 0 10.0.0.1.29275 > 239.255.255.250.1900: udp 262 [ttl 1] 00:02:b3:ed:68:89 01:00:5e:7f:ff:fa 8100 380: 802.1Q vid 4 pri 0 10.0.0.1.29275 > 239.255.255.250.1900: udp 334 [ttl 1] It seems as though the vlan id is being multiplied by 256 for vlans 2 and 3. When I use the gem0 interface on the same machine, things work: * This traffic should be on vlan2 (lan), it is correct: 00:03:ba:04:b2:1d 00:50:8d:95:39:17 8100 110: 802.1Q vid 2 pri 0 10.107.208.1.22 > 10.107.208.102.2692: P 920030:920082(52) ack 11189 win 17520 (DF) [tos 0x10] 00:03:ba:04:b2:1d 00:50:8d:95:39:17 8100 110: 802.1Q vid 2 pri 0 10.107.208.1.22 > 10.107.208.102.2692: P 920082:920134(52) ack 11189 win 17520 (DF) [tos 0x10] * This traffic should be on vlan3 (egress vlan), it is correct: 00:1e:be:fe:f3:05 ff:ff:ff:ff:ff:ff 8100 64: 802.1Q vid 3 pri 0 arp who-has 98.194.104.216 tell 98.194.104.1 00:1e:be:fe:f3:05 ff:ff:ff:ff:ff:ff 8100 64: 802.1Q vid 3 pri 0 arp who-has 76.31.110.47 tell 76.31.108.1 * This traffic should be on vlan4, it is correct: 00:03:ba:04:b2:1d 01:00:5e:7f:ff:fa 8100 373: 802.1Q vid 4 pri 0 10.0.0.1.10117 > 239.255.255.250.1900: udp 327 [ttl 1] 00:03:ba:04:b2:1d 01:00:5e:7f:ff:fa 8100 373: 802.1Q vid 4 pri 0 10.0.0.1.10117 > 239.255.255.250.1900: udp 327 [ttl 1] The em0 interface worked without an issue using 4.4 as did gem0. Here are my interface configurations using gem0: # ifconfig -a lo0: flags=8049 mtu 33160 priority: 0 groups: lo inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 gem0: flags=8863 mtu 1500 lladdr 00:03:ba:04:b2:1d priority: 0 media: Ethernet autoselect (100baseTX full-duplex) status: active inet6 fe80::203:baff:fe04:b21d%gem0 prefixlen 64 scopeid 0x1 em0: flags=8843 mtu 1500 lladdr 00:02:b3:ed:68:89 priority: 0 media: Ethernet autoselect (none) status: no carrier inet6 fe80::202:b3ff:feed:6889%em0 prefixlen 64 scopeid 0x2 enc0: flags=0<> mtu 1536 priority: 0 vlan2: flags=8843 mtu 1500 lladdr 00:03:ba:04:b2:1d priority: 0 vlan: 2 priority: 0 parent interface: gem0 groups: vlan inet6 fe80::203:baff:fe04:b21d%vlan2 prefixlen 64 scopeid 0x5 inet 10.107.208.1 netmask 0xff00 broadcast 10.107.208.255 vlan3: flags=8843 mtu 1500 lladdr 00:03:ba:04:b2:1d priority: 0 vlan: 3 priority: 0 parent interface: gem0 groups: vlan egress inet6 fe80::203:baff:fe04:b21d%vlan3 prefixlen 64 scopeid 0x6 inet x.x.x.x netmask 0xfc00 broadcast 255.255.255.255 vlan4: flags=8843 mtu 1500 lladdr 00:03:ba:04:b2:1d priority: 0 vlan: 4 priority: 0 parent interface: gem0 groups: vlan inet6 fe80::203:baff:fe04:b21d%vlan4 prefixlen 64 scopeid 0x7 inet 10.0.0.1 netmask 0xff00 broadcast 10.0.0.255 vlan5: flags=8843 mtu 1500 lladdr 00:03:ba:04:b2:1d priority: 0 vlan: 5 priority: 0 parent interface: gem0 groups: vlan inet6 fe80::203:baff:fe04:b21d%vlan5 prefixlen 64 scopeid 0x8 inet 10.180.16.1 netmask 0xff00 broadcast 10.180.16.255 pflog0: flags=141 mtu 33160 priority: 0 groups: pflog Here are my interface configurations using em0: lo0: flags=8049 mtu 33160 priority: 0 groups: lo inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 gem0: flags=8863 mtu 1500 lladdr 00:03:ba:04:b2:1d priority: 0 media: Ethernet autoselect (none) status: no carrier inet6 fe80::203:baff:fe04:b21d%gem0 prefixlen 64 scopeid 0x1 em0: flags=8843 mtu 1500 lladdr 00:02:b3:ed:68:89 priority: 0 media: Ethernet autoselect (1000baseT full-duplex,master) status: active inet6 fe80::202:b3ff:feed:6889%em0 prefixlen 64 scopeid 0x2 enc0: flags=0<> mtu 1536 priority: 0 vlan2: flags=8843 mtu 1500 lladdr 00:02:b3:ed:68:89 priority: 0 vlan: 2 priority: 0 parent interface: em0 groups: vlan inet6 fe80::202:b3ff:feed:6889%vlan2 prefixlen 64 scopeid 0x5 inet 10.107.208.1 netmask 0xff00 bro
Re: Invalid 802.1q vlan id using em0 (Intel PRO/1000T) on 4.5
On Sun, May 24, 2009 at 2:52 PM, Axton wrote: > The vlan id for my em0 interface is not reading properly after upgrading to > 4.5. > > Tcpdump shows some wild vid values in the traffic when using em0: > > * This traffic should be on vlan2 (lan) > 00:21:70:c5:3d:4f ff:ff:ff:ff:ff:ff 8100 64: 802.1Q vid 512 pri 0 arp > who-has 10.107.208.1 tell 10.107.208.50 > > * This traffic should be on vlan3 (egress vlan) > 00:1e:be:fe:f3:05 ff:ff:ff:ff:ff:ff 8100 64: 802.1Q vid 768 pri 0 arp > who-has 98.196.101.152 tell 98.196.100.1 > 00:1e:be:fe:f3:05 ff:ff:ff:ff:ff:ff 8100 64: 802.1Q vid 768 pri 0 arp > who-has 98.196.88.115 tell 98.196.88.1 > > * This traffic should be on vlan4, it is correct: > 00:02:b3:ed:68:89 01:00:5e:7f:ff:fa 8100 308: 802.1Q vid 4 pri 0 > 10.0.0.1.29275 > 239.255.255.250.1900: udp 262 [ttl 1] > 00:02:b3:ed:68:89 01:00:5e:7f:ff:fa 8100 380: 802.1Q vid 4 pri 0 > 10.0.0.1.29275 > 239.255.255.250.1900: udp 334 [ttl 1] > > It seems as though the vlan id is being multiplied by 256 for vlans 2 and 3. > > > When I use the gem0 interface on the same machine, things work: > > * This traffic should be on vlan2 (lan), it is correct: > 00:03:ba:04:b2:1d 00:50:8d:95:39:17 8100 110: 802.1Q vid 2 pri 0 > 10.107.208.1.22 > 10.107.208.102.2692: P 920030:920082(52) ack 11189 win > 17520 (DF) [tos 0x10] > 00:03:ba:04:b2:1d 00:50:8d:95:39:17 8100 110: 802.1Q vid 2 pri 0 > 10.107.208.1.22 > 10.107.208.102.2692: P 920082:920134(52) ack 11189 win > 17520 (DF) [tos 0x10] > > * This traffic should be on vlan3 (egress vlan), it is correct: > 00:1e:be:fe:f3:05 ff:ff:ff:ff:ff:ff 8100 64: 802.1Q vid 3 pri 0 arp who-has > 98.194.104.216 tell 98.194.104.1 > 00:1e:be:fe:f3:05 ff:ff:ff:ff:ff:ff 8100 64: 802.1Q vid 3 pri 0 arp who-has > 76.31.110.47 tell 76.31.108.1 > > * This traffic should be on vlan4, it is correct: > 00:03:ba:04:b2:1d 01:00:5e:7f:ff:fa 8100 373: 802.1Q vid 4 pri 0 > 10.0.0.1.10117 > 239.255.255.250.1900: udp 327 [ttl 1] > 00:03:ba:04:b2:1d 01:00:5e:7f:ff:fa 8100 373: 802.1Q vid 4 pri 0 > 10.0.0.1.10117 > 239.255.255.250.1900: udp 327 [ttl 1] > > > The em0 interface worked without an issue using 4.4 as did gem0. > > > Here are my interface configurations using gem0: > # ifconfig -a > lo0: flags=8049 mtu 33160 > priority: 0 > groups: lo > inet 127.0.0.1 netmask 0xff00 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 > gem0: flags=8863 mtu 1500 > lladdr 00:03:ba:04:b2:1d > priority: 0 > media: Ethernet autoselect (100baseTX full-duplex) > status: active > inet6 fe80::203:baff:fe04:b21d%gem0 prefixlen 64 scopeid 0x1 > em0: flags=8843 mtu 1500 > lladdr 00:02:b3:ed:68:89 > priority: 0 > media: Ethernet autoselect (none) > status: no carrier > inet6 fe80::202:b3ff:feed:6889%em0 prefixlen 64 scopeid 0x2 > enc0: flags=0<> mtu 1536 > priority: 0 > vlan2: flags=8843 mtu 1500 > lladdr 00:03:ba:04:b2:1d > priority: 0 > vlan: 2 priority: 0 parent interface: gem0 > groups: vlan > inet6 fe80::203:baff:fe04:b21d%vlan2 prefixlen 64 scopeid 0x5 > inet 10.107.208.1 netmask 0xff00 broadcast 10.107.208.255 > vlan3: flags=8843 mtu 1500 > lladdr 00:03:ba:04:b2:1d > priority: 0 > vlan: 3 priority: 0 parent interface: gem0 > groups: vlan egress > inet6 fe80::203:baff:fe04:b21d%vlan3 prefixlen 64 scopeid 0x6 > inet x.x.x.x netmask 0xfc00 broadcast 255.255.255.255 > vlan4: flags=8843 mtu 1500 > lladdr 00:03:ba:04:b2:1d > priority: 0 > vlan: 4 priority: 0 parent interface: gem0 > groups: vlan > inet6 fe80::203:baff:fe04:b21d%vlan4 prefixlen 64 scopeid 0x7 > inet 10.0.0.1 netmask 0xff00 broadcast 10.0.0.255 > vlan5: flags=8843 mtu 1500 > lladdr 00:03:ba:04:b2:1d > priority: 0 > vlan: 5 priority: 0 parent interface: gem0 > groups: vlan > inet6 fe80::203:baff:fe04:b21d%vlan5 prefixlen 64 scopeid 0x8 > inet 10.180.16.1 netmask 0xff00 broadcast 10.180.16.255 > pflog0: flags=141 mtu 33160 > priority: 0 > groups: pflog > > Here are my interface configurations using em0: > lo0: flags=8049 mtu 33160 > priority: 0 > groups: lo > inet 127.0.0.1 netmask 0xff00 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 > gem0: flags=8863 mtu 1500 > lladdr 00:03:ba:04:b2:1d > priority: 0 > media: Ethernet autoselect (none) > status: no carrier > inet6 fe80::203:baff:fe04:b21d%gem0 prefixlen 64 scopeid 0x1 > em0: flags=8843 mtu 1500 > lladdr 00:02:b3:ed:68:89 > priority: 0 > media: Ethernet autoselect (1000baseT full-duplex,master) > status: active > inet6 fe80::202:b3ff:feed:6889%em0 prefixlen 64 scopeid 0x2 > enc0: flags=0<> mtu 1536 >
