<?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: permit VPN client to access outside interface in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/permit-vpn-client-to-access-outside-interface/m-p/793524#M970072</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Not sure if you need the outside keyword on the end, but other than that it looks okay.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does this router have a route to the vpn client subnet?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 04 Sep 2007 18:22:45 GMT</pubDate>
    <dc:creator>acomiskey</dc:creator>
    <dc:date>2007-09-04T18:22:45Z</dc:date>
    <item>
      <title>permit VPN client to access outside interface</title>
      <link>https://community.cisco.com/t5/network-security/permit-vpn-client-to-access-outside-interface/m-p/793521#M970069</link>
      <description>&lt;P&gt;how do i permit my remote vpn client to access my router that is situated on the outside interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i have this setup:&lt;/P&gt;&lt;P&gt;lan--firewall--router--internet&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i was able to let the remote vpn client access resource on my DMZ. Now, i also need to allow it to access my router on one of its outside interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;below is a sample config:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;interface Ethernet0/0&lt;/P&gt;&lt;P&gt; nameif outside_bayantel&lt;/P&gt;&lt;P&gt; security-level 0&lt;/P&gt;&lt;P&gt; ip address 121.97.xx.xx 255.255.255.248 &lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface Ethernet0/1&lt;/P&gt;&lt;P&gt; nameif inside_lan_data&lt;/P&gt;&lt;P&gt; security-level 100&lt;/P&gt;&lt;P&gt; ip address 192.168.100.1 255.255.255.0 &lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface Ethernet0/2&lt;/P&gt;&lt;P&gt; nameif DMZ_to_Voice&lt;/P&gt;&lt;P&gt; security-level 50&lt;/P&gt;&lt;P&gt; ip address 192.168.200.1 255.255.255.0 &lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface Ethernet0/3&lt;/P&gt;&lt;P&gt; nameif outside_PLDT&lt;/P&gt;&lt;P&gt; security-level 0&lt;/P&gt;&lt;P&gt; ip address 192.168.50.2 255.255.255.0 &lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;access-list inside_lan_data_nat0_outbound extended permit ip 192.168.100.0 255.255.255.0 192.168.100.168 255.255.255.248 &lt;/P&gt;&lt;P&gt;access-list outside_PLDT_nat0_outbound extended permit ip 192.168.50.0 255.255.255.0 192.168.100.168 255.255.255.248 &lt;/P&gt;&lt;P&gt;access-list DMZ_to_Voice_nat0_outbound extended permit ip 192.168.200.0 255.255.255.0 192.168.100.168 255.255.255.248 &lt;/P&gt;&lt;P&gt;access-list ccbslan_splitTunnelAcl standard permit 192.168.100.0 255.255.255.0 &lt;/P&gt;&lt;P&gt;access-list ccbslan_splitTunnelAcl standard permit host 192.168.200.2 &lt;/P&gt;&lt;P&gt;access-list ccbslan_splitTunnelAcl standard permit host 192.168.50.1 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ip local pool ccbslan_pool 192.168.100.170-192.168.100.175&lt;/P&gt;&lt;P&gt;global (outside_bayantel) 101 interface&lt;/P&gt;&lt;P&gt;global (outside_PLDT) 101 interface&lt;/P&gt;&lt;P&gt;nat (inside_lan_data) 0 access-list inside_lan_data_nat0_outbound&lt;/P&gt;&lt;P&gt;nat (inside_lan_data) 101 192.168.100.0 255.255.255.0&lt;/P&gt;&lt;P&gt;nat (DMZ_to_Voice) 0 access-list DMZ_to_Voice_nat0_outbound&lt;/P&gt;&lt;P&gt;nat (DMZ_to_Voice) 101 192.168.200.0 255.255.255.0&lt;/P&gt;&lt;P&gt;nat (outside_PLDT) 0 access-list outside_PLDT_nat0_outbound outside&lt;/P&gt;&lt;P&gt;static (DMZ_to_Voice,outside_bayantel) 121.97.xx.xx 192.168.200.2 netmask 255.255.255.255 &lt;/P&gt;&lt;P&gt;static (inside_lan_data,DMZ_to_Voice) 192.168.100.2 192.168.100.2 netmask 255.255.255.255 &lt;/P&gt;&lt;P&gt;static (inside_lan_data,DMZ_to_Voice) 192.168.100.99 192.168.100.99 netmask 255.255.255.255 &lt;/P&gt;&lt;P&gt;static (inside_lan_data,DMZ_to_Voice) 192.168.100.13 192.168.100.13 netmask 255.255.255.255 &lt;/P&gt;&lt;P&gt;access-group outside_bayantel_access_in in interface outside_bayantel&lt;/P&gt;&lt;P&gt;access-group outside_PLDT_access_in in interface outside_PLDT&lt;/P&gt;&lt;P&gt;route outside_bayantel 0.0.0.0 0.0.0.0 121.97.79.25 1 track 1&lt;/P&gt;&lt;P&gt;route outside_PLDT 0.0.0.0 0.0.0.0 192.168.50.1 254&lt;/P&gt;&lt;P&gt;group-policy ccbslan internal&lt;/P&gt;&lt;P&gt;group-policy ccbslan attributes&lt;/P&gt;&lt;P&gt; dns-server value 192.168.100.3 4.2.2.2&lt;/P&gt;&lt;P&gt; vpn-tunnel-protocol IPSec &lt;/P&gt;&lt;P&gt; split-tunnel-policy tunnelspecified&lt;/P&gt;&lt;P&gt; split-tunnel-network-list value ccbslan_splitTunnelAcl&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;how do i allow the remote vpn client to access my router at 192.168.50.1?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 11:06:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/permit-vpn-client-to-access-outside-interface/m-p/793521#M970069</guid>
      <dc:creator>brianbono</dc:creator>
      <dc:date>2019-03-11T11:06:25Z</dc:date>
    </item>
    <item>
      <title>Re: permit VPN client to access outside interface</title>
      <link>https://community.cisco.com/t5/network-security/permit-vpn-client-to-access-outside-interface/m-p/793522#M970070</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You may have to allow same security level interfaces to communicate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;same-security-traffic permit inter-interface&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Sep 2007 14:50:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/permit-vpn-client-to-access-outside-interface/m-p/793522#M970070</guid>
      <dc:creator>acomiskey</dc:creator>
      <dc:date>2007-09-04T14:50:27Z</dc:date>
    </item>
    <item>
      <title>Re: permit VPN client to access outside interface</title>
      <link>https://community.cisco.com/t5/network-security/permit-vpn-client-to-access-outside-interface/m-p/793523#M970071</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;i've done that but still i cannot communicate to my router at Ethernet0/3.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list outside_PLDT_nat0_outbound extended permit ip 192.168.50.0 255.255.255.0 192.168.100.168 255.255.255.248 &lt;/P&gt;&lt;P&gt;nat (outside_PLDT) 0 access-list outside_PLDT_nat0_outbound outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;are this NAT exempt configuration correct?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Sep 2007 16:58:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/permit-vpn-client-to-access-outside-interface/m-p/793523#M970071</guid>
      <dc:creator>brianbono</dc:creator>
      <dc:date>2007-09-04T16:58:31Z</dc:date>
    </item>
    <item>
      <title>Re: permit VPN client to access outside interface</title>
      <link>https://community.cisco.com/t5/network-security/permit-vpn-client-to-access-outside-interface/m-p/793524#M970072</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Not sure if you need the outside keyword on the end, but other than that it looks okay.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does this router have a route to the vpn client subnet?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Sep 2007 18:22:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/permit-vpn-client-to-access-outside-interface/m-p/793524#M970072</guid>
      <dc:creator>acomiskey</dc:creator>
      <dc:date>2007-09-04T18:22:45Z</dc:date>
    </item>
    <item>
      <title>Re: permit VPN client to access outside interface</title>
      <link>https://community.cisco.com/t5/network-security/permit-vpn-client-to-access-outside-interface/m-p/793525#M970074</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;no, the router does not have any route to the vpn client subnet. do i need to add?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Sep 2007 19:21:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/permit-vpn-client-to-access-outside-interface/m-p/793525#M970074</guid>
      <dc:creator>brianbono</dc:creator>
      <dc:date>2007-09-04T19:21:04Z</dc:date>
    </item>
    <item>
      <title>Re: permit VPN client to access outside interface</title>
      <link>https://community.cisco.com/t5/network-security/permit-vpn-client-to-access-outside-interface/m-p/793526#M970076</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The router would need to know how to get to the 192.168.100.168 255.255.255.248 network unless of course it's default route is the ASA.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Sep 2007 19:22:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/permit-vpn-client-to-access-outside-interface/m-p/793526#M970076</guid>
      <dc:creator>acomiskey</dc:creator>
      <dc:date>2007-09-04T19:22:51Z</dc:date>
    </item>
    <item>
      <title>Re: permit VPN client to access outside interface</title>
      <link>https://community.cisco.com/t5/network-security/permit-vpn-client-to-access-outside-interface/m-p/793527#M970077</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks bro... finally I'm able to connect to the router from my remote vpn client.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Sep 2007 21:25:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/permit-vpn-client-to-access-outside-interface/m-p/793527#M970077</guid>
      <dc:creator>brianbono</dc:creator>
      <dc:date>2007-09-04T21:25:21Z</dc:date>
    </item>
  </channel>
</rss>

