No subject
Thu Aug 20 06:46:28 UTC 2009
However, from router2, babel is not creating a default route for me.
Here is router1's table:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.10.0.1 10.38.8.4 255.255.255.255 UGH 0 0 0 eth0.1
192.168.1.10 10.38.8.4 255.255.255.255 UGH 0 0 0 eth0.1
10.38.8.4 10.38.8.4 255.255.255.255 UGH 0 0 0 eth0.1
10.38.8.0 * 255.255.255.0 U 0 0 0 eth0.1
10.11.0.0 * 255.255.255.0 U 0 0 0 br-lan
router2's table looks like this:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.11.0.1 10.38.8.1 255.255.255.255 UGH 0 0 0 eth0.1
10.38.8.1 10.38.8.1 255.255.255.255 UGH 0 0 0 eth0.1
10.38.8.0 * 255.255.255.0 U 0 0 0 eth0.1
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0.2
10.10.0.0 * 255.255.0.0 U 0 0 0 br-lan
default 192.168.1.1 0.0.0.0 UG 10 0 0 eth0.2
default * 0.0.0.0 U 65534 0 0 lo
I can ping 192.168.1.10 (router2's far side interface). But no
default route is created on router1, and I can not create one by hand
either:
router1# ping 192.168.1.10
PING 192.168.1.10 (192.168.1.10): 56 data bytes
64 bytes from 192.168.1.10: seq=0 ttl=64 time=3.701 ms
router1# route add default gw 192.168.1.10
route: SIOCADDRT: Network is unreachable
I can, however, create one by hand to 10.38.8.4 and this does make things work.
I have a bunch of other possibly related questions:
When router2's internet connection goes away, I would expect router2
to withdraw the route to 192.168.1.10 but it doesn't.
router2 is in fact redistributing a host route to itself (a route to a
single host). Why isn't router2 distributing a route to
192.168.1.0/24? In fact, router2 is also distributing a route to
itself on the network that it's on (route to 10.38.8.4 via 10.38.8.4
on the 10.38.8.0/24 net), hence it's not very useful (not harmful
either). Perhaps I need some filter to only distribute routes with
plen ge 1?
I admit that I do not understand the babel.conf file very well.
Michael
More information about the Babel-users
mailing list