On 31/01/11 18:32, Clemens John wrote:
Am Samstag 29 Januar 2011, 19:00:50 schrieb Marek Lindner:
Hi,
I think if we don't want to change back our configuration (batman-adv on vpn with its mtu-problems etc.) the simplest way would be connecting a usual router to the wrt54g.
I don't think the VPN is the problem here but the fact that you can't bridge an interface running in adhoc mode. Ad-hoc is "lacks" a field in the wifi header which makes bridging impossible. However, I agree with your proposed solution - another router connected to the Ethernet of the wrt54g can solve the issue.
This is not possible in this case (I don´t have another router).
Is there onother (maybe harder) way or a hack to do get the same result like when bridging two interfaces? Maybe with iptables?
Or does anyone know what the status of multiple ssid on wrt54g with kernel 2.6 is?
Regards Clemens
If your non-batman clients don't need incoming connections, you could NAT outgoing connections : [client]-->[adhoc ath1]-->NAT-->[br-mesh] You would have to run a DHCP server on the ath1 interface to give those clients a private IP and tell them to use the private IP on ath1 as their router.
-Kevin
--- Have a vacancy for a Network Engineer/IT guy in London, UK? Please let me know.