pfSense

Hello Sean,

I installed the NMap package and am unable to reproduce this issue. Likely your config has two menu items and potentially an older version of the package had different capitalization or something. I would recommend backing up your config, removing the extra menu item that is broken, and then restoring the config. However, I don't believe this is a bug as I cannot recreate this condition with the NMap package.

...Likely your config has two menu items...

I have backups for exported configs...

The one from 2022-05-04 has only the lowercase variant:

<menu>
    <name>Nmap</name>
    <section>Diagnostics</section>
    <configfile>nmap.xml</configfile>
</menu>

the next one I have, from 2022-06-01, had an additional section added (uppercase variant):

<menu>
    <name>NMap</name>
    <section>Diagnostics</section>
    <configfile>nmap.xml</configfile>
</menu>

Notably, on 2022-05-31 our pfsense hardware died and we switched to our backup device by restoring from a backup config.

This was all on pfsense+ 22.01, so we can absolve the 22.05 upgrade from creating these duplicates (though it could have handled them better, perhaps by deleting one).

potentially an older version of the package had different capitalization or something.

That's my guess too.

I would recommend backing up your config, removing the extra menu item that is broken, and then restoring the config.

You mean just cut out the uppercase variant above?

However, I don't believe this is a bug as I cannot recreate this condition with the NMap package.

Well, I think it's very much a bug, just one that does not yet have known reproduction steps. :)

You mean just cut out the uppercase variant above?

That's right. Delete everything between <menu>...</menu> tags (including tags themselves). Save changes and restore configuration with the edited file.

Well, I think it's very much a bug, just one that does not yet have known reproduction steps. :)

Most of the issues after the upgrade are related to the packages. The best practice is to remove all the packages before the upgrade and re-installing them once the upgrade completes. Alternatively, you can perform a clean install and then restore your configuration.

We would need clear steps to reproduce the issue to call it a bug.

Danilo Zrenjanin wrote in #note-3:

You mean just cut out the uppercase variant above?

That's right. Delete everything between <menu>...</menu> tags (including tags themselves). Save changes and restore configuration with the edited file.

Well, I think it's very much a bug, just one that does not yet have known reproduction steps. :)

Most of the issues after the upgrade are related to the packages. The best practice is to remove all the packages before the upgrade and re-installing them once the upgrade completes. Alternatively, you can perform a clean install and then restore your configuration.

We would need clear steps to reproduce the issue to call it a bug.

I agree. This should be marked as Rejected or Not a Bug.