Project

General

Profile

Actions

Feature #6651

open

Loopback interfaces

Added by Slava Bendersky over 5 years ago. Updated 11 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Interfaces
Target version:
-
Start date:
07/27/2016
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:

Description

Hello Everyone,
I would like place request add ability manipulate loopback interfaces through web ui.
Use cases where dynamic routing protocols is in use.
Also it can be useful for different nat configuration.

volga629

Actions #1

Updated by Chris Buechler over 5 years ago

manipulate loopback interfaces in what way? You can already set static routes to lo0 to null route, and add VIPs on lo0. Can't think of anything beyond that you'd need or want to do at the OS level.

Actions #2

Updated by Slava Bendersky over 5 years ago

Assign additional ip addresses like

lo0 1.1.1.1/32
or
lo1: 2.2.2.2/32
or alias
lo0:0 3.3.3.3/32
Actions #3

Updated by Chris Buechler over 5 years ago

you can already do that with virtual IPs on localhost. That doesn't allow cloning lo0 to lo1, though I don't think any use cases of ours would find that necessary or desirable.

Actions #4

Updated by Slava Bendersky over 5 years ago

major think is create additional lo* interface as right now we can define LAN or WAN.

Actions #5

Updated by Chris Buechler over 5 years ago

I'm curious, what use case do you have for additional lo* interfaces?

Actions #6

Updated by Slava Bendersky over 5 years ago

For dynamic routing protocol.
As example border router supply originate option ( default gateway ) and use of lo* to advertise /32 for anycast or mpls and so on.

Actions #7

Updated by Tom Poole about 5 years ago

Loopback interfaces are a cisco best practice for GRE/IPSec tunnels. I would use them for site-to-site IPSec as an interface to NAT from without using a LAN interface since many cloud providers like VULTR limit the MTU on their internal networking.

Actions #8

Updated by Anonymous over 4 years ago

+1 for this request. The ability is there as Chris mentioned, but IPs can only be bound to lo0. Additionally, an option to not sync specific lo0 addresses to slaves would be realy useful.

The use case for me is to bind hostnames / DNS to a lo0 address that is reachable via dyanmic routing over multiple interfaces.

Actions #9

Updated by Slava Bendersky over 2 years ago

Slava Bendersky wrote:

Hello Everyone,
I would like place request add ability manipulate loopback interfaces through web ui.
Use cases where dynamic routing protocols is in use.
Also it can be useful for different nat configuration.

volga629

Is possible raise priority for this feature request. Since VTI tunnels implementation online it even more critical. PLEASE.

Actions #10

Updated by Jim Pingle over 2 years ago

  • Category set to Interfaces
Actions #11

Updated by Christian McDonald 12 months ago

Any movement on this?

This would be really useful. Currently I'm having to create a dummy vlan on a physical nic in order to terminate /32 IPs and announce them using OSPF. In short, I assign the /32 to this interface, set it as a passive interface in my OSPF area and then I can route traffic to this IP (then doing whatever I want with it, 1:1 NAT to an internal server, etc.)

Actions #12

Updated by Christian McDonald 11 months ago

PR Review:

https://github.com/pfsense/FreeBSD-ports/pull/1011

This might not completely solve every use-case, but it at least allows for loopback interface to be associated to an OSPF area and announce IP aliases. This eliminates the need to create a dummy VLAN interface for this purpose.

Actions

Also available in: Atom PDF