Re: [B.A.T.M.A.N.] Mesh hickups with 2014.3

[Hans-Werner Hilse <hw@haveyouseenthiscat.de>]

Hi,

Am 2015-06-12 17:20, schrieb Bjoern Franke:
>> > Public-IPv6 is announced from a gateway via radvd into the mesh.
>> 
>> So even in that direction, NDP is fine. Seems only ICMPv6 echo
>> requests
>> are somewhat different then?
> 
> ip -6 neigh show says "FAILED".

My bad: I planned to write "RA" instead of NDP. In fact, NDP seems to be 
failing, as you have determined.

>> Look what's actually on the wire on both ends? Tcpdump and batctl
>> tcpdump?
> 
> On the gateway, there are neighbor solicitations from the "router" and
> advertisements from the gateway.

The advertisements are fine then, good.

I've seen the behaviour you're looking at with Linux bridge code and 
icmp snooping. Mind you: with *activated* icmp snooping. The NDP does 
not (does it?) register ICMP multicast with listener notices (or does it 
once, too early?), and the bridge code does then not consider the 
relevant end that should receive NDP traffic a destination for the 
multicast traffic that should have gotten there.

Of course, the question that evolves it whether the solicitation is 
actually received, then handled - answered to - by the gateway.

Did any network bridges come into play on the gateway(s) that hadn't 
been there before?

-hwh