El 07/08/13 18:09, Antonio Quartulli escribió:
Hello Fernando,
to be honest the set up is not really clear to me, not because of the topology but because of all the bridges you created.
Once thing I am confident enough is that if you have clients connected to wlan1.N and then you have a bridge configured as { wlan1, eth0, bat0 } this is not going to work as expected.
Traffic sent over wlan1.1 will not be delivered to the bridge and so not delivered to bat0.
You should include wlan1.1 in the bridge itself.
Other than DAT, I expect this to be a general problem.
Cheers,
Hi Antonio,
This stage is working correctly in a lab. Every client can connect and traffic is correctly routed and delivered. But I noticed the empty dat table, so I think there's something that I'm not understanding or, at least, that I could do it better. I'll try to explain what I want to achieve, perhaps in that way I could be understood better.
I have a freeradius service controlling clients acces, one of the attributes is the vlan-id, I'm using 802.1x. This part is quite easy I think, but the reason why nodes haven't got any ip (but management IP, which users can't achieve...) is not so easy.
1) I'm using dynamic vlan assignment. With this config, I just have to change attribs in my radius server and create a new pool in my fw... I haven't to configure anything in every node.
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..
There is an image attached explaining bridges.
Thanks a lot. Fernando.
