Re: [B.A.T.M.A.N.] DAT issue

Marek Lindner
2013-08-07T17:23:50Z

Fernando,

On Thursday, August 08, 2013 01:07:09 Fernando Pizarro wrote:
> 2) I thougt having nodes without IP and just forwarding traffic to the
> main GW (the firewall) through batman-adv, not natting every client
> traffic with the node IP. In that way, roaming is working very good. The
> problem are stablished sessions, these sessions are lost jumping from a
> node to any other. I think this problem is nearly related to the empty
> DAT table, and empty DAT table problem is nearly related too the nodes
> has no IP assigned. However, I'm not sure about this..

the DAT table has nothing to do with roaming or sessions. It merely is an IP
address cache to speed up ARP lookups. Even without DAT everything should
work. I recommend to read our DAT user guide:
http://www.open-mesh.org/projects/batman-adv/wiki/DistributedArpTable

If disabling DAT would break something we certainly would not make it an
option to invite everybody to shoot themselves in the foot. ;-)

Therefore, I have to agree with Antonio that your problem is likely to be
found somewhere else. First, you should define which established sessions
break. The ones going into the internet or the ones you have locally.
Depending on the answer we can dig deeper.

Generally it is a good idea to simplfy the setup until a point where
everything works. Then you can move forward and make things more complicated.
For the time being I'd recommend to vastly simplify your bridge & vlan setup
by bridging your AP interface with bat0 only (no vlans, no radius tags, no
brvlanN interface) to see if your roaming works.

Cheers,
Marek