Bug in CSV Static Route import with unnumbered interfaces

Reply
L2 Linker

Bug in CSV Static Route import with unnumbered interfaces

Hi!

 

This is related to another bug I just described (Bug in CSV Interface import with unnumbered interfaces).

 

If you import static routes with only an interface (typically a tunnel interface) but without a gateway address, the entry does not get imported.

 

Reasonable if you only ever use ethernet-like interfaces, but needed if you use IPsec VPNs.

 

Workaround: Set a dummy gateway address. It will be ignored (if you don't remove it before putting it in production)

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!