Renaming interface

[g405tsh311]

Trying something extremely easy but, here it goes again down the rabbit hole with pfSense. Centralizing pfSense QA it seems not to be working so hot!!!

Changing the description for any of the interfaces in pfSense shall not be that difficult, correct? Wrong! Changing the description for an interface has become a nightmare.

Changed the description, saved it and the following error pops up:
.
Following the instructions proceeded to the services area to check for IPv6 services, which there were disabled in the past. After accessing DHCPv6 Server & RA the following error is displayed:

At this point, there is to wonder, if there is not DHCPv6 running why there is an error when changing an interface description?

There is a work around where, enabling IPv6 with DHCPv6 allows for the description to be changed. Except for the fact that the interface will drop when the changes are made and either pfSense needs to be access from another system oooorrrr connect directly to the appliance.

Is it possible that there is a bug somewhere that needs to be reported?
Any advice from the community with helpful insights?

As always, thank you in advance for your kind responses.

[AKEGEC]

@g405tsh311
Navigate to Services to disable DHCPv6 Server & RA (Router Advertisements) and DHCPv6 Relay.
After that disable Allow IPv6 in System>Advanced>Networking. Also Change all IPv6 in interfaces IPv6 configuration select to None.

[johnpoz]

I would say you ran into this maybe
https://redmine.pfsense.org/issues/11609
CLI configuration without IPv6 leaves RA enabled.

[AKEGEC]

@johnpoz I don't know what pfsense version g405tsh311 has, but it could be just a bug.

[johnpoz]

Yeah - bug which is why its in redmine ;) Already noted and a fix is out for it, etc.

[g405tsh311]

@AKEGEC
Please re-read my post since what you were recommended was already done. That is why I was receiving the error.
Thank you for your feed back though,

[g405tsh311]

This post is deleted!

[g405tsh311]

@akegec

That would be 2.5.1. Latest version.
Against my best judgement I decided to upgrade to the latest version which has tons of bugs.

[g405tsh311]

@johnpoz

I went to the link that you mentioned but it is a dead end.
Basically a 404 page.

[johnpoz]

No its not a 404 page..

[g405tsh311]

@johnpoz

Thank you much!!!
For some reason it was coming unavailable when I searched for the link.
The proposed solution was applied and seems to be working correctly.

Thank you again.