12-03-2017 10:31 PM - edited 03-05-2019 09:35 AM
Hi All,
Is there any way to make a ospf neighborship between two routers which are not directly connected.
Say example, R1-->R2--->>R3
Only R1 and R3 need to run ospf and form neighborship.
Can we use gre tunnel? If so, how. Please advice
Solved! Go to Solution.
12-05-2017 07:04 AM
Hi
tunnel destination and tunnel source IP addresses can be used with static routing or dynamic like RIP, EIGRP, or OSPF with different process ID if you are going to use OSPF for the tunnel IP address.
Please don't forget to rate or mark as answered if the comments were useful.
:-)
12-04-2017 02:38 AM - edited 12-04-2017 02:54 AM
Hi
Yes, you can create a L2TPv3 VPN, recommended because it is based IP. Also you can use GRE tunnels as you mentioned. There is other way and it is configuring Bridge group between the routers but I suggest test first with GRE and then L2TPv3.
Hope it is useful
:-)
12-04-2017 04:45 AM
12-04-2017 07:40 AM
I just tested with GRE tunnel in gns3 and it worked without any issues. Like the other member stated just make sure that tunnel source and destination are not advertised through the same ospf domain as the tunnel addresses.
12-05-2017 06:18 AM
12-05-2017 06:41 AM
Hi
You could have something like:
interface tunnel 0
ip address x.x.x.x 255.255.255.0
tunnel destination <neighbor interface or IP>
tunnel source <local outside interface or IP>
router ospf x
network x.x.x.x 0.0.0.255 area 0
12-05-2017 06:52 AM
Adding to Julio's comment. I simply used static routing for IP reachability for r1 to reach r3 interface and vice versa through r2. I didn't have to use any routing on r2 since it was directly connected to both r1 and r3. But you can use any dynamic routing protocol to advertise IPs assigned to physical interfaces.
12-05-2017 07:01 AM
12-05-2017 07:04 AM
Hi
tunnel destination and tunnel source IP addresses can be used with static routing or dynamic like RIP, EIGRP, or OSPF with different process ID if you are going to use OSPF for the tunnel IP address.
Please don't forget to rate or mark as answered if the comments were useful.
:-)
12-06-2017 04:00 AM - edited 12-06-2017 04:34 AM
Hi, Coffee's answer is correct otherwise you will have flapping on the tunnel. Also I suggest take in consideration the overhead, the following config should be added to the tunnel:
ip mtu 1476
ip tcp adjust-mss 1436
GRE includes 24 bytes on the header. So to avoid any trouble the configuration is recommended.
:-)
12-06-2017 04:10 AM
12-05-2017 10:31 PM
It is working fine now. Thanks for all your help.
My only doubt is now , why we should not allow the tunnel source and destination ip in ospf.
12-06-2017 01:30 AM
Running a different process over GRE tunnel (not including real interfaces) and a different process over real interface (not including the GRE tunnel) provides the necessary prevention against recursive routing loops, as these two processes will not leak one to another, causing the real endpoint of a tunnel to be discovered through the tunnel itself.
12-06-2017 04:35 AM
Hi, Coffee's answer is correct otherwise you will have flapping on the tunnel. Also I suggest take in consideration the overhead, the following config should be added to the tunnel:
ip mtu 1476
ip tcp adjust-mss 1436
GRE includes 24 bytes on the header. So to avoid any trouble the configuration is recommended.
:-)
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