@stephenw10 Sophos Connect clients use 3 service strongSwan, OpenVPN and Sophos Connect to allow the configuration of both SSL VPN and IPSec. Our staff use both depending on usage however after seeing the logs it looked evident the culprit was the user plugging into the voIP phone port. The rules are very strict as to what vlans can do what.
If you are on something older than 23.01 (e.g. 22.xx), you have to upgrade to 23.01 first, then you can go to 23.05.
If you are already on 23.01 and can't get to 23.05, then there may be a problem.
@mpcjames fair enough. Your situation is probably different from mine as I'm a homelabber who has an out-of warranty router. For me, the option would be to buy a new device which isn't in the budget anyway.
@cable_label Ok, so you didn't submit a ticket earlier when suggested -- I was asking what the ticket was for the previous TAC interaction. Follow the instructions I provided on the ticket response so we can work to get to the bottom of the issue you are experiencing.
@RobbieTT said in System Tunables on Netgate Hardware - Not Active?:
hope you get upgraded to FTTH in the near future!
Me too but it doesn't look like it will happen any time soon.
@stephenw10 Relevant messages were off the screen by the time I looked and nothing jumped out in the processes. I hooked up a console to grab logs and it was in single user mode. Odd. I rebooted and sure enough everything came back like before (all services) and the blue LED is back in the normal booted state.
I’ll keep an eye on it to see if it happens again.
@stephenw10,
I think that captures it very nicely!
Phizix
P.S. I actually own an SG-3100 which I have not used much as I switched to SG-5100, and I copped another SG-5100 on eBay for a very good price as a backup.
@Gertjan
I do have that ticked.
I have connected my switch the firewall. And when assigned all to the port I can access the net, however when I assign one of the VLANS i do not have access to the net. I only have one firewall rule to allow all traffic. Is there something I could have done wrong when creating the VLANS or is the problem in the switch setup?
It probably failed to upgrade completely. I'd guess you're running a mismatched kernel and world.
Try option 8 to drop to the CLI, that usually works in that situation. Reboot from there but just entering 'reboot' and check for errors at boot on the console.
You may need to reinstall if it can't be recovered so do you have a backup of the config?
Steve
You would still see output from uboot at the serial console if it's connected correctly.
https://docs.netgate.com/pfsense/en/latest/solutions/sg-1100/connect-to-console.html
Steve
@Amenophisphp Yes it is when it comes to configuration. It will not contain any logs or statistics from usage, but that is not needed (only for historic performance analysis)
Yes, the only time you should have to do anything with the uboot envs is if you change the boot device. So usually only if you add an m.2 SSD.
See step 7 here: https://docs.netgate.com/pfsense/en/latest/solutions/sg-3100/m-2-sata-installation.html
Hard to know exactly what happened to @eyes here without seeing the boot loop output. We have seen the uboot envs become corrupted in the past so that is possible. That would require rewriting them.
Steve
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.