What’s New in Fireware XTM v11.5.3

Changes in Fireware XTM v  Routing table changes  Feature key global expiration for some XTMv keys  IP address validity checks and warnings WatchGuard Training2

Routing Table Changes in v  The Routes section of the FSM Status Report now displays the routes in a different format.  This improves consistency in the way IPv4 and IPv6 routes are displayed.  The Routes section can contain these route tables: Route Table: main — shows all IPv4 and IPv6 static routes Route Table: default — shows information about the default route Route Table: ethx.out — shows active routes for an external interface, ethx, where x is the interface number. Route Table: zebra— shows dynamic routes received from a peer  If a route table has no entries, it does not appear. For example, the zebra table does not appear if dynamic routing is disabled.  The zebra route table shows only the first 20 dynamic routes. To see a complete list of the dynamic routes, see the OSPF, RIP, or BGP section of the Status Report. WatchGuard Training3

Routing Table Changes in v WatchGuard Training Routes in v Routes in v Routes Destination Gateway Flags Metric Ref Use Iface /30 * U eth /24 * U eth / UG eth /24 * U eth /24 * U lo / UG eth0 default UG eth0 default UG eth0 Special routing tables eth0.out: /24 via dev eth0 metric /24 dev eth0 scope link metric /24 via dev eth0 metric 20 default via dev eth0 metric 1 zebra: /24 via dev eth0 metric 20 Route Table: main /30 dev eth2 proto kernel scope link /24 dev eth1 proto kernel scope link /24 via dev eth0 metric /24 dev eth0 proto kernel scope link /24 dev lo scope link default via dev eth0 ::1/128 dev lo proto kernel metric 256 Route Table: default default via dev eth0 metric 50 Route Table: eth0.out /24 via dev eth0 metric /24 dev eth0 scope link metric 1 default via dev eth0 metric 1 Route Table: zebra /24 via dev eth0 proto zebra metric 20 Comparison of FSM Status Report Routes section in v and v11.5.3

Routing Table Changes in v  A route bound to an XTM device interface appears in this format: dev proto kernel scope link Example: /24 dev eth0 proto kernel scope link  A static route that you add appears in this format: via dev metric Example: /24 via dev eth1 metric 1  A dynamic route appears in the zebra route table in this format: via dev proto zebra metric Example: /24 via dev eth0 proto zebra metric 20  Information that can appear for each route includes: — the destination IP address for the route dev — indicates which device (usually an interface number) the route applies to; for example eth0 for interface 0, or lo for loopback. proto kernel —route was created by the Linux kernel proto zebra — route is a dynamic route learned via a dynamic routing protocol scope link — route is bound to an XTM device interface metric — the routing metric, or cost for the route 5WatchGuard Training

IP Address Validity Checks  Error when you try to configure a primary or backup cluster IP address that overlaps the address pool used in Mobile VPN with SSL, Mobile VPN with IPSec, or Mobile VPN with PPTP. You cannot save a change that would cause this type of IP address overlap. The IP address validation and error occurs:  When you create or save changes to a FireCluster configuration  When you create or save changes to the Mobile VPN with SSL, Mobile VPN with IPSec, or Mobile VPN with PPTP configuration  Warning when primary or backup IP addresses for Mobile VPN for SSL or Mobile VPN for IPSec do not match an external IP address. The warning allows the user to continue (save the change) or cancel. The IP address validation and warning occurs:  When you save the Mobile VPN with IPSec configuration  When you save to the Mobile VPN with SSL configuration  When you save changes to the network configuration 6WatchGuard Training

THANK YOU!