Missing IPv4 Configuration Types

[bladesong]

Having recent changed internet providers I was looking to change my WAN configuration from PPPoE to DHCP.

Now, what have I don't to my setup which is causing only the follow 4 configuration options to appear?
login-to-view

And more importantly, what do I need to do to get DHCP back as an WAN configuration option?

Current running pfSense 2.6.0 inside a proxmox VM if that makes a difference.

[Jarhead]

@bladesong
PPPOE0, the zero probably means a sub-interface.
Go to Interfaces/Assignments and see if you have the parent interface as an option. If so, assign it as the WAN.

[bladesong]

Cheers for the quick reply :)

Interfaces > Assignments
login-to-view

and available options
login-to-view

Don't appear to show a parent interface. I'm fairly sure I never set such a thing up. I have a interface for WAN, one for LAN, and a couple of virtual interfaces for OpenVPN and to access the bridged modem.

[chpalmer]

@bladesong

Look at the drop down for your WAN interface. Delete your PPPOe instance. on the PPPs tab on that page.

[stephenw10]

You can only use a subnterface type there (PPP) because you already have vtnet1 assigned as a different interface.
Delete the ModemAccess interface and you should then be able to set WAN as DHCP.

Steve

[bladesong]

@stephenw10 said in Missing IPv4 Configuration Types:

Delete the ModemAccess interface and you should then be able to set WAN as DHCP.

And then I can recreate the ModemAccess interface to access my bridge modem?

[Bob.Dig]

@bladesong You don't need to, it will run over the WAN-connection, I would guess.

[stephenw10]

Yes, but not in the same way. Depending on how the 'modem' is setup you may be able to access it without doing anything since it's now in the traffic path (no ppp encapsulation).
However you may need to add an IPAlias VIP in the modem subnet to WAN and add an outbound NAT rule on WAN to catch the specific traffic for the modem and translate it to that VIP. That way the modem has a way to respond to queries coming from inside the firewall.

Steve