BWC Cybersecurity Overlord ✭✭✭
Reactions
Comments
-
@MikeMurray I guess you answered your own question already. Because the SNWL does not know about the VLAN Interfaces it cannot assign IP addresses via DHCP to it. You can create the scopes and they'll end up with no Interface Assignment (n/a). The DHCP Server on the SNWL is pretty basic and cannot work on conditions etc.…
-
@KaranM MSW is back, thanks for checking into this. But was there an update on MSW, because the whole UI is in german now, which I don't prefer and cannot change in an obvious way? --Michael@BWC
-
@Erdal I don't have access to a SMA right now, but did you checked the logs for dropped traffic? Did you do a packet capture to see if the DNS requests really getting routed into the Tunnel? --Michael@BWC
-
@coopsnoop SentinelOne is comitted to support macOS Ventura with Agent 22.2+ which is currently EA and not available via Capture Client. Most Endpoint Protection solutions delay OS upgrades these days and should be postponed until proven good for a new release. It's even harder to test on pre-releases of an OS, maybe macOS…
-
@Erdal did you tried to add the external Domain Suffix (xyz.com) to the VPN connection to have the requests answered by your VPN DNS Server which holds the information? --Michael@BWC
-
@KaranM is there a known problem with MSW (Status does not show anything)? Because all I'am getting is a blank page for https://www.mysonicwall.com/muir/login. Tested in different browsers, same outcome. --Michael@BWC
-
Tim, confirmed over here as well. It might be related to the CAS login problems mentioned over here: https://status.sonicwall.com/ --Michael@BWC
-
@hamod I faced this situation plenty of times, just make sure that you're running the latest Firmware which is 6.5.4.11 for Gen6. This fixed a lot of issues and most of my VPNs are fine now. For the remaining troublesome connections I experienced that IKEv1 (MainMode) is working better than IKEv2, especially if a Router…
-
@cecyoung try to access with Firefox or an older browser. Another option would be to update the Firmware to the latest version, then you should be able to access with a current browser again. That's a burden which affects all "older" Hardware and Software, new Browsers cannot access anymore. --Michael@BWC
-
@jtpryan long story short, it'll not work with the integrated 2FA but can be accomplished with a radius based solution (RSA, etc.). --Michael@BWC
-
In the spirit of Columbo "Just one more thing", if you do a ping from a system behind the firewall, these response times will spike as well? --Michael@BWC
-
@PietroCeribelli then I'am out of ideas for the moment. Maybe someone else got a bright idea, at least we covered the basics. --Michael@BWC
-
@PietroCeribelli then I guess we can rule out temporary CPU spikes. Anything else these interfaces have in common, using some form of WAN-Switch when you're in a HA situation? Or did you tried to ping a different destination, to rule out it's 1.1.1.1? --Michael@BWC
-
@PietroCeribelli I would check for Core0 which is IMHO the Core where this SD-WAN checks operate. It's a bit confusing because on the Mulri-Core Monitor it starts with Core 1 but the Core Monitor (which you screenshoted) starts with 0. You need to monitor this Core load while SD-WAN freaks out. This might be hard to catch,…
-
@PietroCeribelli I never experienced something like this, but because the problem is recurring could you check with the Core Monitor if there is a CPU spike which could cause the SD-WAN Probes to fail or acting strange? It looks something system related to me, and CPU Core0 would be my first guess. --Michael@BWC