Date: Thu, 11 Feb 2010 14:52:06 +0000 From: Rui Paulo <rpaulo@freebsd.org> To: batcilla itself <batcilla@gmail.com> Cc: freebsd-net@freebsd.org Subject: Re: TDMA link cannot pass data Message-ID: <4B741996.8030801@freebsd.org> In-Reply-To: <6c36ec371002101424n28589b53l7d7a14660c04ce08@mail.gmail.com> References: <6c36ec371002101424n28589b53l7d7a14660c04ce08@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/02/2010 22:24, batcilla itself wrote: >>> On 3 Jan 2010, at 12:23, Kim Culhan wrote: > > [skip...] > >> This is odd. What happens without the bridge? >> >> -- >> Rui Paulo > > I guess without the bridge ping going w/o any problem. > > I also tried couple of configs with wlan in different wlanmode, hostap etc: > it is precisely same as Kim wrote. In case of use routed connection it > work just fine. > In case of: > [host1]----(eth===bridge0===gif)----wlan0=====wirelesslink=====wlan0---(gif===bridge0===eth)----[host2] > it is works and host1 can ping host2. > in case of > [host1]----(eth===bridge0===wlan0)----====wirelesslink====-----(wlan0===bridge0===etc)---[host2] > broadcast packets including arp can go through bridge, other packets > miss after leaving wlan in direction of wirelesslink. > > I seen this on very recent 8-STABLE. (FreeBSD 8.0-STABLE #1: Thu Feb > 4 23:03:37 EET 2010) > > Can it be somehow linked with experimental bridging support for a mesh? > May be there is some sysctl need to be set in non-default value. > > I also repeat same test with 9-CURRENT ( FreeBSD 9.0-CURRENT #0: Thu > Feb 4 16:16:02 UTC 2010 ). > > This is really odd... I think this is more likely related to ARP and routing table issues. I asked the submitter to use p5-SVN-Bisect in order to find the revision that broke. -- Rui Paulo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B741996.8030801>