@stephenw10 thank you. I thought of using some ETH port as dedicated untagged port in a management VLAN but that seems not to work as intended as I understand. OK: use the next switch for that, I understand. I will see this afternoon if my setup works.

@bmeeks Nice, thanks again

@metacyclic No logs, my observations were not being able to sustain 940/940Mbps using iperf3 or speedtest when traffic source is from a tagged VLAN.

@jimp Sounds about right... I'll get a config backup and reinstall. Thanks

@s0m3f00l https://redmine.pfsense.org/issues/11605

@keyser I would stay on 2.4.5_p1 until a later release. I wish I read that before I updated. After two days I am running on 21.02p1 but the setup is as basic as it gets. I tried restore and manual setup and each time reached a point I had to start over again to get service. I'm not one to complain but this was the one update that makes me want to look around for other options.

@kuser How? I created a ticket specifically requesting it and they sent me the 2.5 patch link instead.

@beard You just download pfsense and install it from a USB stick. You then have pfsense, just as you would with Netgate gear. There's no need for any boot command. Just turn it on and go. When you install from the USB stick, press F11 to cause it to boot from it. Also, you can use the Del key to get into the BIOS, where you may want to change the power restore setting. The choices are off, on and previous state. Since mine is on a UPS, with APCUSD running, I picked on. There are different sources for the Qotom. I got mine from AliExpress and it was shipped from Hong Kong. It's also available under other names. It's also cheaper than the SG-3100, but provides better performance.

@jimp said in SG-3100 LAGG/LACP with Switch: LAGG on the SG-3100 switch with 2.4.4, but at the moment the only supported mode is Load Balance, not LACP This is quite a old Topic - is that still the case even with the latests 21.02?

@naalpv too bad, it's gone ;-)

@stephenw10 tldr: better, but im not convinced it is update related. since loading 21.02 on Feb 19 I have had 119 occurrences of packet loss (gathered from the Gateway log). Since loading 21.02-p1 I have only had 4. Feb 21-23 were not as severe as Feb 19/20. I am still inclined to pin this on my ISP, but things are better for now.

I too am interested to hear from specialists on this topic.

Thanks for the suggestions, always appreciated. I'll pass those to the people making those decisions. Over the years everything has been considered. There's always a compromise to be made. Steve

Yes that's just a note indicating these are free packages: Add optional packages such as Snort or Suricata for IDS/IPS and network security monitoring, Squid for optimized content delivery and SquidGuard for anti-spam/anti-phishing and URL filtering.1 The 1 there should also be superscript. Thanks for noting that. Steve

What were you upgrading from? And I assume it was to 21.02p1 at this point not 2.4.5? Steve

It's not that. It looks like a missing uboot env in that case. On the SG-1100 that does not prevent it booting and running normally. However if you open a ticket with us we can get that fixed for you. Steve

@alpharulez said in 21.02 Sudden lockup: Blog post here for more details: https://www.netgate.com/blog/pfsense-obscure-bugs-and-code-wizards.html How can I find out when the snort issue has been fixed? Thanks for the fix. You can track the Snort issue here: https://redmine.pfsense.org/issues/11466. This one may take several days to figure out and clear up.

@stephenw10 Again, thanks. Paighton sent everything over after I had called it a night. Downloaded what I needed this morning and have updated my restore docs with the info he sent. Over the years, I've found this the best way to get Murphy to look somewhere else to cause trouble. Rick

@stephenw10 said in SG-3100 system activity displaying wrong info: Yes, see the bug. That value is completely invalid for some reason. If you run top from the command line (NOT in the gui) top -aSH you will see the first pass produces that bogus value but all subsequent passes are correct. Because the page in the gui works by repeatedly running single passes it always appears incorrectly. Steve Thanks Steve, I'm not a programmer, so your words help me to understand what is happening under the hood. :)