Dlink DI-804HV to IPCop VPN connection

Jun 28, 2005 1 Replies

I needed more room in my home office so I downsized from an IPCop firewall to a Dlink DI-804HV router w/ VPN capability. I have spent most of two days trying to get the VPN link re-established between the Dlink and a remote IPCop box at my company headquarters. I am amazed that something so easy to do with Linux (IPCop) seems impossibly complicated with the Dlink. No matter what I try, I cannot get the VPN tunnel to establish between the Dlink and the remote IPCop box.



I am well versed in TCP/IP, setting up an IpCop firewall, etc, but my VPN knowledge is very thin and I don't have time to become an expert right now. Googling the web and usenet for hours has not helped either. Help would be appreciated.



In a nutshell, here's what I would like to know: how do I transfer my IPCop VPN settings over to the Dlink to establish a tunnel with a remote IPCop box? In IPCop you use these parameters to set up a VPN tunnel, and this is all you need:



Local Subnet IP Local Subnet Mask Local Subnet next hop (i.e., the local router) Remote Subnet IP Remote Subnet Mask Remote Subnet next hop (i.e., the remote router) UserName Password



The Dlink, on the other hand, has many configuration parameters, some of which resemble those above, and many others (encryption and authorization algorithms, DH Groups, IKE proposals, IpSec Proposals, etc etc.) which even the Dlink tech support folks could not explain to me (yes, I've been on the phone with them for a couple of hours).



No matter how I try to configure the Dlink using my old IpCop parameters, the VPN tunnel will not work. Sometimes the Dlink actually lists an open VPN tunnel on its VPN Status page, but I cannot ping from the local network to the remote one.



Has anyone done this before, or can you help in any way? Thanks very much.



Alan


OK. Eventually figured it out. Hope this helps someone else:

DI-804HV admin interface:

Home > VPN page: VPN Enable: checked Tunnel Name: MyTunnel (or whatever you want) Method: IKE

Click Tunnel Name: (should by MyTunnel entered before) Local Subnet: x.x.x.x Local Netmask: x.x.x.x Remote Subnet: y.y.y.y Remote Netmask: y.y.y.y Remote Gateway: z.z.z.z Preshare Key: this is the Password on the IPCop side

Click Proposal ID: 1 (or a free one) Proposal Name: freeswan (or whatever you want) DH Group: Group 2 Encrypt Algorithm: 3DES Auth Algorithm: SHA1 Life Time: 28800 Life Time unit: Sec

Bottom of the screen: Select Proposal ID 1 (or whatever you used above) Proposal Index Proposal Name should appear in IKE Proposal index at the top of the screen.

Click Proposal ID: 1 (or a free one) Proposal Name: freeswan (or whatever you want) DH Group: Group 2 Encap Protocol: ESP Encrypt Algorithm: 3DES Auth Algorithm: MD5

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required