if at xip.at
Thu Sep 30 17:01:10 CDT 2010
> i was recently bitten by a cousin of this
> research router getting an ebgp multi-hop full feed from 188.8.131.52
> (address is relevant)
> it is on a lan with a default gateway 42.666.77.11 (address not
> relevant), so it has
> ip route 0.0.0.0 0.0.0.0 42.666.77.11
> massive flapping results.
> it seems it gets the bgp route for 184.108.40.206/16 and then can not
> resolve the next hop. it would not recurse to the default exit.
> of course it was solved by
> ip route 220.127.116.11 255.255.0.0 42.666.77.11
> but i do not really understand in my heart why i needed to do this.
last time severall years ago on cisco I used a route-map to rewrite the
route-map xx-in permit 10
set ip next-hop 42.666.77.11
route-map xx-out permit 10
set ip next-hop x.x.x.x
neighbor 18.104.22.168 remote-as yyy
neighbor 22.214.171.124 ebgp-multihop 8
neighbor 126.96.36.199 route-map xx-in in
neighbor 188.8.131.52 route-map xx-out out
something like this.
More information about the NANOG