Re: [B.A.T.M.A.N.] batctl: feature to filter nodes/clients

Simon Wunderlich
2015-02-05T18:24:50Z

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

On Thursday 05 February 2015 19:11:15 Moritz Warning wrote:
> >>
> >> Some explanation beforehand:
> >> Clients are computers not running batman-adv,
> >> represented by the MAC address of its network interface.
> >> Nodes are computers running batman-adv,
> >> represented by the MAC address of its primary interface.
> >>
> >> List of all nodes:
> >> Get all MACs from the 'Originator' column of the originator table
> >
> > Note that this may also show secondary interfaces of your neighbors - you
> > may have to filter that against a list of primary interfaces you collect
> > otherwise.
> Ok, I wonder how I can filter out those secondary interface MAC addresses
> of 1-hop neighbors.
> Can those addresses be recognized by comparing it to the Nexthop column?
> This seems to be the major problem for me right now.
>

Hmm ... actually you can't find that out from the originator output, since
there is no distinction there.

Maybe one thing how to find out from a remote host without prior information
(e.g. centralized database) would be to look at the tt global table -
secondary interfaces won't show up there. But thats also more a hack than
anything else. ;)

> >> List of all clients:
> >> Get all MACs of the 'Client' column of the transtable_local table
> >> when it starts with a '*' character.
> >
> > Yes, but you may want to filter out local mac addresses, which are
> > configured on top of VLANs on bridges.
>
> Are those the MAC-addresses of the bridge interface. Say, when I bridge bat0
> into br-lan, then the MAC of br-lan will show up as client?

The mac address of br-lan will most likely show up in the local translation
table, yes - unless you never send a packet from that interface.

Cheers,
Simon

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 181 bytes --]