Replies: 4 comments 7 replies
-
Router C can't forward the traffic back via the same interface it receives the traffic, or I don't understand your case here? |
Beta Was this translation helpful? Give feedback.
-
C node uses the BGP protocol to route traffic from the ens256 network interface to the local network and forwards it to D's ens256 network interface. The ens256 network interface on D captures the request twice, indicating that C node successfully forwarded it. However, the forwarded traffic cannot be found on D's ens224 network interface or any other network interface. How can this issue be resolved? The traffic seems to have disappeared. Thank you. |
Beta Was this translation helpful? Give feedback.
-
yes
…---- Replied Message ----
| From | Donatas ***@***.***> |
| Date | 10/26/2023 18:45 |
| To | ***@***.***> |
| Cc | ***@***.***>***@***.***> |
| Subject | Re: [FRRouting/frr] Ping Request not found (BGP) (Discussion #14643) |
But it has a single interface?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
When A pings B, and C establishes a BGP relationship with D, A can successfully ping B when BGP is turned off. However, when BGP is enabled, C redirects the traffic from D's ens256 network card to the local system and then sends it back to the ens256 network card. The ens256 network card can capture two Ping Request requests, but it cannot capture the Ping Request requests after the replies on ens224 or other network interfaces. How can this problem be resolved?
Beta Was this translation helpful? Give feedback.
All reactions