Nmap package

johnpoz

@jpetovello and what package are you running, what version of pfsense?

What is the actual link your following? You don't show the actual url for example I only see 1 entry and that is this url

https://sg4860.local.lan:8443/nmap_scan.php

I'm running 22.05 showing nmap package 1.4.4_6

jpetovello

@johnpoz running pfSense Plus 22.05 and nmap package 1.4.4_6

First opens to: https://192.168.1.1/pkg.php?xml=nmap.xml
Second opens to: https://192.168.1.1/nmap_scan.php

johnpoz

@jpetovello said in Nmap package:

pkg.php?xml=nmap.xml

I do not see that on my menu for sure.. Strange - was this a clean install to 22.05, an upgrade from what version of pfsense 22.01?

jpetovello

@johnpoz It was a clean install of the latest stable CE, that was upgraded to Plus 22.05. As you can see it appears twice.

johnpoz

@jpetovello so you moved from CE to plus... strange - the one link has m and other big M.. Odd for sure..

Maybe @stephenw10 might have some clue..

jpetovello

@johnpoz The only thing I can think of is that when I installed CE, I used my backed up configuration.

johnpoz

@jpetovello I would think something like that is possible. You could try removing nmap seeing if the both menu items go away. If one is left you could remove it from the config.xml and reload and then reinstall nmap.

jpetovello

@johnpoz Removing the package leaves behind the NMap link but removes the Nmap link. Clicking on the left behind link leads to

johnpoz

@jpetovello I would remove that link from the xml then, and then reinstall nmap that should straighten it out I would think.

If you look in your xml you find the bad link.

		<menu>
			<name>Nmap</name>
			<section>Diagnostics</section>
			<tooltiptext></tooltiptext>
			<url>/nmap_scan.php</url>
		</menu>

Something like that but wrong url..

jpetovello

@johnpoz ~~Okay, how do I go about removing the link? Save the current config to an xml, edit and reload said config?~~

FIXED!

I just edited the live config.xml and rerooted the machine.

johnpoz

@jpetovello great to hear - why it happened is odd though..

stephenw10

Hmm, looks like that was changed here:
https://github.com/pfsense/FreeBSD-ports/commit/7f64c9db1a0f5c0ffc18afe7a9f7a9b9f82f9c67

Not sure how you ended up with both though.