@insmod since pfsense is designed to be managed via the web gui, while some stuff can be done via the cli, ie either consoled in or via ssh. What you can do via management is going to be limited via that.

Your best bet is to just limit who can access the gui.. Create firewall rules that only allow from say your management network, or admin machine.

For example - the web gui is only available via my lan network, only devices on my lan are my main PC, and my nas - all my other segments have no access to the web gui via simple firewall rules blocking access to "this firewall". Dns and ntp is allowed, icmp - but they can not access the web gui port or any other service on the firewall, on any IPs be it its other lan segment Ips or even its public IP from lan side networks.

example: here is a locked down segment that would have no access to the firewall gui, or anything else on any pfsense IP other than ping, dns and ntp.

lockdown.jpg

@SteveITS Got it,thanks!

It's a really handy feature now and I have already used it to diagnose something on the WAN side.

A really helpful improvement on the original pcap function and I appreciate the effort people put into it to expand its functionality. 👍

☕️

remaining images
@FSSantanaJr 05.png
06.png

pfSense software does not include an API like that.

You may have installed some kind of third-party add-on to act as an API, in which case you need to consult their documentation about key management.

@jimp Damn it. Should of looked further. We deploy Atera RMM and I have a scanning agent on that server/IP. I will take the router out of the scan.
Thanks @jimp for catching that!

@jimp Thanks, i never used system patches package before.
everyday is a day you can learn something new ;)

@steveits The problem seems to have been resolved but I am not sure why. I moved around and reconfigured a few of the widgets and rebooted late last night. (I swear it is harder to get "change management" approval at home than in an organisation of 7500 people 😉 ) I no longer get the error.

Thus, it could have been (a) by moving around the widgets it "fixed" a corrupted configuration; or (b) there was something hanging around in memory/cached/etc. that rebooting cleared out.

Adding the search/filter bar on there wouldn't be difficult. Nor would a new add button. The frame/scrolling part is not as simple and is unlikely to be viable.

You can open feature requests on Redmine for the search part and the add button. May not make the next release but we can get them in before too long.

I feel dumb, forgot i installed UniFi-Poller along with other dockers to better monitor the UDM. I failed to shut it down, so it was looking for something that wasn't there

@altonwoods
Find out the parent in Status > Interfaces.
Then go to Interfaces > Assignments, edit it and state the MAC.

@mulantis Same error here, even if i create a new channel in slack and try to save. Did you manage to find something?
Thanks

The last time that came up it was because some value being passed through those functions was actually an IPv6 address and not an IPv6 subnet definition.

It's not clear exactly which one it might be in your case since that function would read through not only all IPsec P2 entries but also mobile IPsec, but you might check the addresses you have in each of those places. If you have something defined as a subnet but you've actually defined an IP address inside the subnet instead of the subnet itself, it might hit something like that.

For example if you are supposed to define a /64 size IPv6 subnet/prefix but you pass it x:x:x:x::1/64 that is an address, not a prefix, it should be x:x:x:x::/64. But again it depends on context.

If you could post your IPsec section of config.xml that would help, you can remove the secret parts (PSKs, cert metadata like subjects/identifiers, etc), but please mask the addresses for privacy rather than removing them, keeping something in those places so we know the general values. Like you could replace fc80:1234:5678:9abc::1 with xxxx:xxxx:xxxx:xxxx::1

@gertjan

23.01-RELEASE (amd64)
Version 111.0.1661.54 (Official build) (64-bit) and the newest version

My and for the late reply thanks for the help

router.domainname.com is what I am putting in.

Thanks Jim!