From owner-freebsd-net  Tue Jan 15 14:20:22 2002
Delivered-To: freebsd-net@freebsd.org
Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38])
	by hub.freebsd.org (Postfix) with ESMTP id 712E437B402
	for <freebsd-net@FreeBSD.ORG>; Tue, 15 Jan 2002 14:20:19 -0800 (PST)
Received: from InterJet.elischer.org ([12.232.206.8])
          by rwcrmhc51.attbi.com
          (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP
          id <20020115222019.QOPN5944.rwcrmhc51.attbi.com@InterJet.elischer.org>;
          Tue, 15 Jan 2002 22:20:19 +0000
Received: from localhost (localhost.elischer.org [127.0.0.1])
	by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id OAA83204;
	Tue, 15 Jan 2002 14:07:37 -0800 (PST)
Date: Tue, 15 Jan 2002 14:07:37 -0800 (PST)
From: Julian Elischer <julian@elischer.org>
To: Bjoern Fischer <bfischer@Techfak.Uni-Bielefeld.DE>
Cc: freebsd-net@FreeBSD.ORG
Subject: Re: bridged interfaces don't see broadcasts
In-Reply-To: <20020115212056.GA3520@frolic.no-support.loc>
Message-ID: <Pine.BSF.4.21.0201151407090.82675-100000@InterJet.elischer.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: QUOTED-PRINTABLE
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org

What happens if you use netgraph bridging?
(/usr/share/examples/netgraph)


On Tue, 15 Jan 2002, Bjoern Fischer wrote:

> Hello,
>=20
> on a NIS and NFS serving machine I bridged two ethernet NICs:
>=20
> 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
>=20
> vr0: flags=3D8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 150=
0
>         inet6 fe80::250:baff:fe23:df3%vr0 prefixlen 64 scopeid 0x1=20
>         inet 192.168.43.1 netmask 0xffffff00 broadcast 192.168.43.255
>         ether 00:50:ba:23:0d:f3=20
>         media: Ethernet autoselect (100baseTX <full-duplex>)
>         status: active
> ed1: flags=3D8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 150=
0
>         inet6 fe80::24f:4cff:fe02:4a4c%ed1 prefixlen 64 scopeid 0x3=20
>         ether 00:4f:4c:02:4a:4c=20
>=20
> ed1 is an old 10-Base2/10-Base-T.
>=20
> 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.
>=20
> 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.
>=20
> -Bj=F6rn
>=20
>=20
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-net" in the body of the message
>=20


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message