[Bug 250394] After creating an ethernet bridge the host responds to incoming packets not addressed to itself
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Fri Oct 16 11:55:48 UTC 2020
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250394
Bug ID: 250394
Summary: After creating an ethernet bridge the host responds to
incoming packets not addressed to itself
Product: Base System
Version: 12.1-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: kern
Assignee: bugs at FreeBSD.org
Reporter: be at 0x20.net
Preface: the host where this issue was detected is connected to a buggy switch.
The switch sends unicast packets addressed to foreign MACs to this host.
As soon as a bridge is created with the host's uplink interface as a member,
the host responds to packets addressed to foreign MAC/IP address combinations.
In this example 0c:c4:7a:9a:9a:ac is a foreign MAC address and 46.251.251.225
is a foreign IP address while 70:85:c2:39:08:19 and 46.251.251.47 are local to
the host. tcpdump output:
12:07:49.256533 00:24:dc:41:9f:c0 > 0c:c4:7a:9a:9a:ac, ethertype IPv4 (0x0800),
length 74: 144.76.249.205.56701 > 46.251.251.225.33452: UDP, length 32
12:07:49.256612 70:85:c2:39:08:19 > 00:24:dc:41:9f:c0, ethertype IPv4 (0x0800),
length 102: 46.251.251.47 > 144.76.249.205: ICMP 46.251.251.225 udp port 33452
unreachable, length 68
On the other hand as soon as the bridge is detroyed, the host stops responding
to foreign packets. It also does not respond to foreign packets without the
bridge but with enabled promisc. mode on the uplink interface.
This is the interface configuration while showing the weird behaviour:
# ifconfig
re0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu
1500
options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
ether 70:85:c2:39:08:19
inet 46.251.251.47 netmask 0xffffff00 broadcast 46.251.251.255
inet 46.251.251.54 netmask 0xffffffff broadcast 46.251.251.54
inet 46.251.251.57 netmask 0xffffffff broadcast 46.251.251.57
inet 192.168.10.4 netmask 0xffffff00 broadcast 192.168.10.255
inet 46.251.251.55 netmask 0xffffffff broadcast 46.251.251.55
inet 46.251.251.56 netmask 0xffffffff broadcast 46.251.251.56
inet 127.1.0.2 netmask 0xffffffff broadcast 127.1.0.2
inet6 fe80::7285:c2ff:fe39:819%re0 prefixlen 64 scopeid 0x1
inet6 2a0a:51c0:0:2c::e prefixlen 64
inet6 2a0a:51c0:0:2c::80 prefixlen 128
inet6 2a0a:51c0:0:2c::53 prefixlen 128
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
inet 127.0.0.1 netmask 0xff000000
inet 127.1.0.2 netmask 0xffffffff
groups: lo
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
pflog0: flags=141<UP,RUNNING,PROMISC> metric 0 mtu 33160
groups: pflog
tap0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
description: vmnet-discourse.nomadbsd.org-0-public
options=80000<LINKSTATE>
ether 00:bd:c7:24:20:00
groups: tap vm-port
media: Ethernet autoselect
status: active
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
Opened by PID 39345
vm-public: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether d2:f1:1a:d8:37:b0
id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
member: re0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 1 priority 128 path cost 20000
groups: bridge vm-switch viid-4c918@
nd6 options=1<PERFORMNUD>
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list