1. XTM Networking Tips and Tricks Carlo Alvarez Technical Trainer - APAC

2. 2WatchGuard Training Agenda  Public IP Address Subnet Behind XTM  Dynamic Routing in FireCluster  Enhanced Network Failover (ENF) with Remote WAN Failover  Mixed Clientless SSO

3. PUBLIC SUBNET BEHIND XTM

4. 4WatchGuard Training Top 5 Reasons Why End Users Have Public IPs in their Network 1.They care about redundancy in terms of path going into their network 2.They care about the IP Address their hosts are going to use when they communicate on the internet 3.They demanded for Public IPs but they are not going to use it 4.They were just assigned by their ISP and they don’t care about it 5.They just make up addresses on their own

5. 5WatchGuard Training Public Subnet Behind XTM  Generally, the concern is the redundancy and the inbound path going to the Public Subnet  Works with either static or dynamic routing  Can be as simple as Single-WAN and can go as complex as Multi-WAN with Dynamic Routing

6. 6WatchGuard Training Simple Scenario : Public Subnet behind XTM  Single External Interface  Static Routing is sufficient  Works with Subnets of variable sizes

7. 7WatchGuard Training Simple Scenario : Public Subnet behind XTM  Configuration Tips Static route must be configured on the router before the XTM device  In this example a route to 202.101.21.0/24 with the next hop to 208.82.1.2 (XTM’s External Interface) Assign an IP Address from the same subnet to the XTM’s Optional Interface The subnet must not be included in the Dynamic NAT configuration Uncheck the NAT options on the Policies involving the Optional Network or any host of the Public Subnet

8. 8WatchGuard Training Simple Scenario : Public Subnet behind XTM  Network Configuration

9. 9WatchGuard Training Simple Scenario : Public Subnet behind XTM  Policy Example 1 - Outbound

10. 10WatchGuard Training Simple Scenario : Public Subnet behind XTM  Policy Example 2 - Inbound  In this example 202.101.21.25 is the Mail Server  Destination Address is the Mail Server IP Address

11. 11WatchGuard Training Complex Scenario 1 : Public Subnet behind XTM  With Multi-WAN  Static Routing only  Works similar to the Single- WAN but with failover function using a different IP Address  Works even with subnet smaller than /24  Inbound path to the real Public IP is still on a single path

12. 12WatchGuard Training Complex Scenario 1 : Public Subnet behind XTM  Configuration Tips Static route must be configured on the router before the XTM device going to XTM’s External-1 similar to the Simple Scenario example Assign an IP Address from the same subnet to the XTM’s Optional Interface Add a Dynamic Nat of the Public Subnet Translating to the IP Address of External-2 for outbound purposes Inbound Policies will require two entries going to the same host

13. 13WatchGuard Training Complex Scenario 1 : Public Subnet behind XTM  Network Configuration

14. 14WatchGuard Training Complex Scenario 1 : Public Subnet behind XTM  DNAT Configuration  An entry is added for the Public IP subnet to translate to External-2 only

15. 15WatchGuard Training Complex Scenario 1 : Public Subnet behind XTM  Policy Example 1 - Outbound

16. 16WatchGuard Training Complex Scenario 1 : Public Subnet behind XTM  Policy Example 2 - Inbound  In this example 202.101.21.25 is the Mail Server  Destination Address has two entries The host as is (202.101.21.25) Static NAT translating the other External IP 122.22.21.2 to 202.101.21.25

17. 17WatchGuard Training Complex Scenario 1 : Public Subnet behind XTM  Configure the DNS Records for inbound traffic  Example NS Records for Email Systems company.com IN MX 5 mail1.company.com. company.com IN MX 10 mail2.company.com. mail1 IN A 202.101.21.25 mail2 IN A 122.22.21.2  Example NS Records for Web Service Www1.company.com. IN A 202.101.21.80 www2.company.com. IN A 122.22.21.2

18. 18WatchGuard Training Complex Scenario 2 : Public Subnet behind XTM  With Multi-WAN  Dynamic Routing support  Inbound path to the Public IP can be either of the WAN interfaces  Limited to subnets /24 or greater

19. 19WatchGuard Training Complex Scenario 2 : Public Subnet behind XTM  Configuration Tips Configure External Interfaces Assign an IP Address from the same subnet to the XTM’s Optional Interface Configure the Dynamic Routing with the Upstream Peers

20. 20WatchGuard Training Complex Scenario 2 : Public Subnet behind XTM  Network Configuration

21. 21WatchGuard Training Complex Scenario 2 : Public Subnet behind XTM  Dynamic Routing Configuration

22. 22WatchGuard Training Complex Scenario 2 : Public Subnet behind XTM  Policy Example 1 - Outbound

