Re: agr(4) + bridge(4): problems!

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Thu, Sep 27, 2012 at 08:40:31AM -0400, Thor Lancelot Simon wrote:
> 
> What you may be seeing is an inherent asymmetry of agr in our kernel.
> Unless some other interface is stacked on top of the agr, there's really
> no reason for packets to be fed to the agr's input routine rather than
> passed directly from the underlying hardware's input routine to the
> network-layer protocol input routine (usually but not always ip_input).
> So -- unless things have changed since last I looked -- that's exactly
> what is done.  Packets go _out_ the agr, but they come _in_ the wm
> interfaces.  If you attach tcpdump to the agr you may miss all inbound
> traffic, and the bridge likely does too.
> 
> Even in the case of vlan-on-agr, since most network hardware supports
> vlan decapsulation directly it is probably the case that the agr input
> routine is bypassed.  Unless my head's gone completely wrong this
> morning and I'm thinking of a different kernel.

I guess you may be mixing things up: I tried a tcpdump on an agr,
and it's seeing inbound and outbound traffics.

-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--