Do you have a wireguard connection still? A wireguard interface? If not you should remove (or disable) those rules with that alias in them.

@JKnott COOL!!

Mmm, indeed. If you really need UPnP then lock it down to only known devices.

I ordered two of these and put them in my Netgate 6100 Max with TNSR and they are not recognized. Running 22.10 software. Does it need an update? Well, after reading the reddit post and seeing this comment - It’s a 10G module, so it won’t connect at 1G or 2.5G - I found my problem. I was testing to a 1 Gig port on a Cisco switch. Moved it to a 10G port on server as a temporary workaround and its up now.

@stephenw10 Given that the interface status is "no carrier" I don't think there is a physical connection to either a host or a switch.

@stephenw10 That's good news. Just don't want the issue to carry over and get in a bind.

i agree with backing up any of the files that are changed. The openssl.cnf file edits was something I did not see many topics within this forum. As I was comparing a signed CSR using a customer ICA/CA generated from the pfSsense web UI against ACME, I wanted to ask this question. The signed certificate has an intended use within Cockpit within a number of server (not connected to the internet). Naturally the environment will have a different CA generated. While the signed CSR from pfsense works well for Apache, Nginx, HAproxy, etc, other applications were not as accepting. I did add my ICA/CA chain to the server's OS. This lead to me to check out the options in the openssl itself (to see what pfSense uses). Thank you for the responses. I was going to attempt to edit the openssl.cnf and try that.

@CharlesT so the speakers on the iot are the upstream.. But the speakers are not found via multicast they are found via mdns.. Well that works out for you then I would think you can talk to your speakers from multiple networks.

@JohnUtiu Too bad, we could not find out what was going one with the 15.xxx ip's. Maybe the ntopng community has an idea about it. I will let you know if I find out what was going on.

Notably, the NDI changes when network cards are changed.

@stephenw10 Yes I've seen that on my XG210 Rev2

@QuantumParadox said in upgrade error message in pfsense dashboard GUI: I am on version 24.03 An ID is always something unique. As we are all on 24.03, that number can't be an ID. This one is : [image: 1719384028234-90af6c4c-68bc-480d-9a30-b9f20a0e294c-image.png]

If you had something creating a picture with all your devices.. Say something like this.. [image: 1719348485993-devices-resized.jpg] And then you had some way to input some parameters like port.. It could show you which other devices the firewall rules allow for.. But even viewing it gets tricky when you have lots of devices.. This is only showing my wireless devices, and you have to really zoom in to see anything. And while pfsense can say hey there is a rule that allows that to these other devices in other networks.. Still doesn't know if that device even listens on that port, or that its own possible firewall allows it. And as you mention how would it know if something like private vlans or AP isolation is deployed? Is this AI going to validate every connection is actually possible from the devices IP address you selected as your source? And for stuff on the same network as your client, pfsense isn't involved anyway.. I have worked on many a different firewalls, Palo's, ASAs, Juniper, checkpoints way back in the day.. The only thing I have seen that would come close to what your asking that isn't graphical is where you can put in some parameter(s) and it will list the rules that mention those parameters, you can do with panorama for the palos.. But not freaking cheap! ;) But I do not see how this helps you learn to be honest.. If you want to learn.. Learn how to create the rules you want to allow or block and how to create those.. I mean how many rules could you possible have? Its not like enterprise, previous gig we had over 50 different Palo firewalls in the org, and searching for what rules might allow or block specific traffic was really a requirement.. There were 1000's and 1000's of rules across the org.. Finding out if some specific traffic was allowed or not would of been painful if there wasn't a way to easy search through them.. Biggest save in search in rules was when someone requested something to talk to something else on port X.. Was to search for if those devices are already allowed to talk to each other one some ports so you could just add the port to an existing rule, etc.

After set that checkbox? Hmm, try restarting arpwatch. Though I would have expected that to happen anyway...

You can run: pfSense-led.sh update 0 That will clear the update alert. It be interesting to see if it comes back. It does look like there may be an issue.

Regarding using shellcmd to start the iperf3 server ... be sure to include the "-D" option or your boot-up will hang in difficult-to-identify ways. My start-up command in shellcmd is iperf3 -s -D If you look at your firewall console and don't see your usual menu or login prompt after setting iperf3 to start on boot, a Ctrl-C will get you unstuck. If this sounds like the result of a painful experience ... well, yes.

Little update for this shell script in case You have MULTIPLE WAN (and need testing each uplink connection): THIS SCRIPT SENDS HEARTBEAT ON ONE (1) CERTAIN TEST ID. So, if You need really monitoring all WANS and receiving SEPARATE ALERT on EACH WAN,- You may create several Tests on StatusCake and USING V.2 OF THIS SCRIPT #!/bin/sh # HEARTBEAT to StatusCake external monitoring and alerting service # Examples and additional information # https://www.statuscake.com/kb/knowledge-base/what-is-push-monitoring/ # Successfully working on pfSense CE 2.7.X # List of network interfaces INTERFACES="igb10 igb11 igb12 igb13" # StatusCake URL URL="https://push.statuscake.com/?PK=123456764226&TestID=7347942&time=0"" # Loop through each interface and send a curl request for INTERFACE in $INTERFACES do echo "Sending request through interface $INTERFACE" /usr/local/bin/curl --interface "$INTERFACE" "$URL" echo "" # Print a newline for better readability done YOU MAY TEST exactly script from Diagnostic / Command Shell TO ENSURE THAT ALL ARE WORKING as expected! The result MUST be looks like this: Sending request through interface igb0 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 7 100 7 0 0 12 0 --:--:-- --:--:-- --:--:-- 12 success Sending request through interface igb1 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 7 100 7 0 0 13 0 --:--:-- --:--:-- --:--:-- 13 success Sending request through interface igb2 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 7 100 7 0 0 13 0 --:--:-- --:--:-- --:--:-- 13 success Sending request through interface igb3 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 7 100 7 0 0 13 0 --:--:-- --:--:-- --:--:-- 13 success P.S. 1. After testing on exactly Your setup, You MUST comment both ‘echo’ command to avoid unnecessary output to terminal. 2. logger’ command not using also: because of a lot of calling (1 time / min, 1 time / 5 min,…) system log would be filled by unnecessary records that not helping You even when You have automatic log aggregator & analyser like Splunk, ELK, Graylog,….

No worries let us know if that fixes it.

@JonathanLee I guess that was me, almost lost in the noise. Anyway thanks for tidying. ️