How do I set up the Firebox for multi- WAN in round-robin order?

How do I set up the Firebox for multi- WAN in round-robin order? How do I set up the Firebox for multi- WAN in round-robin order?

watchguard.com
from watchguard.com More from this publisher
12.07.2015 Views

How do I set up the Firebox for multi-WAN in round-robin order?Fireware/MultiWANThis document applies to:Appliance Firebox X Core / Firebox X Core e-Series / Firebox X Peak /Firebox X Peak e-SeriesAppliance Software versions Fireware 8.3 / Fireware Pro 8.3Management Software versions WatchGuard System Manager 8.3IntroductionThe multi-WAN functionality of Fireware is designed to give the Firebox® administrator more control and greater efficiencywith a very large or high-traffic network. You can use Fireware® appliance software to configure up to fourFirebox interfaces as external or wide area network (WAN) interfaces. You can control the flow of traffic through multipleWAN interfaces to share the load of outgoing traffic.Fireware gives you the option to configure multiple external interfaces. This allows you to connect the Firebox tomore than one Internet Service Provider (ISP). When you configure multiple external interfaces, you have threeoptions to control which interface that outgoing packets use:Multi-WAN in round robin orderThis document explains how you can share the load of outgoing traffic among external interfaces through“round robin”. It works like this:- The first host, with IP address x.x.x.x, sends an HTTP request to the Internet. The packets in this session aresent through the lowest number external interface.- The second host, with IP address y.y.y.y, sends an HTTP request to the Internet. The packets in this sessionare sent through the external interface with the second higher number.- The third host, with IP address z.z.z.z, sends an HTTP request to the Internet. The packets in this session aresent through the lowest number external interface (if there are only two external interfaces configured) orthe third higher number external interface.As each host initiates a connection, the Firebox cycles through external interfaces using the pattern explainedabove.Multi-WAN failoverAnother option is failover, which allows you to configure additional external interfaces as backup if the primaryextrnal interface is down. For more information seehttps://www.watchguard.com/support/Fireware_Howto/83/HowTo_SetupWANFailover.pdfMulti-WAN with the routing tableIf you select this option, the Firebox uses the routes set in its internal routing table to send packets throught thecorrect external interface. For more information seehttps://www.watchguard.com/support/Fireware_Howto/83/HowTo_MultiWANroutingtable.pdfIs there anything I need to know before I start?As soon as you configure a second external interface, multiple WAN support is automatically enabled with Multi-WAN in round robin order set as the default.Note that:1

