Am Mittwoch, den 20.08.2014, 08:25 +0200 schrieb Henning Brauer:
> > trying to do the same for IPv6, the set nexthop statement in the bgpd.conf
> > has no effect. The cisco receives the prefixes with the non-carp IP of each
> > firewall as nexthop.
>
> that smells like a bug.
I can confirm that I've seen this behaviour also. Yet I thought the
reason would be more of the kind that I did evil things[tm]
to bgpd. And maybe stuff like "::ffff:10.0.0.1" would somehow not be
regarded as a valid next_hop address for IPv6.
Mickael, can you confirm that a route towards "2a02:d48:2f:1c::1:4" is
in your rtable 0 FIB?
-dd
--
David Dahlberg
Fraunhofer FKIE, Dept. Communication Systems (KOM) | Tel: +49-228-9435-845
Fraunhoferstr. 20, 53343 Wachtberg, Germany | Fax: +49-228-856277
