BEFVP41: This tunnel should not be initiator !

[Dreddnews]

I cannot connect any tunnels I create with my BEFVP41. I always get this error: 00:00:04 IKE[1] ERROR: This tunnel should not be initiator !

I followed the directions from Linksys's website on connecting SSH's Sentinel to the router. Does anyone know what this means since Linksys is giving me the run around.

Thanks!

 

[markku]

If you are using Sentinel pls follow the instructions in

http://www.ssh.com

no other instructions.

Since your Sentinel is residing in dynamic IP there is no way you can initiate the tunnel from BEFVP. You can fire up the tunnel from Sentinel only.

 

[Dreddnews]

I'll walk thru the steps again tonight... but the directions on Linksys's site are taken from the guide given on SSH's site. So the client itself will intiate the tunnel? Then why does the BEFVP41 have a connect button on its screen when you go to the router setup?

 

[markku]

Connect-button is intended for box-to-box VPN

 

[Dreddnews]

Ok great. Thanks for the help and I'll go back through my settings on Sentinel.

 

[Dreddnews]

I went straight threw the documentations from SSH on how to connect to my BEFVP41. This is starting to get annoying that after 6 months I can't get one client to connect. I even used their same example pre-shared key and I still can't access the VPN. I keep getting errors from Sentinel saying that my gateway might not be online or that I have incorrect authentication key settings. Well if they are wrong, then the documentation is wrong since that is where I got it from. What is left for me to do? I emailed SSH to see if they can understand my logs and locate a problem.

 

[markku]

Is your BEFVP in static IP = are you really connecting to your Linky. Other possibility is to use DDNS in case of dynamic IP of Linky.

There should be something in the log of Linky if you are connecting it Sentinel

 

[Dreddnews]

My BEFVP41 has a dynamic WAN IP assigned to it by way of the Roadrunner Cable modem. The LAN IP of the BEFVP41 is 192.168.1.1 since it is my gateway for the network.

 

[markku]

Question remains: How are you connecting to your Linkys WAN IP address? Do you know it in advance or are you using DDNS?

 

[Dreddnews]

Well for me to gain access to my network from an external connection, I do so thru my domain name that is registered and my server runs a dynamic dns updated. But since I am testing this VPN locally first off to see if it works, what does my wan address have anything to do with it? Now Roadrunner uses DHCP for my WAN IP. So I do not have a static address, that is why I have to use a domain name with dynamic updating. Does this help any?

 

[markku]

If you are testing this locally, you have to connect to WAN port of BEFVP. This can be simulated by removing WAN connection from the net and connecting your PC to WAN port of the router and giving BEFVP and PC a static IP in the same subnet.

Testing is not necessary though, Sentinel and BEFVP work very well together. DDNS in BEFVP is a good solution.

 

[Dreddnews]

Why do I need the DDNS when I already use Dynamic DNS on my Windows 2000 Server for my website and 2k domain?

 

[markku]

No, you do not.

BEFVP41 with latest beta is capable of doing DDNS without any external software though.