<strong>How</strong> <strong>do</strong> I <strong>set</strong> <strong>up</strong> <strong>the</strong> <strong>Firebox</strong> <strong>for</strong> <strong>multi</strong>-<strong>WAN</strong> <strong>in</strong> <strong>round</strong>-rob<strong>in</strong> <strong>order</strong>?Fireware/Multi<strong>WAN</strong>This <strong>do</strong>cument applies to:Appliance <strong>Firebox</strong> X Core / <strong>Firebox</strong> X Core e-Series / <strong>Firebox</strong> X Peak /<strong>Firebox</strong> X Peak e-SeriesAppliance Software versions Fireware 8.3 / Fireware Pro 8.3Management Software versions WatchGuard System Manager 8.3IntroductionThe <strong>multi</strong>-<strong>WAN</strong> functionality of Fireware is designed to give <strong>the</strong> <strong>Firebox</strong>® adm<strong>in</strong>istrator more control and greater efficiencywith a very large or high-traffic network. You can use Fireware® appliance software to configure <strong>up</strong> to four<strong>Firebox</strong> <strong>in</strong>terfaces as external or wide area network (<strong>WAN</strong>) <strong>in</strong>terfaces. You can control <strong>the</strong> flow of traffic through <strong>multi</strong>ple<strong>WAN</strong> <strong>in</strong>terfaces to share <strong>the</strong> load of outgo<strong>in</strong>g traffic.Fireware gives you <strong>the</strong> option to configure <strong>multi</strong>ple external <strong>in</strong>terfaces. This allows you to connect <strong>the</strong> <strong>Firebox</strong> tomore than one Internet Service Provider (ISP). When you configure <strong>multi</strong>ple external <strong>in</strong>terfaces, you have threeoptions to control which <strong>in</strong>terface that outgo<strong>in</strong>g packets use:Multi-<strong>WAN</strong> <strong>in</strong> <strong>round</strong> rob<strong>in</strong> <strong>order</strong>This <strong>do</strong>cument expla<strong>in</strong>s how you can share <strong>the</strong> load of outgo<strong>in</strong>g traffic among external <strong>in</strong>terfaces through“<strong>round</strong> rob<strong>in</strong>”. It works like this:- The first host, with IP address x.x.x.x, sends an HTTP request to <strong>the</strong> Internet. The packets <strong>in</strong> this session aresent through <strong>the</strong> lowest number external <strong>in</strong>terface.- The second host, with IP address y.y.y.y, sends an HTTP request to <strong>the</strong> Internet. The packets <strong>in</strong> this sessionare sent through <strong>the</strong> external <strong>in</strong>terface with <strong>the</strong> second higher number.- The third host, with IP address z.z.z.z, sends an HTTP request to <strong>the</strong> Internet. The packets <strong>in</strong> this session aresent through <strong>the</strong> lowest number external <strong>in</strong>terface (if <strong>the</strong>re are only two external <strong>in</strong>terfaces configured) or<strong>the</strong> third higher number external <strong>in</strong>terface.As each host <strong>in</strong>itiates a connection, <strong>the</strong> <strong>Firebox</strong> cycles through external <strong>in</strong>terfaces us<strong>in</strong>g <strong>the</strong> pattern expla<strong>in</strong>edabove.Multi-<strong>WAN</strong> failoverAno<strong>the</strong>r option is failover, which allows you to configure additional external <strong>in</strong>terfaces as back<strong>up</strong> if <strong>the</strong> primaryextrnal <strong>in</strong>terface is <strong>do</strong>wn. For more <strong>in</strong><strong>for</strong>mation seehttps://www.watchguard.com/s<strong>up</strong>port/Fireware_<strong>How</strong>to/83/<strong>How</strong>To_Set<strong>up</strong><strong>WAN</strong>Failover.pdfMulti-<strong>WAN</strong> with <strong>the</strong> rout<strong>in</strong>g tableIf you select this option, <strong>the</strong> <strong>Firebox</strong> uses <strong>the</strong> routes <strong>set</strong> <strong>in</strong> its <strong>in</strong>ternal rout<strong>in</strong>g table to send packets throught <strong>the</strong>correct external <strong>in</strong>terface. For more <strong>in</strong><strong>for</strong>mation seehttps://www.watchguard.com/s<strong>up</strong>port/Fireware_<strong>How</strong>to/83/<strong>How</strong>To_Multi<strong>WAN</strong>rout<strong>in</strong>gtable.pdfIs <strong>the</strong>re anyth<strong>in</strong>g I need to know be<strong>for</strong>e I start?As soon as you configure a second external <strong>in</strong>terface, <strong>multi</strong>ple <strong>WAN</strong> s<strong>up</strong>port is automatically enabled with Multi-<strong>WAN</strong> <strong>in</strong> <strong>round</strong> rob<strong>in</strong> <strong>order</strong> <strong>set</strong> as <strong>the</strong> default.Note that:1


