Comments
-
Hello @xdmfanboy, On the latest general release 6.5.4.7, the HTTPS content filtering is moved to a profile-based section whereas DPI SSL is a global option. When using DPI SSL, the SonicWall performs SSL proxy and can see the HTTP GET that shows the entire URI being accessed and can also show the block page as the SSL…
-
Hello @jkjung, Usually, warm boots can occur due to multiple reasons like RAM exhaustion, deadlocks, etc but they are usually due to software/firmware reasons and not hardware. I see that you are on a very old firmware version, 6.5.0.2. I would request to upgrade to 6.5.1.3 and then to 6.5.4.7 and then monitor. In these…
-
Hello @tejasshenai, If all the VLANs are also created in zone LAN, then no separate access rules are needed. Thanks!
-
@tejasshenai, If the subnet mask is /21 on the interface then 180.4.22.xx/21 also belongs to the same network. I agree with @BWC, the DHCP IP assignment is not sequential and any free IP belonging to the network can be assigned. Thanks!
-
Hello @DisaRicks, How is the VPN configured, is it site-to-site VPN or route-based VPN? If there is a site-to-site VPN, SonicWall automatically sends the traffic through the VPN. But if you add a static route, it does not pass through the VPN engine and goes unencrypted using that route. Also, I am not sure why the NAT is…
-
@tejasshenai, Are you testing with ping alone or are some other applications failing too? You can check for the windows firewall on the end machines. On the firewall, make sure that the IPS low priority attack is set to detect and not prevent as ping is considered as low priority IPS attack. You can perform packet capture…
-
Hello @tejasshenai, If the DHCP is enabled for a VLAN sub-interface, the SonicWall needs to identify that the request is being made by a computer belonging to that VLAN. This is done using the VLAN tag. So, please make sure that on the switch the port connecting the computer to the switch is an access port belonging to the…
-
@tejasshenai, The LAN to WAN access rule is set to allow by default. You can check to make sure that it is present and not altered. But it is present by default on the firewall. Thanks!
-
No changes are required on the firewall for this. The switch port that connects to the X0 port of the firewall needs to be a trunk port so that all VLAN traffic can be carried to the firewall. Thanks!
-
@tejasshenai, VLAN 1 is a native VLAN and is not tagged. The X0 itself belongs to VLAN 1 and I think the switch itself should also use VLAN 1 as the native VLAN. Please use some higher VLAN IDs (usually above 50) for the sub-interfaces so that it does not collide with the internal VLANs used by the firewall. Thanks!
-
Sure, keep us posted!
-
Hello @tejasshenai, Since the sub-interfaces are created on the firewall, the inter-VLAN routing will automatically be handled by SonicWall. The communication between these VLANs depends on the access rules and what zones these sub-interfaces are added with. If they are created on zone LAN, the LAN to LAN access rule…
-
Hello @tejasshenai, You would need to check what zones X0 and X10 are and make sure the access rules are configured between those two zones to allow communication. Kindly take a look at the KB below for more info. Thanks!
-
Hello @Enzino78, I can see a provisioning profile for SonicPointN on Gen 7 devices, so it should be able to provision older Ni access points. Thanks!
-
Hello @mrshahin, We need a lot more detail to understand this issue. Are both these devices using the same subnet masks? How are they connected to each other? Are they on the same switch? Thanks!