12-05-2022 01:06 AM - last edited on 12-06-2022 01:36 AM by Translator
IP add of VPC1 is 192.168.1.10 , VPCS 2 is 192.168.2.10
GRE tunnel is configured between R3 and R4.
Tunnel is up and I am able to ping the VPC2 from VPC1 and vice versa, however if I take a capture I couldn't able to see the Tunnel IP being encapsulated.
Solved! Go to Solution.
12-05-2022 04:15 AM - last edited on 12-06-2022 01:24 AM by Translator
you need these two command.
R3
ip route 192.168.1.0 255.255.255.0 184.50.255.193
REMOTE router
ip rotue 192.168.2.0 255.255.255.0 184.50.255.192
note:- in mid router you dont need these static route
S 192.168.1.0/24 [1/0] via 4.15.133.218
S 192.168.2.0/24 [1/0] via 23.50.138.134
12-05-2022 01:22 AM
capture do you use filter ?
12-05-2022 01:26 AM
No I didn't use any filter.
Other than ICMP no other traffic is generated.
12-05-2022 01:35 AM
what software you use eve-ng or CML ?
12-05-2022 02:32 AM
I am using eve-ng
12-05-2022 02:41 AM
https://support.cloudmylab.com/portal/en/kb/articles/wireshark-capturing-on-eve-ng-pro-24-2-2019
use wireshark to open capture traffic, check link above
12-05-2022 03:30 AM
Problem is not the filter or wireshark, I can see the ICMP packets from wireshark but not the actual encapsulated IP.
12-05-2022 03:41 AM - last edited on 12-06-2022 01:17 AM by Translator
Ok,
share the config I will check it
what I suspect you mistake config the static route
ip route x.x.x.x y.y.y.y <tunnel destination> <<<-- this wrong
you need
ip route x.x.x.x y.y.y.y <tunnel IP> <<<- this is right
the static route to remote peer tunnel IP end shift the traffic to enter the tunnel.
12-05-2022 04:12 AM - edited 12-05-2022 04:14 AM
Yeah that's right. may be the route issue.
let me change and check
12-05-2022 04:15 AM - last edited on 12-06-2022 01:24 AM by Translator
you need these two command.
R3
ip route 192.168.1.0 255.255.255.0 184.50.255.193
REMOTE router
ip rotue 192.168.2.0 255.255.255.0 184.50.255.192
note:- in mid router you dont need these static route
S 192.168.1.0/24 [1/0] via 4.15.133.218
S 192.168.2.0/24 [1/0] via 23.50.138.134
12-05-2022 04:19 AM
Thanks , it is resolved now.
12-05-2022 04:20 AM
you are so welcome
12-06-2022 12:02 AM
Can you also suggest me how to achieve this with the help of BGP(Instead of static route)
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide