Date: Mon, 29 Oct 2012 17:59:04 -0400 From: Kim Culhan <w8hdkim@gmail.com> To: Monthadar Al Jaberi <monthadar@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: Interfaces connected by bridge(4) do not pass arp replies Message-ID: <CAKZxVQUBC9m0WjQ-n7%2BoJo0=0_DEMU0bnXopsNYqYdgxq2xE0g@mail.gmail.com> In-Reply-To: <CA%2BsBSoKmnQAW1WoKnrDzNje5SF1wooW0JVdxb57JjyYpEeFQpA@mail.gmail.com> References: <CAKZxVQVXptkzS-hisKRmaooFaqgrHx7nOouO3Uj4vxuTBqkhTg@mail.gmail.com> <CA%2BsBSo%2BQy70cLL97KY8BE9L4GR2cwzhLTe6XP_Pe1Qsr8Xa7mQ@mail.gmail.com> <CAKZxVQXaZy9H2QR4uz0XzZ%2BmCyX-27CVBQEeFGH=J4G5EtvPXg@mail.gmail.com> <CA%2BsBSoKmnQAW1WoKnrDzNje5SF1wooW0JVdxb57JjyYpEeFQpA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Oct 29, 2012 at 5:17 PM, Monthadar Al Jaberi <monthadar@gmail.com> wrote: > On Mon, Oct 29, 2012 at 9:55 PM, Kim Culhan <w8hdkim@gmail.com> wrote: >> On Mon, Oct 29, 2012 at 3:59 PM, Monthadar Al Jaberi >> <monthadar@gmail.com> wrote: >>> On Mon, Oct 29, 2012 at 8:46 PM, Kim Culhan <w8hdkim@gmail.com> wrote: >>>> With 2 interfaces present on a bridge0, an arp request is send from >>>> msk0 and is received >>>> by a machine on em0. >>>> >>>> When a reply to that arp request is sent by a machine on em0 it is not >>>> visible on the >>>> bridge0 nor on msk0 as indicated by tcpdump. >>>> >>>> The arp reply is visible while watching em0 with tcpdump. >>> >>> Is em0 set in promisc mode? >>> >>>> >>>> This behaviour is also true when arp requests are sent from a wlan >>>> interface ath0 >>>> and received on a wired interface, the arp reply is visible on the >>>> wired interface but not >>>> visible monitoring with 'tcpdump -i bridge0 arp'. >>> >>> Hmm, I am briding between ath0 and wired (arge0). >>> >>> Can you provide more info? what is your rc.conf? How does it set the interfaces? >>> Can you give ifconfig output? >>> The are reply that you dont see on bridge0 can you dump it from wired >>> interface? >> >> What svn revision of FreeBSD -current are you running? > > FreeBSD head r238604. I should have mentioned earlier this is with r242126, there have been some changes to the network code since 238604, maybe that is why you don't have this problem. -kim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKZxVQUBC9m0WjQ-n7%2BoJo0=0_DEMU0bnXopsNYqYdgxq2xE0g>