In reply to a post by SpeedySlow:

What's the difference between all these subnets? Is lower better?

Lower number = more IP addresses.

IPv4 addresses are 32 bits long. If you get a "/32" address that means that all 32 bits are set by the provider, so you only have a single address available.

A "/29" means a prefix of 29 bits from the provider, and the remaining 3 bits are for you to set. This gives 8 combinations from 000 to 111, so it's a range of 8 IP addresses.

In practice, if you use this directly on an ethernet LAN, the first and last addresses are reserved for network address and broadcast address, and one will be needed by your router, so you can connect up to 5 end devices (e.g. servers or firewalls) with unique IP addresses.

All the registries which assign IPv4 addresses have run out, so IPv4 addresses are a scarce commodity and traded at high cost on the open market.

The supposed "solution" was to replace IPv4 with IPv6, which has 128-bit addresses.

There are lots of IPv6 addresses available, and the IPv6 Internet runs in parallel with the IPv4 Internet. Unfortunately you need an IPv4 address if you want to communicate with any other device on the Internet which has only an IPv4 address - and that's almost everything.

Use private addresses on the 'WAN' side of your pfSense box and then have the device you sit in front of it that is doing the PPPoE route a single /30 towards your pfSense VIP giving you 4 public IPs that you can use in NAT rules.

Challenge then is to find an ISP that will do this, but I know that Gamma when you ask for a routed public IP route a /30 towards whatever static IP you're already assigned by PPPoE. The intention is that you configure this on your router but if you use a device that can do its own routes then you don't have to do this. BT Business I think also operates in this way.

In reply to a post by jpm:

Challenge then is to find an ISP that will do this, but I know that Gamma when you ask for a routed public IP route a /30 towards whatever static IP you're already assigned by PPPoE.

Cerberus did this with my /30. It was something.232/30, so I had .233 for the router, and .232 .234 .235 available that I static-routed to loopback interfaces on VMs.

How are you finding Aquiss?

Do you have any smokeping graphs to anything showing the latency consistency of them? I assume your on OR not CF fibre.