<?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 Re: Spoofed IP address zone protection of vwire in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/spoofed-ip-address-zone-protection-of-vwire/m-p/50950#M37495</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Would it?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cant you through zones define which networks are expected on which end of the vwire?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Perhaps it needs a feature request similar to how vwire filters 802.1Q tagged vlans.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 01 Aug 2013 19:43:31 GMT</pubDate>
    <dc:creator>mikand</dc:creator>
    <dc:date>2013-08-01T19:43:31Z</dc:date>
    <item>
      <title>Spoofed IP address zone protection of vwire</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/spoofed-ip-address-zone-protection-of-vwire/m-p/50944#M37489</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have created a zone protection profile with protection against "Spoofed IP address".&lt;/P&gt;&lt;P&gt;We have put this protection profile on a vwire interface.&lt;/P&gt;&lt;P&gt;Question:&lt;/P&gt;&lt;P&gt;What will happen since a vwire interface has no IPs?&lt;/P&gt;&lt;P&gt;Will this "feature" be ignored, or what will happen / how can we configure this to apply the protection?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;KR&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Aug 2013 13:17:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/spoofed-ip-address-zone-protection-of-vwire/m-p/50944#M37489</guid>
      <dc:creator>mr.linus</dc:creator>
      <dc:date>2013-08-01T13:17:06Z</dc:date>
    </item>
    <item>
      <title>Re: Spoofed IP address zone protection of vwire</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/spoofed-ip-address-zone-protection-of-vwire/m-p/50945#M37490</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Linus,&lt;/P&gt;&lt;P&gt;As the vwire interfaces dont have an IP address, they wouldnt be subjected to IP spoofed attacks. But if you want to protect the servers behind the vwire interfaces, you can deploy a DoS Protection policy with a DoS protection profile, which includes protection for the IP spoof attacks as well.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Karthik&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Aug 2013 13:29:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/spoofed-ip-address-zone-protection-of-vwire/m-p/50945#M37490</guid>
      <dc:creator>kprakash</dc:creator>
      <dc:date>2013-08-01T13:29:08Z</dc:date>
    </item>
    <item>
      <title>Re: Spoofed IP address zone protection of vwire</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/spoofed-ip-address-zone-protection-of-vwire/m-p/50946#M37491</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Linus,&lt;/P&gt;&lt;P&gt;I just verified that the DoS Protection profile doesnt support checking for Spoofed IPs. The firewall can detect an IP address as being spoofed, if it sees the packet on a different interface than the one for which it has learnt the route for. As there is no routing information per se on the vwire interfaces, the PANFW, ignores the route checks for the source and the destination IP addresses, and hence ignores the IP spoof check for these packets.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR,&lt;/P&gt;&lt;P&gt;Karthik RP&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Aug 2013 13:56:57 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/spoofed-ip-address-zone-protection-of-vwire/m-p/50946#M37491</guid>
      <dc:creator>kprakash</dc:creator>
      <dc:date>2013-08-01T13:56:57Z</dc:date>
    </item>
    <item>
      <title>Re: Spoofed IP address zone protection of vwire</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/spoofed-ip-address-zone-protection-of-vwire/m-p/50947#M37492</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;seems logical, but is there a way we can add IP information to the vwires so we can use this feature?&lt;/P&gt;&lt;P&gt;I know that when we create sub-vwire-interfaces we can use classifiers, would this be an option?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Aug 2013 14:20:23 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/spoofed-ip-address-zone-protection-of-vwire/m-p/50947#M37492</guid>
      <dc:creator>mr.linus</dc:creator>
      <dc:date>2013-08-01T14:20:23Z</dc:date>
    </item>
    <item>
      <title>Re: Spoofed IP address zone protection of vwire</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/spoofed-ip-address-zone-protection-of-vwire/m-p/50948#M37493</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No Mr.linus,&lt;/P&gt;&lt;P&gt;that would break the concept of using a vwire. but I would recommend converting the vwire interfaces to layer 3 interfaces, unless there is a company norm for you to use vwire interfaces. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Karthik RP&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Aug 2013 14:34:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/spoofed-ip-address-zone-protection-of-vwire/m-p/50948#M37493</guid>
      <dc:creator>kprakash</dc:creator>
      <dc:date>2013-08-01T14:34:58Z</dc:date>
    </item>
    <item>
      <title>Re: Spoofed IP address zone protection of vwire</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/spoofed-ip-address-zone-protection-of-vwire/m-p/50949#M37494</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Alright, thanks for the info.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Aug 2013 14:43:34 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/spoofed-ip-address-zone-protection-of-vwire/m-p/50949#M37494</guid>
      <dc:creator>mr.linus</dc:creator>
      <dc:date>2013-08-01T14:43:34Z</dc:date>
    </item>
    <item>
      <title>Re: Spoofed IP address zone protection of vwire</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/spoofed-ip-address-zone-protection-of-vwire/m-p/50950#M37495</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Would it?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cant you through zones define which networks are expected on which end of the vwire?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Perhaps it needs a feature request similar to how vwire filters 802.1Q tagged vlans.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Aug 2013 19:43:31 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/spoofed-ip-address-zone-protection-of-vwire/m-p/50950#M37495</guid>
      <dc:creator>mikand</dc:creator>
      <dc:date>2013-08-01T19:43:31Z</dc:date>
    </item>
  </channel>
</rss>

