Bug in CSV Interface import with unnumbered interfaces

Reply
L2 Linker

Bug in CSV Interface import with unnumbered interfaces

Hi!

 

Running Expedition 1.1.28.

 

I recently begun importing tunnels via CSV import. I have discovered that interfaces with type (media) "tunnel" are ignored if they are not assigned an address at all. Tunnel interfaces often don't need addresses asigned, especially if they are used with static routing and next-hop is the interface.

 

Performing an experiment with an ortdinary ethernet interface shows the same thing, without an address ethernet interfaces are not imported either. This is more understandable, as this could be en error in the CSV file.

 

Request: Please allow importing interfaces without IP addresses, at least for those media types where it makes sense.

 

/Per

L2 Linker

Re: Bug in CSV Interface import with unnumbered interfaces

Workaround: Set a dummy address, then it will be accepted. The address can be removed later.

 

/Per

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!