<?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: Cisco ASA Site-to-Site VPN in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/cisco-asa-site-to-site-vpn/m-p/5035889#M1109723</link>
    <description>&lt;P&gt;Thanks&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/97036"&gt;@Rob Ingram&lt;/a&gt;. I was able to get this working in a lab as expected using distribution lists for the BGP peer in AWS.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 07 Mar 2024 13:37:39 GMT</pubDate>
    <dc:creator>MattMH</dc:creator>
    <dc:date>2024-03-07T13:37:39Z</dc:date>
    <item>
      <title>Cisco ASA Site-to-Site VPN</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-site-to-site-vpn/m-p/5034474#M1109649</link>
      <description>&lt;P&gt;I have a 2-part question for setting up a site-to-site VPN with a vendor.&lt;/P&gt;&lt;P&gt;Question 1&lt;/P&gt;&lt;P&gt;We have /28 subnet assigned to us from our ISP. Our ASA is using .2 and our default route is .1 to the ISP. I do not want to set this site-to-site VPN up using our .2 IP address. I'd like to use a .10 IP address. When I am working through the site-to-site VPN wizard, I can only choose the interface assigned to "outside". Is there any way, maybe through CLI, that I can use a.10 IP address for the site-to-site VPN? If so, would I need to create an object, or not necessary?&lt;/P&gt;&lt;P&gt;Question 2&lt;/P&gt;&lt;P&gt;The vendor (this is an AWS peer) can BGP peer with my ASA via the tunnel, but I really do not want to redist to them our entire route table. Since I can't run 2 separate BGP AS's on the ASA, should I just stick with static routes between us and them? Any recommendations?&lt;/P&gt;</description>
      <pubDate>Tue, 05 Mar 2024 16:15:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-site-to-site-vpn/m-p/5034474#M1109649</guid>
      <dc:creator>MattMH</dc:creator>
      <dc:date>2024-03-05T16:15:11Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA Site-to-Site VPN</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-site-to-site-vpn/m-p/5034478#M1109650</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1423319"&gt;@MattMH&lt;/a&gt; from ASA 9.19 you can use loopback interfaces for a VPN (VTI only), but that would have to be a different routed public subnet to the physical outside interface. Other than that you have to use the interface (outside) IP address to terminate a VPN.&lt;/P&gt;
&lt;P&gt;You can use statics or filter what routes are redistributed via BGP to AWS.&lt;/P&gt;</description>
      <pubDate>Tue, 05 Mar 2024 16:21:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-site-to-site-vpn/m-p/5034478#M1109650</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2024-03-05T16:21:16Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA Site-to-Site VPN</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-site-to-site-vpn/m-p/5035889#M1109723</link>
      <description>&lt;P&gt;Thanks&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/97036"&gt;@Rob Ingram&lt;/a&gt;. I was able to get this working in a lab as expected using distribution lists for the BGP peer in AWS.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 07 Mar 2024 13:37:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-site-to-site-vpn/m-p/5035889#M1109723</guid>
      <dc:creator>MattMH</dc:creator>
      <dc:date>2024-03-07T13:37:39Z</dc:date>
    </item>
  </channel>
</rss>

