Configuring a Third-Party Gateway using a Watchguard with a SonicWall SSL-VPN appliance

Description

Configuring a Third-Party Gateway using a Watchguard with a SonicWall SSL-VPN appliance

Resolution

WatchGuard Configuration for SonicWall SSL-VPN Appliance Deployment

Product: WatchGuard Firebox X Edge

This guide assumes that your WatchGuard Firebox X Gateway is configured with an IP of 192.168.100.1 and your SonicWall SSL-VPN is configured with an IP of 192.168.100.2.

The steps below are similar for WatchGuard SOHO6 series firewall.

Before you get started, take note of which port the WatchGuard is using for management. If the WatchGuard is not being managed on HTTPS (443), perform the following steps. If the WatchGuard is being managed on HTTPS (443) you’ll need to first review the notes within this guide.

  1. Step 1:- Open browser and enter the IP address of the WatchGuard Firebox X Edge appliance (i.e. 192.168.100.1). Once successful, you’ll be brought to the “System Status” page.
  2. Step 2:- If the WatchGuard’s management interface is already configured to accept HTTPS on port 443 you will need to change the port in order to be able to manage both the SonicWall SSL-VPN and WatchGuard appliances.
  3. Step 3:- Navigate to Administration > System Security.
  4. Step 4:- Uncheck Use non-secure HTTP instead of secure HTTPS for administrative Web site.
  5. Step 5:- Change the HTTP Server Port to 444 and click the Submit button.

    The WatchGuard will now be managed from the WAN on port 444. It should be accessed as follows: https://<watchguard wan ip>:444
  6. Step 6:- In the left-hand navigation menu, Navigate to Firewall > Incoming.
  7. Step 7:- For the HTTPS Service, set Filter to Allow and enter the WAN IP of the SonicWall SSL-VPN appliance (192.168.100.2) in the Service Host field.
  8. Step 8:- Click the Submit button at the bottom of the page.

Your Watchguard Firebox X Edge is now ready for operations with the SonicWall SSL-VPN appliance.

Excerpted from SSL-VPN 2.1 Administrator’s Guide

Related Articles

  • SMA100 End of Support No-Charge Replacement FAQ
    Read More
  • SMA1000: Post upgrade to 12.5.0 on AWS and Azure, we show the error Could not retrieve the DNS settings once we log in to AMC/CMS console
    Read More
  • Firmware version required to upgrade to version 12.5.0.
    Read More
not finding your answers?