BGP, "Invalid NEXT_HOP attribute"

[Lexi Winter]

Ondrej Zajicek:
> Note that confederations in BIRD are a bit tricky. There are two styles:
 
> 1) Shared IGP:
> In this case, intra-confederation EBGP links should have an option
> 'gateway recursive', so bgp_next_hop is resolved recursively through
> shared IGP routes.
 
i see, i thought EBGP with a confederation peer would use recursive next
hop resolution by default (since NEXT_HOP is propagated unchanged in
this case, like in IBGP), but if not, this could be related.  i will
configure 'gateway recursive' explicitly on my peerings and see if this
makes any difference.

(i don't use 'next hop self' since my IGP covers the entire network.)

> I received that, sorry for not replying earlier. Will check that.

no rush at all, i was only wondering because i know sometimes mail
delivery from non-Google/Microsoft addresses can be an issue these days.