06-08-2003 11:27 AM - edited 02-21-2020 12:35 PM
I have a tipical PIX-2-PIX (site-2-site) VPN tunnel established and working fine. However, I don't want to allow everybody on the Internet to chat ESP/IKE with my VPN peer/firewall.
Can this be blocked at all? I've tried permitting all ESP and 500/UDP only from trusted VPN peers on my external interface (with my external IP as the destination) and blocking everything else, but it didn't work.
I have 'no sysopt permit-ipsec'. in my config.
Thanks.
06-09-2003 07:57 PM
What "didn't work"? What happened? Disabling "sysopt connection permit-ipsec" and adding an outside ACL only allowing IPSec traffic should be enough.
Keep in mind also that unless a host has a valid isakmp key defined (which in your case with just L2L tunnels it should not), then they won't get very far through the negotiation.
06-10-2003 06:05 AM
Any host can try to initiate an IKE negotation to my firewall's external interface/address. Sure, they don't know the pre-share key, but it can be guessed.
Having 'no sysopt connection permit-ipsec' and ACLs on outside interface is enough for protecting traffic going to hosts in the VPN protected domains, but not to the firewall itself. AFAIK, you can't limit IKE negotations to particular hosts. This is bad, IMHO.
Any chance this can be changed in future PIX versions?
06-10-2003 07:01 AM
This is why we use certificates for our authentication. You can use the free certificate server in Win2k to do it. We happen to use Verisign because we built this before MS was supported.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide