bgpd: Do not convert to ipv6 mapped address if it was modified by route-map #15611
Conversation
…te-map Fixes 0325116 ("bgpd: fix 6vpe nexthop") Signed-off-by: Donatas Abraitis <[email protected]>
|
I'm very gratefull! I'll make some time to take notes on how to recompile FRR in VyOS. Please ignore my ignorance, but wouldn't it perhaps not be better to change behaviour to not override the next-hop when 'attribute-unchanged next-hop' is set on a peer? Our problem with the suggested patch is that the outgoing policy wouldn't know what each prefix's gateway should be, each provider edge router sets this when the prefix is announced to the route reflector. Replacing the prefix's next hop with the route reflector's IPv4 encoded as IPv6 on iBGP route reflector sessions should IMHO be an option, to either disable or enable the behaviour, depending on the default. |
|
I was thinking if incoming or outgoing RMAP is used to change the next hop, then ignore the mapping. Other than that, I'm not much familiar with other edge cases where this might hit also... @louis-6wind do you have an opinion here? |
|
Shall we continue in #15614 ? |
|
Sure. |
No description provided.