As Dave mentioned, you should redistribute the subnets used by each AP into Babel.
Assuming AP X uses 2001:db8:0:X::/64 on its interface wlan0, you should add this to Babel: redistribute ip 2001:db8:0:X::/64 eq 64 allow Or, if you want to have the same configuration on all routers, simply match on the interface: redistribute if wlan0 allow Remember, here, wlan0 is the interface on which you run an AP (not the ad-hoc interface on which you run Babel). See "man babeld" for the various filters options. On Fri, Feb 20, 2015 at 08:28:49AM +0530, pramod Jayram wrote: > Hello everyone, > Even i have the same problem. I have created two wireless network one in > ap mode and other in adhoc mode with two different ip address which > assigns ip to clients using dhcp. But a client (not running babel) > connected to ap cannot find the route generated by the mesh node(router > running babel on wireles interface) running babeld i.e it cannot ping any > other nodes available in the network. Is there something that i should be > aware of? > > Thanks > regards > > On Sun, Feb 15, 2015 at 6:30 PM, Juliusz Chroboczek < > [email protected]> wrote: > > > > I am in no way an expert with babeld, but I will try to answer your > > question. > > > > Everything you say is correct. > > > > -- Juliusz > > > > _______________________________________________ > > Babel-users mailing list > > [email protected] > > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users > > > _______________________________________________ > Babel-users mailing list > [email protected] > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users
pgphtF8kNhg8C.pgp
Description: PGP signature
_______________________________________________ Babel-users mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users
