PPPoE: assign a public IP octet

Started by trigg3r, Today at 09:03:15 AM

Previous topic - Next topic
In my OPNsense 25.7.11_9-amd64 FreeBSD 14.3-RELEASE-p7 OpenSSL 3.0.18 I need to activate a second WAN interface to connect to the new provider and reconfigure services before deleting my current provider configuration.

Following the instructions, I created VLAN 100 (vlan0.2.100), which I then used as the "Link interface(s)" in the new PPPoE point-to-point device, which I then associated with the WAN2 interface (opt1).

Everything works fine.

The problem is that the PPPoE connection automatically assigns the public IP 1.2.3.4 to the interface, but I purchased a set of public IPs, so I need to set the public IP 5.6.7.8/29.

I tried setting this address in the "Local IP (vlan0.2.100)" field of the PPPoE device configuration, but if I edit the PPPoE device configuration again after saving it, I notice that the IP hasn't been saved (and I don't find any error messages about this in the logs).

Can someone tell me the correct way to handle this situation? (I haven't found any instructions on this in the official documentation.)

Thanks

If you got a public /29 the idea is to assign one of the IP addresses to a local DMZ interface and place the servers with the rest of the addresses in that network.
Deciso DEC750
People who think they know everything are a great annoyance to those of us who do. (Isaac Asimov)

... or if you want to use the additional IPv4 addresses for local services on OPNsense, you can configure additional loopback interfaces with them.
... or if you want to use them for NAT, you can add them to the WAN2 interface using virtual IPs.

So it really depends on your use case.

Cheers
Maurice
OPNsense virtual machine images
OPNsense aarch64 firmware repository

Commercial support & engineering available. PM for details (en / de).