[Bug 236983] bnxt(4) VLAN not operational unless explicit "ifconfig promisc" is used on the physical IF

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236983

--- Comment #10 from punkt.de Hosting Team <mops at punkt.de> ---
ifconfig bnxt0 -promisc
packets stop

ifconfig bnxt0 promisc
packets resume

Some SSH traffic:

5:18:48.715538 00:19:e7:94:5b:6a > 00:25:90:5f:9a:82, ethertype 802.1Q
(0x8100), length 98: vlan 1, p 0, ethertype IPv4, 217.29.44.151.63305 >
217.29.45.32.22: Flags [.], ack 3274335, win 2048, options [nop,nop,TS val
506603871 ecr 3213738477,nop,nop,sack 3
{3280555:3280679}{3278667:3280291}{3287327:3292827}], length 0
15:18:48.715586 00:19:e7:94:5b:6a > 00:25:90:5f:9a:82, ethertype 802.1Q
(0x8100), length 98: vlan 1, p 0, ethertype IPv4, 217.29.44.151.63305 >
217.29.45.32.22: Flags [.], ack 3274335, win 2048, options [nop,nop,TS val
506603871 ecr 3213738477,nop,nop,sack 3
{3280555:3280679}{3278667:3280291}{3287327:3292827}], length 0
15:18:48.715632 00:19:e7:94:5b:6a > 00:25:90:5f:9a:82, ethertype 802.1Q
(0x8100), length 98: vlan 1, p 0, ethertype IPv4, 217.29.44.151.63305 >
217.29.45.32.22: Flags [.], ack 3274335, win 2048, options [nop,nop,TS val
506603871 ecr 3213738477,nop,nop,sack 3
{3280555:3280679}{3278667:3280291}{3287327:3292827}], length 0
15:18:48.716515 00:19:e7:94:5b:6a > 00:25:90:5f:9a:82, ethertype 802.1Q
(0x8100), length 98: vlan 1, p 0, ethertype IPv4, 217.29.44.151.63305 >
217.29.45.32.22: Flags [.], ack 3274335, win 2048, options [nop,nop,TS val
506603872 ecr 3213738477,nop,nop,sack 3
{3280555:3280679}{3278667:3280291}{3287327:3292827}], length 0
15:18:48.717626 00:19:e7:94:5b:6a > 00:25:90:5f:9a:82, ethertype 802.1Q
(0x8100), length 98: vlan 1, p 0, ethertype IPv4, 217.29.44.151.63305 >
217.29.45.32.22: Flags [.], ack 3274335, win 2048, options [nop,nop,TS val
506603873 ecr 3213738477,nop,nop,sack 3
{3280555:3280679}{3278667:3280291}{3287327:3292827}], length 0
15:18:48.717678 00:19:e7:94:5b:6a > 00:25:90:5f:9a:82, ethertype 802.1Q
(0x8100), length 98: vlan 1, p 0, ethertype IPv4, 217.29.44.151.63305 >
217.29.45.32.22: Flags [.], ack 3274335, win 2048, options [nop,nop,TS val
506603873 ecr 3213738477,nop,nop,sack 3
{3280555:3280679}{3278667:3280291}{3287327:3292827}], length 0


Kind regards,
Patrick


P.S. I have setups like this in production by the dozen. With em(4), igb(4),
ix(4), ixl(4), bge(4) ... this is our first system with bnxt(4) and the only
system with this problem. I really strongly suspect a driver problem.

P.P.S. In the linked ix Systems ticket there is another link to a forum post
that deals with precisely this issue with bnxt(4) *only*. That user wonders why
it seems to work the moment he starts tcpdump on the interface ... go figure
;-)

-- 
You are receiving this mail because:
You are the assignee for the bug.