GoBGP does not advertise prefixes to neighbor whose AS is present in AS-PATH of prefixes

[ykondratov]

GoBGP docker container is peered with VyOS via eBGP: GoBGP AS = 65000, VyOS = 65001. GoBGP receives from Route reflector prefix with AS-PATH which contains 65001. GoBGP does not advertise this prefix to VyOS. If I set replace-peer-as = true in gobgpd.conf, then it starts advertising with AS-PATH 65000 65000. But that is not desired behavior.

I checked with FRR instead of GoBGP, prefixes are advertised as should (with AS-PATH 6500 65001)

Is there anything I am missing in configuration to allow advertising such prefixes? (Correct me if I am wrong, but to my mind the default behaviour of BGP should allow this without any tuning)

GoBGP speaker config: [global.config] as = 65000 router-id = "10.10.10.1"

[global.apply-policy.config] export-policy-list = ["set-next-hop-self"] default-export-policy = "accept-route"

[[neighbors]] [neighbors.config] neighbor-address = "10.10.10.2" <---VyOS router peer-as = 65001 [[neighbors]] [neighbors.config] neighbor-address = "172.18.0.10" <---- Route-reflector peer-as = 65000

[[policy-definitions]] name = "set-next-hop-self" [[policy-definitions.statements]] [policy-definitions.statements.actions.bgp-actions] set-next-hop = "self"

[ton31337]

Since I tested with more recent versions, it works well with your mentioned setup.

[lastorel]

1. This option works like as-override and not like as-path replace

2. I have noticed that withdrawal mechanism doesn't work on eBGP sessions with option replace-peer-as. It's a bug