<div>
Thanks Aarie, completely what I thought - just needed a confirmation. &nbsp;Thank you
</div>


<div>
<div class="content wysiwyg-content">
Hello,<br />
How would you configure a S2S connection with a vendor who requires you to have a PUBLIC address as the source on the tunnel.<br />
<br />
<br />
Currently I have a pair Cisco ISR's devices doing our production NAT and FWing. &nbsp;Since this is a temporary solution, I plan to configure a standalone ISR that will participate in the vendor S2S VPN connection. The servers that need access to the the vendors tunnel are NATTED on the core's. My thought process is to simply put a static route on my core to point at the temp ISR performing the 2S2 to get to that network. This should all work, but I am concerned on how to set up the NAT on the S2S Tunnel so that it looks like they are coming from one of our public addresses. They are putting a filter in place and will only accept the PUB address.
</div>
</div>


Hello,
How would you configure a S2S connection with a vendor who requires you to have a PUBLIC address as the source on the tunnel.


Currently I have a pair Cisco ISR's devices doing our production NAT and FWing.  Since this is a temporary solution, I plan to configure a standalone ISR that will participate in the vendor S2S VPN connection. The servers that need access to the the vendors tunnel are NATTED on the core's. My thought process is to simply put a static route on my core to point at the temp ISR performing the 2S2 to get to that network. This should all work, but I am concerned on how to set up the NAT on the S2S Tunnel so that it looks like they are coming from one of our public addresses. They are putting a filter in place and will only accept the PUB address.

Thanks Aarie, completely what I thought - just needed a confirmation.  Thank you

S2S VPN - connection to a partner site, requires using PUB NATTED address on the tunnel

Hello,
How would you configure a S2S connection with a vendor who requires you to have a PUBLIC address as the source on the tunnel.


Currently I have a pair Cisco ISR&amp;#39;s devices doing our production NAT and FWing.  Since this is a temporary solution, I plan to configure a standalone ISR that will participate in the vendor S2S VPN connection. The servers that need access to the the vendors tunnel are NATTED on the core&amp;#39;s. My thought process is to simply put a static route on my core to point at the temp ISR performing the 2S2 to get to that network. This should all work, but I am concerned on how to set up the NAT on the S2S Tunnel so that it looks like they are coming from one of our public addresses. They are putting a filter in place and will only accept the PUB address.

Network Management involves issues that are independent of specific hardware or software, including email policies, upgrade planning, backup scheduling and working with managed service providers for Desktop-As-A-Service (DaaS), Software-As-A-Service (SaaS) and the like through the use of tools, coupled with manufacturer standards, best practice guidelines, policies and procedures plus all other relevant documentation. Network management also includes monitoring, alerting and reporting, management reporting, planning for device or service updates, the backup of configurations, the setting of key performance indicators and measures (KPIs/KPMs), associated service level agreements and problem records as part of the IT Service Management (ITSM) framework.