Re: [B.A.T.M.A.N.] Filtering BATMAN-ADV packet

Sven Eckelmann
2011-07-21T08:23:43Z

[-- Attachment #1: Type: text/plain, Size: 1601 bytes --]

On Thursday 21 July 2011 15:28:18 Nik M. Anas Kamarudin wrote:
> I think this is misunderstanding. This method work fine on wire
> interface because it use ebtables to filter the batman-adv packet, and
> ebtables need to be use with bridge interface.
>
> And why this method don't work on wireless, is simply because you
> can't create bridge interface with wireless interface. That why ask,
> if anyone here got another idea on how to filter the batman-adv
> packet. I provide the example above to show what i done, if others can
> do same thing but different way.

As explained in my counterexample, this statement is simply wrong. I am 100%
sure that I use bridges together with wireless interfaces (ath9k+AP) and I
can't take enough drugs to forget that. Either you have a specific situation
where this is not possible (there are some of course) and have to say that or
you are simply lying. But giving no information or lying will not help you at
all.

> About the br0, you can make the br0 work with or without IP.

And now we bury the routing...

I don't see that you use specific routes which are set to the correct device.
So let's assume that your routing table now has two entries for 192.168.5.0
with different outgoing devices and that it chooses (for unknown reasons) to
use the route over br0. The target you want to reach is not only one hop away
and thus the actual nic can't reach it directly, but batman-adv would be able
to forward the packet correctly. And now think about how useful it was to give
br0 a conflicting ip (due to the same subnets).

Kind regards,
Sven

[-- Attachment #2: This is a digitally signed message part. --]