<?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: ASA with two WebVPN interfaces in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-with-two-webvpn-interfaces/m-p/4015360#M23071</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for quick reply.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;One more demand.&lt;/P&gt;&lt;P&gt;Let's say, on current webvpn I have tunnel-group 12345.&lt;/P&gt;&lt;P&gt;I will create new one (for inside) 54321.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But, what I need, is:&lt;/P&gt;&lt;P&gt;1) from outside I will see (in client) only 12345&lt;/P&gt;&lt;P&gt;2) from inside I will see (in client) only 54321&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There will be no possibility to use tunnel-group 54321 from outside and vice versa.&lt;/P&gt;&lt;P&gt;I cannot find any solution, to limit tunnel-groups in that way.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Pavel&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 21 Jan 2020 14:38:14 GMT</pubDate>
    <dc:creator>Pavel Pokorny</dc:creator>
    <dc:date>2020-01-21T14:38:14Z</dc:date>
    <item>
      <title>ASA with two WebVPN interfaces</title>
      <link>https://community.cisco.com/t5/network-security/asa-with-two-webvpn-interfaces/m-p/4015234#M23067</link>
      <description>&lt;P&gt;Dear all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please advice, what are possibilities.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;AsIs situation: ASA with webvpn configured on outside interface. This is pretty standard solution which is working for many years.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ToBe situation: add possibility to connect via VPN client on inside interface. But here comes the trick. I would like to have (on this new headend) different tunnel-groups and with this also different ip-pool for clients.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is it even possible (9.8 version)?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Pavel&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 21 Jan 2020 11:51:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-with-two-webvpn-interfaces/m-p/4015234#M23067</guid>
      <dc:creator>Pavel Pokorny</dc:creator>
      <dc:date>2020-01-21T11:51:58Z</dc:date>
    </item>
    <item>
      <title>Re: ASA with two WebVPN interfaces</title>
      <link>https://community.cisco.com/t5/network-security/asa-with-two-webvpn-interfaces/m-p/4015306#M23069</link>
      <description>Hi,&lt;BR /&gt;Yes this should be possible. You would need to:-&lt;BR /&gt;&lt;BR /&gt;- Enabled SSL/IKEv2 IPSec on the INSIDE interface.&lt;BR /&gt;- Create additional IP Pools&lt;BR /&gt;- Create a new Group Policy, reference the new IP Pool within the Group Policy&lt;BR /&gt;- Create a new tunnel group, reference the new group policy within the tunnel group.&lt;BR /&gt;&lt;BR /&gt;You should then connect to the new tunnel group and receive an IP address from the new IP Pool. You would probably also need a new NAT exemption rule to ensure traffic from the new IP Pool to the local internal network is not natted.&lt;BR /&gt;&lt;BR /&gt;If you need further assistance please upload your configuration.&lt;BR /&gt;HTH</description>
      <pubDate>Tue, 21 Jan 2020 13:37:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-with-two-webvpn-interfaces/m-p/4015306#M23069</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2020-01-21T13:37:05Z</dc:date>
    </item>
    <item>
      <title>Re: ASA with two WebVPN interfaces</title>
      <link>https://community.cisco.com/t5/network-security/asa-with-two-webvpn-interfaces/m-p/4015360#M23071</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for quick reply.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;One more demand.&lt;/P&gt;&lt;P&gt;Let's say, on current webvpn I have tunnel-group 12345.&lt;/P&gt;&lt;P&gt;I will create new one (for inside) 54321.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But, what I need, is:&lt;/P&gt;&lt;P&gt;1) from outside I will see (in client) only 12345&lt;/P&gt;&lt;P&gt;2) from inside I will see (in client) only 54321&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There will be no possibility to use tunnel-group 54321 from outside and vice versa.&lt;/P&gt;&lt;P&gt;I cannot find any solution, to limit tunnel-groups in that way.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Pavel&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 21 Jan 2020 14:38:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-with-two-webvpn-interfaces/m-p/4015360#M23071</guid>
      <dc:creator>Pavel Pokorny</dc:creator>
      <dc:date>2020-01-21T14:38:14Z</dc:date>
    </item>
  </channel>
</rss>

