Comments
-
@gparker919 , yes it is supported on gen7 models.
-
Hi @BWC , Unfortunately we had a tertiary issue surface with the fix (not a new problem but a branch of the old one). We will resolve that before releasing 10.0.24.
-
Hi @BWC. Sorry for the inconvenience. The firmware was pulled due to an SPF lookup problem that may cause mail flow disruption. However, 10.0.23 is in the final stages of being QA'd and once released, will address the issue.
-
@Enzino78 , you can still purchase the 270 and deploy it on a larger instance size with 3 interfaces for HA. It will not use the full RAM/CPU if it is above the 270 maximums but it will still function and you can have HA.
-
That is one way to do it, you can also do a dynamic botnet list or make manual botnet entries.
-
@Jour , did you use the migration tool? https://migratetool.global.sonicwall.com/
-
Upstream NAT should not effect your security posture unless you have a very niche circumstance.
-
@morkos, What firmware version is your firewall?
-
@Alberto, can you provide screenshots of what you mean by surfing to the internet requiring 2FA?
-
What browser are you actually using?
-
OK, then you have narrowed it down enough to be the ISP or Upstream device at the WeWork location.
-
Technically, the GEN6 ISP/Modem might be at fault but you can rule that out by testing a tunnel to another location to see if it presents the same behavior.
-
Sounds like either the WeWork upstream firewall or ISP is touching the ESP traffic. Hopefully they don't have ESP ALG enabled (ugh) because it sounds like when you are manually renegotiating the tunnel and the SPI's change, this issue starts.
-
900 is just the redundancy interval. Can you confirm that the event actually triggered in the local UI logs?
-
Have you used NSM Analytics?