Comments
-
@ISDPCMAN, You can go through this datasheet and compare but, I would suggest involving SonicWall Sales team to get their input on it. They should be able to guide you to make the right decision. Thanks!
-
Hello @Paco, Welcome to the SonicWall community. Are you testing this with GVC or SSLVPN? Can you please make sure that you have enough licenses? Also, are you getting any error messages on the client or any logs on the firewall when you test with the second user? Thanks!
-
@ACETech, All managed L2 switches have VLAN capability. Only if it is an unmanaged switch, you might not be able to set up VLANs. Basically, the ports on which the AP and the firewall are connected should be made trunk and hence tagged for the VLAN ID you are using for Guest SSID and untagged for native VLAN 1. (That is…
-
Hello @Faye, Welcome to the SonicWall community. Although the CLI commands are not exactly the same, you can SSH to the box and use the commands from this doc below. The ? and tab features work as usual. Also, to save the current configuration you can either export the settings file to save it on your local device or…
-
@Audi911, You can create static routes from Policy | Rules and Policies | Routing Rules section as per the screenshot below. I hope that helps! Thanks!
-
@Audi911, I will work with the concerned team to get this KB updated with the screenshots for Gen 7 devices as well. The configuration steps remain the same and can be found under Network | System | Interface and Add Interface section. Thanks!
-
Yes, you are right. X1 is the default WAN interface, so VLANs should be added with X1 as the parent interface. Thanks!
-
Hello @Audi911, Welcome to the SonicWall community. I think you would need to create VLAN sub-interfaces as mentioned in this KB. Thanks!
-
@Charper, You are right. If you see all the VLAN networks as well in the address group, then we should be good. I would suggest sending some ping traffic across the VPN and monitoring using the packet monitor tool to see what could be the problem. Thanks!
-
Glad I could help. Have a good one!
-
Yes, I understand. In that case, you might need to add that cable to X6 which should already be set with DHCP or the right IP addressing scheme. Also, the static ARP should be added to the firewall so that the phones start considering the X0 interface's MAC address as 192.168.0.254. This should be removed while CL is…
-
@PDXPaul, The only problem with that setup is that the Default gateway on the phones will be still pointing to the incorrect address creating a problem. You can manually add a static ARP for 192.168.0.254 and bind to X0 when the CL internet goes down. This can logically pair a secondary IP to the physical interface X0. You…
-
Yes, for us to introduce the TZ 215, we would need access to the CL at least. We can use IP 192.168.0.254 on the TZ 215 X0 interface, but the connection to CL on X1 as well the connection to TZ 400 needs to be on a separate network. Thanks!
-
The suggestion that I provided will make the whole process automatic and you would need not make any physical or configuration changes if the CL internet connection goes down. I am sure there are other ways to achieve it but that will need real-time physical or configuration changes. Thank you!
-
@PDXPaul, You can do the following. 1) Connect the phones to the TZ 215 and use that as the default gateway. Set up WAN failover on TZ 215 with CL as the primary and have a separate connection to the existing TZ 400. 2) With that setup, you can have logical probing done for CL and if the internet is down, route the traffic…