Date: Tue, 15 Jan 2002 22:20:56 +0100 From: Bjoern Fischer <bfischer@Techfak.Uni-Bielefeld.DE> To: freebsd-net@FreeBSD.ORG Subject: bridged interfaces don't see broadcasts Message-ID: <20020115212056.GA3520@frolic.no-support.loc>
next in thread | raw e-mail | index | archive | help
Hello,
on a NIS and NFS serving machine I bridged two ethernet NICs:
net.link.ether.bridge_cfg: vr0:0,ed1:0
net.link.ether.bridge: 1
net.link.ether.bridge_ipfw: 0
net.link.ether.bridge_ipfw_drop: 0
net.link.ether.bridge_ipfw_collisions: 0
vr0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::250:baff:fe23:df3%vr0 prefixlen 64 scopeid 0x1
inet 192.168.43.1 netmask 0xffffff00 broadcast 192.168.43.255
ether 00:50:ba:23:0d:f3
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
ed1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::24f:4cff:fe02:4a4c%ed1 prefixlen 64 scopeid 0x3
ether 00:4f:4c:02:4a:4c
ed1 is an old 10-Base2/10-Base-T.
It seems that broadcasts (coming from the ed1 segment) are transmitted
by the bridge to the vr0 segment (as it should be). But vr0 never sees
any of these broadcast packets. That's why NIS does not work on any
client that sits on the ed1 segment.
As an experiment I enabled net.inet.icmp.bmcastecho on the server
(192.168.43.1) and on some clients on both segments. When pinging
192.168.43.255 from a vr0 segment client everything is fine. When
pinging from an ed1 segment client the response from 192.168.43.1
is always missing.
-Björn
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020115212056.GA3520>