Static Routing - persistent path
Hi,
I'm trying to set up few static routes between ER707 and ER605. Everything works fine unless those two devices looses their connection. Which is typical afaik, once there is no connection, the static route got terminated form the table.
Unfortunately, once the connection is back online, the static route does not get back into the table.
Is there a way to set up Persistent Static Route, which will try to forward packages no matter if the link is up or down (and drop packages when the link is down ofc)?
I've tried to find any info on that in manuals, this forum or reddit. No luck tho. I know such setting is possilbe in Cisco for example...
Thanks for any help,
Cheers
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @RaRu
Thanks for posting in our business forum.
RaRu wrote
I'll check the Wireguard later this week, thanks :)
Thank you for your input and test!
Are there any plans for implementing persistent routing in the future or not yet?
Cheers
RaRu
Not yet. Based on my discussion with the dev, no plans or any prior requests on this.
He recommended you consider IPsec while you have a dilemma here with the public IP. That's not gonna work. I come up if you may have a better result with the WG.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi,
Thank you for picking it up. I'll try to cover that with screenshots.
So, I have a VPN connection between ER707 (server) and ER605 (client). It is old L2TP setup (for now, for testing).
Whenever VPN connection drops and get reconnected automatically, the static routing stops working. Here you can see, that VPN connection is established (after reconnecting automatically):
And in theory, there is proper record in Routing Table (as it should be):
But if you would like to access the subnet 192.168.10.X, you get time out (ping) and no route (tracert) - or to be more specific, the traffic goes to WAN...
In order make it work, I have to go back to Routing settings, edit the setting (change value and change it back) and save:
It doesn't matter if I choose direct IP (192.168.20.20) or general (192.168.20.1).
After that the Routing is back up and running:
Until the next VPN reconnect...
Any idea how I could fix that? to make is running all the time (whenever VPN reconnect?
Cheers
- Copy Link
- Report Inappropriate Content
Hi @RaRu
Thanks for posting in our business forum.
Diagram of the network with IP specified is needed.
It's IPsec site-to-site, more specially speaking?
When the VPN is disconnected, and it reconnects, what's the difference in the routing table?
- Copy Link
- Report Inappropriate Content
Not the best diagram but hope it's good enough :)
The connection is L2TP Client-to-Site since the site B has private IP address from ISP.
After VPN reconnection there is no difference in Routing Table, at least according to what Omada Controller's interface shows. But the routing itself doesn't work. editing the routing rule restore the connectionbut still, shows exactly the same value in Routing Table.
- Copy Link
- Report Inappropriate Content
Hi @RaRu
Thanks for posting in our business forum.
RaRu wrote
Not the best diagram but hope it's good enough :)
The connection is L2TP Client-to-Site since the site B has private IP address from ISP.
After VPN reconnection there is no difference in Routing Table, at least according to what Omada Controller's interface shows. But the routing itself doesn't work. editing the routing rule restore the connectionbut still, shows exactly the same value in Routing Table.
With the given information, it is pretty clear but strange. I will bring this case and consult with the dev.
- Copy Link
- Report Inappropriate Content
Hi @RaRu
Thanks for posting in our business forum.
RaRu wrote
Not the best diagram but hope it's good enough :)
The connection is L2TP Client-to-Site since the site B has private IP address from ISP.
After VPN reconnection there is no difference in Routing Table, at least according to what Omada Controller's interface shows. But the routing itself doesn't work. editing the routing rule restore the connectionbut still, shows exactly the same value in Routing Table.
I consulted with the dev and this is expected behavior at this time.
When the tunnel is up and the routing entry is there, this static routing will be effective until the VPN tunnel(interface) is lost/disabled.
We indeed don't support the persistent routing entry yet. This is reproduced in the lab and we monitored its background process.
If possible, will you try the WireGuard VPN if that's an alternative type to address the issue you have now?
- Copy Link
- Report Inappropriate Content
I'll check the Wireguard later this week, thanks :)
Thank you for your input and test!
Are there any plans for implementing persistent routing in the future or not yet?
Cheers
RaRu
- Copy Link
- Report Inappropriate Content
Hi @RaRu
Thanks for posting in our business forum.
RaRu wrote
I'll check the Wireguard later this week, thanks :)
Thank you for your input and test!
Are there any plans for implementing persistent routing in the future or not yet?
Cheers
RaRu
Not yet. Based on my discussion with the dev, no plans or any prior requests on this.
He recommended you consider IPsec while you have a dilemma here with the public IP. That's not gonna work. I come up if you may have a better result with the WG.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 232
Replies: 8
Voters 0
No one has voted for it yet.