<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Firewall interfaces in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firewall-interfaces/m-p/1002522#M940552</link>
    <description>&lt;P&gt;Say you have three interfaces on a firewall such as a PIX. Two of the interfaces are WAN links, (broadband internet access, different ISP's) and one is your LAN.  The LAN interface address is what your LAN uses as its gateway.  What determines which WAN interface internet traffic initiated form the inside goes to, assuming you permit the web traffic for both?&lt;/P&gt;&lt;P&gt;Would you have to choose which one by setting up NAT, Routes, etc, or could you enable LAN users to access both, thereby having a failover option in case one WAN link goes down?&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 12:20:53 GMT</pubDate>
    <dc:creator>attrib7575</dc:creator>
    <dc:date>2019-03-11T12:20:53Z</dc:date>
    <item>
      <title>Firewall interfaces</title>
      <link>https://community.cisco.com/t5/network-security/firewall-interfaces/m-p/1002522#M940552</link>
      <description>&lt;P&gt;Say you have three interfaces on a firewall such as a PIX. Two of the interfaces are WAN links, (broadband internet access, different ISP's) and one is your LAN.  The LAN interface address is what your LAN uses as its gateway.  What determines which WAN interface internet traffic initiated form the inside goes to, assuming you permit the web traffic for both?&lt;/P&gt;&lt;P&gt;Would you have to choose which one by setting up NAT, Routes, etc, or could you enable LAN users to access both, thereby having a failover option in case one WAN link goes down?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 12:20:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-interfaces/m-p/1002522#M940552</guid>
      <dc:creator>attrib7575</dc:creator>
      <dc:date>2019-03-11T12:20:53Z</dc:date>
    </item>
    <item>
      <title>Re: Firewall interfaces</title>
      <link>https://community.cisco.com/t5/network-security/firewall-interfaces/m-p/1002523#M940553</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You would setup one as primary ISP link and the second one as a backup. You cannot load balance traffic out both interfaces. Point the default route out via the primary link and another default route with a higher admin distance via the second link. Set NAT rules and may want to configure IP SLA to track the availability of the next hop via the primary link.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sundar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Mar 2008 19:40:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-interfaces/m-p/1002523#M940553</guid>
      <dc:creator>sundar.palaniappan</dc:creator>
      <dc:date>2008-03-21T19:40:00Z</dc:date>
    </item>
    <item>
      <title>Re: Firewall interfaces</title>
      <link>https://community.cisco.com/t5/network-security/firewall-interfaces/m-p/1002524#M940554</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Very good thanks!! I'll start figuring that out.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Mar 2008 14:01:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-interfaces/m-p/1002524#M940554</guid>
      <dc:creator>attrib7575</dc:creator>
      <dc:date>2008-03-24T14:01:38Z</dc:date>
    </item>
    <item>
      <title>Re: Firewall interfaces</title>
      <link>https://community.cisco.com/t5/network-security/firewall-interfaces/m-p/1002525#M940555</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00806e880b.shtml" target="_blank"&gt;http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00806e880b.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is it here.  Unfortunately I dont think think my 6.2 ver PIX supports it. UGH.  &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Mar 2008 15:26:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-interfaces/m-p/1002525#M940555</guid>
      <dc:creator>attrib7575</dc:creator>
      <dc:date>2008-03-24T15:26:40Z</dc:date>
    </item>
  </channel>
</rss>

