You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I advertise the route 100.0.0.0/8 next-hop self as-path [1 3 4 65412 10] from R1 to R2. The route installed in R2 has the AS path 1 3 4 65412 10 as expected. But R3 receives this route with the AS path 768 1 3 4 10.
Expected behavior: Since I have set the replace-peer-as flag to True in R2's configuration, R2 should remove the AS number 65412 from the route's AS path and replace it with 768. Thus R3 should receive a route with the AS path 768 1 3 4 768 10.
The text was updated successfully, but these errors were encountered:
I have three routers R1, R2 and R3 connected in series.
R1 runs ExaBGP while R2 and R3 both run GoBGP v3.13.0.
R1 is in AS 64512.
R2 is in the confederation AS 1 and sub AS 256
R3 is in AS 256.
R1's ExaBGP configuration is as follows:
Here are the configurations for R2 and R3.
R2:
R3:
I advertise the route 100.0.0.0/8 next-hop self as-path [1 3 4 65412 10] from R1 to R2. The route installed in R2 has the AS path 1 3 4 65412 10 as expected. But R3 receives this route with the AS path 768 1 3 4 10.
Expected behavior: Since I have set the replace-peer-as flag to True in R2's configuration, R2 should remove the AS number 65412 from the route's AS path and replace it with 768. Thus R3 should receive a route with the AS path 768 1 3 4 768 10.
The text was updated successfully, but these errors were encountered: