@dschmitz Steve's already pointed you at a way to have the UI show lower memory use, but I wanted to reinforce the point that what your 'top' screenshot shows is not a problem.

It does show that the majority of RAM is in use, but if you look one line lower you can see that 13 out of the 14 GB of wired memory is used by the ARC (ZFS's buffer cache).
That's a good thing. It means that the memory you paid for is doing stuff, rather than sitting around burning electrons for nothing. Once memory is needed for other things (such as pf states, or installing packages or any of the thousands of other things the system does) the ARC will release that memory.

As a general rule, memory usage on modern operating systems is much more complicated than you think it is, even if you take this rule into account.

@dchiang1987 said in SG-3100 upgraded storage to M.2 but disk is still reading eMMC storage:

I tried changing m2dev to 1 and that worked. I modified your second line to run m2boot. Thanks for the tip!

Great =)
Good to know that its working, I remember when that happened to me and it was baddd, hehe.

@terryzb The ARM device install copies the image to disk, overwriting it. Just restore your saved config file afterwards.

Edit: for pfB it will restore whatever is in the config file.

@terryzb said in Console display missing letters 'u' and 'l':

The SiLab driver notes list several bug fix

I will have to take a look see if I am behind in driver version - even though have never seen that issue, I like to be up to date with everything ;)

edit: I was a couple releases behind, was on 11.0 now on 11.2..

@viragomann If i re-run the installer from Clients export in pfsense, then it installs the PCKS12 file i need and in the certificate store. OpenVPN config file is generated to automatically to look at the trust store. So thats what i have been doing to test.
User Cert + 2FA, and no admin rights on this workers laptop...Im happy.

@octopuss That's what I was vaguely remembering...someone that had enabled it then disabled IPv6, or similar. I don't really recall the details.

I suppose another option would be to edit it out of the config .xml file and restore.

By the time a patch makes it into the "Recommended" list it's usually either already included in a newer release or it's been well tested internally and confirmed to solve the problem in question.

A quick update. Today I tried the upgrade again and now IPTV/IGMP is working fine. Upon checking the igmp package I can see that the working version (0.3_1,1) is installed automatically. Always nice to wait a little before upgrade. Thanks and another happy upgrade running here.

I'm running pfSense Plus 23.01 with HPE 561T card, which is basically a HP made X540-T2.
No problems here.

@gertjan Your main post about private/public network looks like it may have been the main thing, then I forwarded the ports for Plex, my old box forwarded them automatically which is odd, looks like that has fixed the main issues. Thanks for the help there, I was losing my mind.

Mmm, that error is usually the result of traffic shaping and isn't usually a problem.
https://redmine.pfsense.org/issues/8991

If you just see two, it's probably OK and a normal part of (re)negotiation depending on which side does what.

If you get more and they start piling up, then you might need to adjust the settings:

https://docs.netgate.com/pfsense/en/latest/troubleshooting/ipsec-duplicate-sa.html

@steveits It worked after the patch. I had already rebooted and tried a few other things, and let it even sit for several days to see it it would drop. Using top it would always have the High memory usage. After that patch, the reboot it has not hit 30% memory usage yet. I feel more confident adding rules and such now. I do believe the patch corrected this issue for me, as I was up to date, at least the system said I was, and I had purchased this netgate 1100 only a couple weeks ago. Thanks again!

Yes, some 1100s don't have eMMC that supports reading that data.

@gertjan - I do know how to do the troubleshooting, I was just trying to avoid the 24 hours for each iteration but I'm sure it will help someone else if they're reading.

I had already updated pfBlocker but it looks like those processes were orphaned from before I updated the package. All seems to be fine now.

By default all traffic inbound is blocked on the WAN anyway so this only applies if you've added a rule to pass traffic.

Generally you would not have DNSSec enabled with DoT but only because you will be in forwarding mod for DoT. You should be able to use them together but it's likely far less tested because there's little point.

@michmoor My CyberPower has been stable with the NUT workaround from the thread I referred to previously.
NUT Screen Shot.png