TKWITS Community Legend ✭✭✭✭✭
Reactions
Comments
-
Are the subnets overlapping? Have you double checked the access rules?
-
Not sure why they took down the KB but here is a cached version of it, have you seen it? There should be no reason a /29 would be a problem as long as its in the IANA designated private subnets.
-
Is your ISP providing you a bridged connection (as in their device is not doing NAT or firewalling)? Provide more information please.
-
The whole point of OOBM interfaces are for them not to be on a routed network.
-
Does it work when not using tunnel all mode?
-
Have you searched the forums yet? https://community.sonicwall.com/technology-and-support/discussion/comment/9143
-
I had some weirdness like this with a 570 on R906 at the beginning of the year. After a factory default and upgrade to R1262 they seemed to have gone away, and now on the latest (5023?) without issue. The earlier firmwares on Gen7 were terrible and upgrading without factory default never helped.
-
Check your SSLVPN to VPN (and VPN to SSLVPN) access rules...
-
You did not specify that you wanted to forbid ANY IP address. I do not think you can accomplish that with CFS, maybe with AppControl / AppRules.
-
I repeat. You'd have to add the IP address to a URI list, then use that URI list as the 'Forbidden URI' list, with the forbidden action as 'block'.
-
I did not configure it. Did you look at the switchport that is connected to X2?
-
They don't. VLAN4 was created specifically for the APs, and the switchports they are plugged into are likely configured as 'trunk' ports with the native VLAN set to 4. Back when I was using Sonicpoints that's how I did it. Hope that helps.
-
Content filtering works off of categorizing DNS addresses. You'd have to add the IP address to a URI list, then use that URI list as the 'Forbidden URI' list, with the forbidden action as 'block'. Hope that helps.
-
Yes, no one does what you are describing with using multiple interfaces to get devices behind a firewall 'exposed' to the internet. Maybe during the earliest years people did that... Your issue was specific to a route policy, not the way the Sonicwall handles NAT... "Now the route policy is a little strange because it…
-
Does it produce the same error in the Web UI?