Unable to delete an (unused) IPv6 gateway. Is this a bug?
-
Cross posting in this topic for better visibility.
Netgate 6100 on 23.09.1.
Please see https://forum.netgate.com/topic/185567/unable-to-delete-an-unused-ipv6-gateway-is-this-a-bug for details.
I think it may be a bug?
-
Is the new WAN using DHCPv6?
-
@stephenw10 Yup, that is what is in the configuration. It's not live (or even connected) yet so I can change that if it will allow me to delete the gateway...
UPDATE: If I change the interface to 'Static IPv6 address' then I can delete the errant IPv6 gateway, but if I then change the interface back DHCP6 (or SLAAC) then it autocrats a gateway with an unhelpful name which I cannot then delete.
My solution, which I think is okay, is to:
-
Change the interface to Static IPv6.
-
Delete the badly named IPv6 gateway.
-
Explicitly create a 'dynamic' IPv6 gateway on the WAN interface giving the gateway a sensible name.
-
Change the interface back to DHCP6 - it seems happy to use the pre-created gateway and doesn't autocreate another one.
Hopefully this will be okay... This GUI behaviour seems kind of weird to me, though if it allowed gateways to be renamed then there would be no issue.
-
-
A dhcp connection will create a dynamic gateway even if you have not added one manually. It will be available to edit so you can set any custom values on it.
-
@stephenw10 Yes, the auto created gateway is available to edit, but you are not allowed to change it's name. The GUI allows you to change the name but when you try to save it it gives an error saying that gateways cannot be renamed. Is there some reason why gateways cannot be renamed? It's an annoying restriction; you can rename almost every other object in pfSense.
-
I'm not sure exactly what the limitation is there but it's always existed. It looks like the required abstraction code does not exist. Yet.
https://redmine.pfsense.org/issues/13294 -
OK I'm wrong it looks like it was restricted in 2.0
: https://redmine.pfsense.org/issues/883 -
@stephenw10 So they fixed a bug by adding a restriction (instead of actually fixing it). Nice... Any way to enter a feature request for this (not that I would expect it to arrive any time soon)?
-
You can add comments to the feature request I linked: https://redmine.pfsense.org/issues/13294
-
@stephenw10 Done
