Date: Thu, 20 Nov 2008 12:53:28 +0100 From: Ivan Voras <ivoras@freebsd.org> To: freebsd-net@freebsd.org Subject: Re: FreeBSD Bridge and ARP question/strangeness Message-ID: <gg3j1u$l0u$1@ger.gmane.org> In-Reply-To: <002f01c94af4$ecbced90$c636c8b0$@net> References: <002f01c94af4$ecbced90$c636c8b0$@net>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig857B30409D1AE3D619B3685F Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cole wrote: > Hi. >=20 > I have been playing with FreeBSD bridging in 7.0-Release. And was just > testing some things to see exactly how it worked and try a few things o= ut. I > know that this isn't how the bridge is meant to be setup, but now im ju= st > curious as to why the following is happening. >=20 > I have a box with a few interfaces, and i had setup rl0 with an ip addr= ess > and it could communicate/ping everything on the network fine, all the r= est > of the other interfaces are unplugged and have no ip's assigned. Now if= i go > ahead and create a bridge interface and then just add that single inter= face > with the ip assigned to it to the bridge, without assigning a new ip to= the > bridge, i get some strange things happening. Every box on the network n= ot > running FreeBSD is still able to ping and receive a reply from the box = on > the ip it was using on the interface. However, no FreeBSD box is now ab= le to > ping the box at all. In the arp listing, it shows any of the FreeBSD bo= xes > that are trying to ping it as "(incomplete)". But for every other box t= hat > isn't FreeBSD it gets a full arp listing and all those boxes are still = able > to communicate with the box fine. >=20 > So i was just wondering if theres a reason for this, or if anyone has a= ny > idea or clues why this might be happening. If you want i can provide > whatever dumps you would need or anything like that. Can you rule out ARP timeouts? E.g. maybe other boxes have longer ARP TTLs than FreeBSD boxes. It's happened to me once (it was a bug in the em driver). --------------enig857B30409D1AE3D619B3685F Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJJU+4ldnAQVacBcgRAhirAJ0QRL+yKuDp5nkxL4kJlIQo+YIzuACg5Mjv vBwoVGLH4UtXn+052NT35hw= =FKt4 -----END PGP SIGNATURE----- --------------enig857B30409D1AE3D619B3685F--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?gg3j1u$l0u$1>