<?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 ipsec UDP reverse path check in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ipsec-udp-reverse-path-check/m-p/1986209#M440770</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Robert&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 17 Jun 2012 06:52:11 GMT</pubDate>
    <dc:creator>robert</dc:creator>
    <dc:date>2012-06-17T06:52:11Z</dc:date>
    <item>
      <title>ipsec UDP reverse path check</title>
      <link>https://community.cisco.com/t5/network-security/ipsec-udp-reverse-path-check/m-p/1986207#M440768</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASA running 8.2(5).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When vpn clients connect with a ipsec vpn client configured as a zero tunnel route (0.0.0.0/0) the ASA logs the below:&lt;/P&gt;&lt;P&gt;Deny UDP reverse path check from 192.168.200.47 to 192.168.11.200 on interface HOSTING&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;192.168.200.0/24 is the subnet where the ipsec clients gets a ip address from when connecting.&lt;/P&gt;&lt;P&gt;192.168.11.200 in this case the the clients own local subnet. Is it expected that the ASA box will log these messages from clients local subnet when they are connected with ipsec vpn and it is a zero tunnel configuration?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Interfaces and routes:&lt;/P&gt;&lt;P&gt;Current available interface(s):&lt;/P&gt;&lt;P&gt;&amp;nbsp; DATA-BACKUP&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Name of interface Redundant1.10&lt;/P&gt;&lt;P&gt;&amp;nbsp; DMZ&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Name of interface Redundant1.900&lt;/P&gt;&lt;P&gt;&amp;nbsp; GUEST&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Name of interface Redundant1.990&lt;/P&gt;&lt;P&gt;&amp;nbsp; HOSTING&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Name of interface Redundant1.100&lt;/P&gt;&lt;P&gt;&amp;nbsp; Infrastruktur&amp;nbsp;&amp;nbsp; Name of interface Redundant1.20&lt;/P&gt;&lt;P&gt;&amp;nbsp; Intern&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Name of interface Management0/0&lt;/P&gt;&lt;P&gt;&amp;nbsp; OUTSIDE-BACKUP&amp;nbsp; Name of interface Redundant1.998&lt;/P&gt;&lt;P&gt;&amp;nbsp; PHONE&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Name of interface Redundant1.200&lt;/P&gt;&lt;P&gt;&amp;nbsp; SPECTRA-LAN&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Name of interface Redundant1.50&lt;/P&gt;&lt;P&gt;&amp;nbsp; outside&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Name of interface Ethernet0/3&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gateway of last resort is 1.2.3.4 to network 0.0.0.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp; 172.31.0.0 255.255.255.0 is directly connected, DMZ&lt;/P&gt;&lt;P&gt;S&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.200.46 255.255.255.255 [1/0] via 1.2.3.4, outside&lt;/P&gt;&lt;P&gt;S&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.200.47 255.255.255.255 [1/0] via 1.2.3.4, outside&lt;/P&gt;&lt;P&gt;S&amp;nbsp;&amp;nbsp;&amp;nbsp; VPN-hosting 255.255.255.0 [1/0] via 192.168.200.1, outside&lt;/P&gt;&lt;P&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp; 93.167.197.80 255.255.255.240 is directly connected, outside&lt;/P&gt;&lt;P&gt;S&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.100.110.0 255.255.255.0 [1/0] via 10.100.110.1, outside&lt;/P&gt;&lt;P&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.10.10.0 255.255.255.0 is directly connected, GUEST&lt;/P&gt;&lt;P&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.100.100.0 255.255.255.0 is directly connected, Intern&lt;/P&gt;&lt;P&gt;S&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.100.101.0 255.255.255.0 [5/0] via 10.100.100.252, Intern&lt;/P&gt;&lt;P&gt;S&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.100.0.0 255.255.0.0 [10/0] via 10.100.100.252, Intern&lt;/P&gt;&lt;P&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.200.100.0 255.255.252.0 is directly connected, PHONE&lt;/P&gt;&lt;P&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.199.1.0 255.255.255.0 is directly connected, Infrastruktur&lt;/P&gt;&lt;P&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.199.0.0 255.255.255.0 is directly connected, DATA-BACKUP&lt;/P&gt;&lt;P&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.254.0 255.255.255.0 is directly connected, HOSTING&lt;/P&gt;&lt;P&gt;S*&amp;nbsp;&amp;nbsp; 0.0.0.0 0.0.0.0 [1/0] via 1.2.3.4, outside&lt;/P&gt;&lt;P&gt;S&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.0.0 255.255.0.0 [5/0] via 192.168.254.1, HOSTING&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Robert&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 23:20:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ipsec-udp-reverse-path-check/m-p/1986207#M440768</guid>
      <dc:creator>robert</dc:creator>
      <dc:date>2019-03-11T23:20:12Z</dc:date>
    </item>
    <item>
      <title>ipsec UDP reverse path check</title>
      <link>https://community.cisco.com/t5/network-security/ipsec-udp-reverse-path-check/m-p/1986208#M440769</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, because you don't configure split tunnel, all traffic including local vpn client subnet will also be routed through the VPN tunnel. If your vpn client needs to access their own local LAN while connected to the VPN tunnel, then you would need to configure split tunnel.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 17 Jun 2012 03:52:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ipsec-udp-reverse-path-check/m-p/1986208#M440769</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2012-06-17T03:52:03Z</dc:date>
    </item>
    <item>
      <title>ipsec UDP reverse path check</title>
      <link>https://community.cisco.com/t5/network-security/ipsec-udp-reverse-path-check/m-p/1986209#M440770</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Robert&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 17 Jun 2012 06:52:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ipsec-udp-reverse-path-check/m-p/1986209#M440770</guid>
      <dc:creator>robert</dc:creator>
      <dc:date>2012-06-17T06:52:11Z</dc:date>
    </item>
  </channel>
</rss>

