<?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: Palo Alto connection Virtual wire drop User VPN anyconnect in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-connection-virtual-wire-drop-user-vpn-anyconnect/m-p/356765#M87686</link>
    <description>&lt;P&gt;if you set your policy as default, you will be silently (no log) dropping connections that are not being allowed&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;you can resolve that by setting a drop rule at the end of your policy that logs all denied vonnections, or override and edit the default rule to log-at-end&lt;/P&gt;</description>
    <pubDate>Fri, 16 Oct 2020 14:37:48 GMT</pubDate>
    <dc:creator>reaper</dc:creator>
    <dc:date>2020-10-16T14:37:48Z</dc:date>
    <item>
      <title>Palo Alto connection Virtual wire drop User VPN anyconnect</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-connection-virtual-wire-drop-user-vpn-anyconnect/m-p/355623#M87563</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;I am facing an issue where I setup my PA-850 as a transparent mode (virtual wire) and set the policy as default to allow all the traffic. Connection of my PA-850 is in between router and core switch. I can see all the traffic is passthrough the PA-850 without any issue however, some of the user from other branch connect through Anyconnect VPN of their branch ASA firewall unable to reach to my internal server due to my PA-850. I try to filter in monitor tab and check the source or destination ip address of the branch ASA firewall and nothing is showing. Temporary solution is to set my router directly connect to the core switch (bypass PA-850) and then user that connect through Anyconnect VPN able to reach my internal server. any idea what is the reason for this ?&lt;/P&gt;</description>
      <pubDate>Sun, 11 Oct 2020 14:49:07 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-connection-virtual-wire-drop-user-vpn-anyconnect/m-p/355623#M87563</guid>
      <dc:creator>sayyidi</dc:creator>
      <dc:date>2020-10-11T14:49:07Z</dc:date>
    </item>
    <item>
      <title>Re: Palo Alto connection Virtual wire drop User VPN anyconnect</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-connection-virtual-wire-drop-user-vpn-anyconnect/m-p/356765#M87686</link>
      <description>&lt;P&gt;if you set your policy as default, you will be silently (no log) dropping connections that are not being allowed&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;you can resolve that by setting a drop rule at the end of your policy that logs all denied vonnections, or override and edit the default rule to log-at-end&lt;/P&gt;</description>
      <pubDate>Fri, 16 Oct 2020 14:37:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-connection-virtual-wire-drop-user-vpn-anyconnect/m-p/356765#M87686</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2020-10-16T14:37:48Z</dc:date>
    </item>
  </channel>
</rss>