<strong>How</strong> <strong>do</strong> I <strong>set</strong> <strong>up</strong> <strong>the</strong> <strong>Firebox</strong> <strong>for</strong> <strong>multi</strong>-<strong>WAN</strong> <strong>in</strong> <strong>round</strong>-rob<strong>in</strong> <strong>order</strong>?• If you have a policy configured with an <strong>in</strong>dividual external <strong>in</strong>terface alias <strong>in</strong> its configuration, you must change<strong>the</strong> configuration to use <strong>the</strong> alias “Any-External”.• If you use <strong>the</strong> <strong>multi</strong>ple <strong>WAN</strong> feature, map your company’s Fully Qualified Doma<strong>in</strong> Name to <strong>the</strong> external <strong>in</strong>terfaceIP address of <strong>the</strong> lowest <strong>order</strong>. If you add a <strong>multi</strong>-<strong>WAN</strong> <strong>Firebox</strong> to your Management Server configuration, youmust add <strong>the</strong> <strong>Firebox</strong> us<strong>in</strong>g its lowest-<strong>order</strong>ed external <strong>in</strong>terface to identify it.• You cannot use 1-to-1 NAT <strong>in</strong> a <strong>multi</strong>ple <strong>WAN</strong> configuration. If you have a public SMTP server beh<strong>in</strong>d your<strong>Firebox</strong>, you must <strong>set</strong> <strong>up</strong> a static NAT rule to allow access to your public SMTP e-mail server. Then, you can <strong>set</strong> <strong>up</strong><strong>multi</strong>ple MX records, one <strong>for</strong> each external <strong>Firebox</strong> <strong>in</strong>terface.• If you have a <strong>multi</strong>ple <strong>WAN</strong> configuration, you cannot use <strong>the</strong> policy-based, dynamic NAT Set Source IP option.Use <strong>the</strong> Set Source IP option only when your <strong>Firebox</strong> uses a s<strong>in</strong>gle external <strong>in</strong>terface.• Multiple <strong>WAN</strong> s<strong>up</strong>port <strong>do</strong>es not apply to branch office or Mobile User VPN traffic. Branch office and Mobile UserVPN traffic always uses <strong>the</strong> first external <strong>in</strong>terface configured <strong>for</strong> <strong>the</strong> <strong>Firebox</strong>. RUVPN with PPTP operates correctly<strong>in</strong> a <strong>multi</strong>ple <strong>WAN</strong> configuration.• The <strong>multi</strong>ple <strong>WAN</strong> feature is not s<strong>up</strong>ported <strong>in</strong> drop-<strong>in</strong> mode.Configure <strong>the</strong> <strong>Firebox</strong> <strong>for</strong> Multi-<strong>WAN</strong> <strong>in</strong> Round-Rob<strong>in</strong> Order1 From Policy Manager, select Network > Configuration.The Network Configuration dialog box appears.2


<strong>How</strong> <strong>do</strong> I <strong>set</strong> <strong>up</strong> <strong>the</strong> <strong>Firebox</strong> <strong>for</strong> <strong>multi</strong>-<strong>WAN</strong> <strong>in</strong> <strong>round</strong>-rob<strong>in</strong> <strong>order</strong>?2 Select <strong>the</strong> <strong>in</strong>terface you want to configure as external and click Configure. Select External from <strong>the</strong> InterfaceType drop-<strong>do</strong>wn list to activate <strong>the</strong> dialog box. Type an <strong>in</strong>terface name and description.You must have a m<strong>in</strong>imum of two external network <strong>in</strong>terfaces configured be<strong>for</strong>e you can see and configure <strong>multi</strong>-<strong>WAN</strong> <strong>set</strong>t<strong>in</strong>gs.3 Type <strong>the</strong> IP address and default gateway <strong>for</strong> <strong>the</strong> <strong>in</strong>terface. Click OK.When you type an IP address, type all <strong>the</strong> numbers and <strong>the</strong> periods. Do not use <strong>the</strong> TAB or arrow key.After you configure a second external <strong>in</strong>terface, <strong>multi</strong>ple <strong>WAN</strong> configuration options appear <strong>in</strong> <strong>the</strong> Network Configuration dialogbox.3


