On Wed, Nov 4, 2009 at 08:49, Gabriel Kerneis <[email protected]> wrote: > Hi again, > > On Wed, Nov 04, 2009 at 08:39:10AM +0100, Gabriel Kerneis wrote: >> I'm not sure this will work, however, since your interface is not >> involved in the Babel protocol (it is only providing a default route). I >> don't know how such interfaces are handled by Babel. > > On second thought, a (probably) much better solution would be: > redistribute metric 128 > on router1 and > redistribute metric 256 > on router2. > > This will redistribute your default routes with different metric > values, the lower being the better. You might need to tune this a > little, I suppose.
This doesn't seem to work. So far not matter what I've tried, if the local adsl line is working, each router prefers to send out packets out it's own local line (the closest default route). Also, each adsl line, when it comes up (or rather when the adsl router on the far end is there), it creates a default route in the routing table. I can inhibit this by adding "option gateway 0.0.0.0" to the wan interface in /etc/config/network (this is openWRT). However, when I do that in both routers, no default route to the outside gets created. Hence babel isn't able to propagate a usable route to the outside. I also tried inhibiting the creation of the default route upon the interface coming up and creating a static default route with a high metric out the adsl line on both routers. The hope was that babel would then create a second default route with a lower metric. However, no, no other default route gets created if the nearest adsl line is usable. This is what I have in babel.conf: redistribute local deny redistribute metric 256 (128 on router1, 256 on router2 as you recommend) maybe I'm missing something to get it to distribute those local default routes? Michael _______________________________________________ Babel-users mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/babel-users