23. 23WatchGuard Training Complex Scenario 2 : Public Subnet behind XTM  Policy Example 2 - Inbound  In this example 202.101.21.25 is the Mail Server  Destination Address is the Mail Server IP Address

24. DYNAMIC ROUTING IN FIRECLUSTER

25. 25WatchGuard Training Dynamic Routing in FireCluster  Consider this…

26. Let’s try it out…

27. ENF with REMOTE WAN FAILOVER

28. 28WatchGuard Training Consider This Scenario  A site can access the other through the Point-to-Point Link (PTP)

29. BOVPN 29WatchGuard Training Consider This Scenario  A site can access the other through the Point-to-Point Link (PTP)  If the Point-to-Point link goes down the traffic routes through BOVPN ENF Enhanced Network Failover

30. 30WatchGuard Training Enhanced Network Failover  A site’s access to any resource on the internet goes through its WAN

31. 31WatchGuard Training Enhanced Network Failover  A site’s access to any resource on the internet goes through the WAN  If WAN breaks, it should be able to re-route through the PTP link

32. 32WatchGuard Training ENF with Remote WAN Failover  The idea is to be able to use the remote site’s WAN for failover  Remote WAN failover can be configured on either or both sites

33. 33WatchGuard Training ENF with Remote WAN Failover Configuration  Network Configuration

34. 34WatchGuard Training ENF with Remote WAN Failover Configuration  Dynamic NAT is only on the real WAN interface

35. 35WatchGuard Training ENF with Remote WAN Failover Configuration  Dynamic Routing (OSPF)

36. 36WatchGuard Training ENF with Remote WAN Failover Configuration  BOVPN Configuration

37. 37WatchGuard Training ENF with Remote WAN Failover Configuration  The Policies

38. 38WatchGuard Training ENF with Remote WAN Failover Tips  The link between two sites must be Point-to-Point: with HO site set as LAN/OPT, while BO site should be set as WAN.  Multi-Hop link is also possible provided the routers used in between can do source based routing to filter the direction of the default routes  On BO site, Dynamic NAT is configured on the real WAN interface only such that traffic from one site to the other is not translated to the interface IP.  On BO, the Multi-WAN should be set as Failover.  On HO site, you must allow the remote subnet in the Global DNAT settings, and in the outbound rules for WEB access.  Ping must be allowed from the opposite end of the Point-to-Point link otherwise the External interface will fail.  This can work with Static or Dynamic routes, with classic Site-to-Site VPN.

39. Let’s try it out…

40. MIXED CLIENTLESS SSO

41. 41WatchGuard Training Mixed Clientless SSO Scenario  Network is a combination of AD Joined-Hosts and Disjoined-Hosts  AD Joined-Host will do Clientless SSO  AD Disjoined Hosts such as Macs and Unix will be auto- redirected to authentication page when browsing

42. 42WatchGuard Training Helpful Hints:  Break the trusted subnet for easier policy configuration DHCP Address reservation for AD-Joined Hosts DHCP Pool for AD-Disjoined Hosts  Another option is to put the AD- Disjoined Hosts to a different subnet such as another Zone or a Wireless Guest network  WebBlocker plays a key role in this scenario since we will block the initial access of the Disjoined Hosts (IP Address Reservations) (IP Pool)

43. 43WatchGuard Training Mixed Clientless SSO Configuration  Configure ELM  ELM should be the top priority on the Clientless SSO Settings

44. 44WatchGuard Training Mixed Clientless SSO Configuration  Check the Trusted Interface configuration  Host Range should be easily segregated  In this example the lower half is for the reserved addresses of the AD-Joined Hosts  The upper half is for the Disjoined Hosts (DHCP Pool)

45. 45WatchGuard Training Mixed Clientless SSO Configuration  Add the Active Directory Domain

46. 46WatchGuard Training Mixed Clientless SSO Configuration  Enable the Single Sign-On  Add Exceptions to the SSO Clients List  Exceptions here is the host range corresponding to the IP Pool available for the Disjoined Host

47. 47WatchGuard Training Mixed Clientless SSO Configuration  Add the Policy for the AD-Joined Hosts and the Authenticated Hosts

48. 48WatchGuard Training Mixed Clientless SSO Configuration  Add the Policy for the Disjoined Hosts  The Source corresponds to the IP Pool of the Disjoined Hosts  Take note of the Proxy Action

49. 49WatchGuard Training Mixed Clientless SSO Configuration  Add and configure WebBlocker to Deny All Categories

50. 50WatchGuard Training Mixed Clientless SSO Configuration  Edit the Deny Message

51. 51WatchGuard Training Mixed Clientless SSO Configuration  Note that the Policies are in Manual Order Mode

52. Let’s try it out…

53. THANK YOU!