[bryancn]

Alex

Following you time out ptoblem you say: “The VaporSec ‘Show ’em’ output indicates there are IPSec tunnels between 192.168.2.1 and 192.168.2.2. But I cannot ‘ping’ the IP address of 192.168.2.1”

What does a tail of system.log produce? Mine always contains something like “phase2 negotiation failed due to time up waiting for phase1. ESP 210.54.170.19->192.168.2.2 ” which I think means the VaporSec/Router combination can’t handle NAT translation.

B

[bryancn]

Thanks Joel – a typo of course, allowing progress to the next problem (opportunity?).

The issue is NAT Traversal, I think. I have a belkin 54g wireless router with udp port 500 open and get:

Dec 30 19:16:05 localhost racoon: ERROR: isakmp.c:2033:isakmp_chkph1there(): phase2 negotiation failed due to time up waiting for phase1. ESP 210.54.170.19->192.168.2.2

The server is trying to negotiate with my internal IP so I assume the router isn’t handling this. Did I read somewhere that Vaporsec handles NAT traversal or is it something that you set up at the server (in my case FreeS/WAN) end?

You (Pat) say you configured your client inside the router. Did you have to cope with this?

[Author]

Posts