On Sun, Jul 08, 2007 at 11:07:13PM +0200, Falk Brockerhoff wrote: > Falk Brockerhoff schrieb: > > > Ok, I'll give it a try. I assume 4.1 GENERIC#320 is "current enough"? > > In this version the bug is NOT fixed. I will try an update and this > setup again tomorrow. > > # ospfctl sh rib > Destination Nexthop Path Type Type Cost > Uptime > 195.140.213.0/24 194.9.86.2 Intra-Area Network 20 > 00:00:25 > > # ifconfig carp213 > > > carp213: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> mtu 1500 > lladdr 00:00:5e:00:01:01 > carp: INIT carpdev vlan213 vhid 1 advbase 1 advskew 0 > groups: carp > inet6 fe80::200:5eff:fe00:101%carp213 prefixlen 64 scopeid 0x1f > inet 195.140.213.1 netmask 0xffffff00 broadcast 195.140.213.255 > # route get 195.140.213.30 > route to: 195.140.213.30 > destination: 195.140.213.30 > interface: carp213 > if address: 195.140.213.1 > flags: <UP,HOST,DONE,LLINFO,CLONED> > use hopcount mtu expire > 209 0 0 858 > > The route should be the one distributed via ospf with next-hop > 194.9.86.2, but it isn't. Ok, perhaps better luck tomorrow :-) >
There are still some issues with carp and the routes it modifies on the fly. Ospfd and bgpd have problems to see carp routes as connected. You can force ospfd to redistribute the route by mentioning the network directly in the redistribute statement for now until the real issue is fixed. -- :wq Claudio
