I have a few questions about the SG 125w. We have one.
1. how do I block an external public IP address on the firewall? I have noticed in our L2TP over IPSec log that someone is trying to log in as myself using a different internet provider. They have tired using other things to connect but lately it's my account. Nothing stops them I know from changing their IP address all I want is to slow them down.
2. is there anyway to setup L2TP over IPSec to work as a split tunnel connection? According to the Sophos support L2TP over IPSec cannot run as a split tunnel yet I have seen a lot of talk about doing in this forum (previous threads) but no direct method on how to set it up. 
3. other than backing up my profile and reinstalling UTM 9 again on my SG 125w (until we get a better firewall) is there no other way to fix the DB in UTM 9 other than using the rebuild command? Currently our CPU is hitting 95-99% usage since the DB issue started.**
4. Is there any other Remote Access (VPN) option I can use that will work with RADIUS on the UTM 9 SG 125w firewall? I know L2TP over IPSec has a lot of overhead, and in part we are having problems with Windows 11 clients trying to remote in. Previously it was a matter of getting them to uninstall their latest Windows CU to get them working over WiFi (from their remote connection) but now WiFi doesn't work and only having a wired connection works. Using W10 also works in wired/wireless mode. MS has supposedly fixed this issue a couple of months ago but I call BS because at some point when our staff are WFH they complain their W11 machines are having issues getting connecting to, then connecting to their desktops which gives them a black screen. I just don't see any option for SSL to work with RADIUS.
** So I reached out Sophos support, one person recommended to backup my profile and reinstall UTM from scratch again because he didn't see any errors coming from the SSD inside and could figure out why the DB refused to rebuild. He eventually escalated to a L2 (I am going to say) who had a look and was quick to pass the buck back to me saying the CPU is so HIGH because we supposedly have 172 devices behind our firewall and our firewall is only made to support 40 devices behind it max. Which doesn't explain why it was working before the SG was patched two patches ago then it started having this problem. I explained this to the tech and they just didn't care. So I guess we won't be buying any new firewalls from Sophos then.
Thanks,
This thread was automatically locked due to age.
