Category: VPN

Connect OpenVPN to Watchguard
article #769, updated 808 days ago

There are lots of GUIs, but the command-line method is extremely simple when you need it quick and ad-hoc. This works with Fireware version 11.8 and after. First web-browse to here:

https://1.2.3.4/sslvpn.html

where 1.2.3.4 is the IP of your Watchguard. Then login and pull in client.ovpn from the lowermost link. Then just run:

openvpn --config client.ovpn

login in, and you’re in. If the Watchguard has multiple SSL VPN configs and the default is the wrong IP, just change the IP in the .ovpn file and it will work fine.

Categories:   VPN   

==============

OpenVPN for MacOS X
article #598, updated 1276 days ago

This one is very good:

https://code.google.com/p/tunnelblick/

Categories:   VPN   

==============

Watchguard SSL VPN to iPad
article #552, updated 1378 days ago

One recommendation, is to use OpenVPN:

http://customers.watchguard.com/articles/Article/Create-an-SSL-VPN-Profile-for-the-Open-VPN-Client-for-Android-iOS/?q=ipad+vpn&l=en_US&fs=Search&pn=1

Categories:   VPN   

==============

Watchguard IPSec Mobile User VPN Configuration for Core/XTM
article #292, updated 2022 days ago

This is specifically for Watchguard IPSec mobile user VPN, but is probably applicable in other IPSec situations also.

When setting up IPSec VPN, at least in some paradigms, the server side is set up without DNS/WINS settings, and then in the client profile, after the import, one does this in “IPsec Address Assignment”:

Local IP address (takes the IP from the local LAN)
DNS Server:  <destination LAN DNS or general>
WINS Server:  <destination LAN WINS or none>
Domain Name:  <destination LAN-local domain>

Some notes on the destination side.

  1. In the Watchguard IPSec VPN configuration, the “virtual IP range” under resources, has to be a range (a) included in the DHCP distribution but (b) excluded on the DHCP server (if any) at the destination; it has to be part of the destination subnet. It is reportedly also possible to set the router up to use a new subnet for this, but this requires adding a rule in the router and is more complex.
  2. If there is a Windows domain controller at the destination, recommended is to set the Watchguard IPSec VPN for Active Directory authentication. In such a case, the “Group Name” has to be a Security Group in the AD of exactly the same name, case significant, as exists on the server, and any user has to be a member of that group. If a user attempts to connect who is not a member of that group, connection will occur, but RX will remain at zero bytes.

Categories:   VPN   Router/Firewall Configuration