TKWITS Community Legend ✭✭✭✭✭
Reactions
Comments
-
Do your homework. 172.16.53.10-254 isn't even in your CIDR range. 'Preferred or better' are both subjective, it's up to you to design and maintain the network so its your preference. But using something outside your CIDR range is technically impossible.
-
You'd want to create address object for each IP, then create a group containing those address objects, then select the group rather than 'any' in the rules. Read up on objects.
-
Read up on subnets and CIDR. What subnet mask are you currently using?
-
"From this, it should be clear that the PM on 172.24.12.47 is transmitting packets from 192.168.10.244 over VLAN 10 and they are hitting the X0:V10 MAC address." The MAC address of VLAN interfaces is shared from the parent interface, so thats not an accurate statement. "Can I assume that it is using 172.10.0.1 as the…
-
FWIW Sonicwall Mobile Connect for Windows is no longer supported.
-
did you enable https management on the X3 interface?
-
Not yet, but thank you for bringing this up! Was this the latest version on NetExtender? Did you try a reinstall or anything?
-
If the request is hitting the X0 interface as the log says ("Alert - 192.168.10.244, 56880, X0 - 8.8.8.8, 853, X1 - dns.google - tcp - IP spoof dropped") than the ARP'd address should be done on that interface. I don't know how it would hit just X0 and not X0:V10 if its really connected to the guest SSID; unless of course…
-
I never look at status pages. Maybe I should...
-
"Are these packets (since they are coming from the guest SSID) being tagged with V10, even though they're on a different subnet." You should be able to answer this question yourself if you are using VLANs, but the answer is yes. The log entry should provide what interface and vlan the packet arrived on, or you can run a…
-
Are you using a dedicated interface for the HA link? Have you replaced the cable? .
-
Run a packet capture to see if the Sonicwall is dropping the connection.
-
Firefox Portable version 3.5 is your friend.
-
That's an old firmware, you should probably read release notes and update. What you are describing may have been fixed in a later release.
-
This makes no sense.