pfSense » pfSense Packages

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.

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

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.

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

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

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.

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.

+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.

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.

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.)

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.

lo0/Loopback is added
https://redmine.pfsense.org/issues/11186