Sven, > also various bgp implementations will send the autoconfigure crap ip as the > next-hop instead of the session ip, resulting in all kinds of crap in your > route table (if not fixed with nasty hacks on your end ;) which doesn't > exactly make it easy to figure out which one belongs to which peer > all the more reason not to use that autoconfigure crap ;)
As per RFC 2545 BGP announces a global address as the next-hop. Its only in one particular case that it advertises both global and link local addresses. So, i guess, BGP is not broken. Its only RIPng afaik that mandates using a link local address. Glen