<strong>How</strong> <strong>do</strong> I <strong>set</strong> <strong>up</strong> <strong>the</strong> <strong>Firebox</strong> <strong>for</strong> <strong>multi</strong>-<strong>WAN</strong> <strong>in</strong> <strong>round</strong>-rob<strong>in</strong> <strong>order</strong>?4 Make sure that Multi-<strong>WAN</strong> <strong>in</strong> <strong>round</strong> rob<strong>in</strong> <strong>order</strong> is selected. This will send traffic sessions through <strong>the</strong> external<strong>in</strong>terfaces <strong>in</strong> sequence.5 In <strong>the</strong> <strong>WAN</strong> P<strong>in</strong>g Address dialog box, <strong>do</strong>uble-click <strong>in</strong> <strong>the</strong> P<strong>in</strong>g Address column to add an IP address or <strong>do</strong>ma<strong>in</strong>name <strong>for</strong> each external <strong>in</strong>terface. We recommend that you use <strong>the</strong> IP address of a computer external to yourorganization.When an external <strong>in</strong>terface is active, <strong>the</strong> <strong>Firebox</strong> p<strong>in</strong>gs <strong>the</strong> IP address or <strong>do</strong>ma<strong>in</strong> name you <strong>set</strong> here each 20 seconds to see if <strong>the</strong><strong>in</strong>terface is operat<strong>in</strong>g correctly. If <strong>the</strong>re is no response after three p<strong>in</strong>gs, <strong>the</strong> <strong>Firebox</strong> starts to use <strong>the</strong> subsequent configured external<strong>in</strong>terface. It <strong>the</strong>n starts to p<strong>in</strong>g <strong>the</strong> <strong>WAN</strong> p<strong>in</strong>g address you <strong>set</strong> <strong>for</strong> that <strong>in</strong>terface to check <strong>for</strong> connectivity.6 Click OK. Save your changes to <strong>the</strong> <strong>Firebox</strong>.Frequently Asked Questions About This ProcedureI have a public SMTP server beh<strong>in</strong>d my <strong>Firebox</strong>. Because <strong>the</strong> <strong>multi</strong>-<strong>WAN</strong> feature <strong>do</strong>es not work with 1-to-1NAT, what <strong>do</strong> I <strong>do</strong>?Because you cannot use 1-to-1 NAT with <strong>the</strong> <strong>multi</strong>-<strong>WAN</strong> feature, you will have to <strong>set</strong> <strong>up</strong> a static NAT rule to allowaccess to your public SMTP e-mail server. Then, you must <strong>set</strong> <strong>up</strong> <strong>multi</strong>ple MX records, one <strong>for</strong> each external<strong>Firebox</strong> <strong>in</strong>terface.Can I use <strong>round</strong>-rob<strong>in</strong> <strong>for</strong> <strong>in</strong>com<strong>in</strong>g connections?Yes. If you use <strong>multi</strong>-<strong>WAN</strong> <strong>in</strong> <strong>round</strong>-rob<strong>in</strong> mode, it is possible to <strong>set</strong> <strong>up</strong> <strong>round</strong>-rob<strong>in</strong> DNS with your DNS provider to<strong>do</strong> load-balanc<strong>in</strong>g among more than one external <strong>in</strong>terface.Was this <strong>do</strong>cument helpful? Please send your feedback to faq@watchguard.com.SUPPORT:www.watchguard.com/s<strong>up</strong>portU.S. and Canada +877.232.3531All O<strong>the</strong>r Countries +1.206.613.04564COPYRIGHT © 2006 WatchGuard Technologies, Inc. All rights reserved.WatchGuard, <strong>the</strong> WatchGuard logo, <strong>Firebox</strong>, Core, and Fireware are registered trademarks or trademarks ofWatchGuard Technologies, Inc. <strong>in</strong> <strong>the</strong> United States and/or o<strong>the</strong>r countries.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!