Custom VPN parameters

Published 10 years ago

Good day,

I'm struggling with L2TP VPN connections using a pre-shared key. We are using a small 2000 entries in the enterprise edition with our whole support team.

We want a centralized solution for connecting to customer networks. Using PPTP and a central .pbk file, everything is working fine.

Since I’m unable to add a pre-shared key within the .pbk, I am going for the work around with a PowerShell script using “Add-VpnConnection”.

Now on to the bug report ;-)

If I add an entry and define a Custom VPN to it, the tab “settings” gives me 4 parameters.

The parameters $VPN_USERNAME$, $VPN_DOMAIN$ and $VPN_HOST$ work fine.

If I use the parameter $VPN_PASSWORD$, it gives me the value of the $VPN_USERNAME$ .

I’ve checked Security\Allow password in variable

I’ve also tried Data Source Settings\Password Policy\Allow password in macro (from another post)

Could you look into this for me please?

Also, any other hints regarding L2TP and preshared key usage is welcome ;-)

Thanks!

Sander

All Comments (22)

Marc Beausejour

Published 10 years ago

Hello,

What version of RDM are you using?

What type of data source are you using?

Best regards,

Marc Beauséjour

sander

Published 10 years ago

Hi Marc,

I'm using 11.7.2.0 with a Microsoft SQL Database.

Sander

sander

Published 10 years ago

Hi Marc,

Just tested it with 11.7.2.0 with a local data source (XML), but still the same error.

Also tried to run it in 64 bit mode.

Sander

sander

Published 10 years ago

Had an old 11.6.1.0 version; tested it with SQL, same error

David Hervieux

Published 10 years ago

Hi,

I've found the bug and this is fixed internally. I could send you an hot fix if you want.

Regards

David Hervieux

sander

Published 10 years ago

Hi David, yes please!

David Hervieux

Published 10 years ago

Hi,

I've posted the patch here. It's too big for an email

David Hervieux

sander

Published 10 years ago

Hi David,

Sorry for getting back to you after so long.

The modifications work fine now!

Do you include them in the next release?

Thanks!

Sander

sander

Published 10 years ago

Hi David,

One other question. It looks like the parameters aren't sent when the closing arguments kick in.

Could you check that for me?

Sander

sander

Published 10 years ago

I discovered that when you let RDM disconnect the VPN connection after ending the session, the parameters are sent correctly.

Only when using the "Close VPN" button, the paramters are not used.

"Open VPN" works fine.

Sander

Hubert Mireault

Published 10 years ago

Hello,

I've tried reproducing the issue on RDM 11.7.2.0 but the closing argument is sent properly. Do you send any special characters or anything of the sort? What do your closing arguments look like so we can test with something similar?

Regards,

Hubert Mireault

sander

Published 10 years ago

Hi Hubert,

This is my closing argument:

\192.168.1.1\Shares\Script.ps1 $VPN_HOST$ disconnect

This is what I entered within the VPN type Custom:

Host: example.domain.com

Executable: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe

Opening argument: \192.168.1.1\Shares\Script.ps1 $VPN_HOST$ $VPN_USERNAME$ $VPN_DOMAIN$ $VPN_PASSWORD$

Closing argument: \192.168.1.1\Shares\Script.ps1 $VPN_HOST$ disconnect

Wait interval: 2 sec

Run in 64 bit: enabled

Run in background: disabled

Username: testuser

Domain: testdomain

Password: testpassword

I'm using 11.7.2.0 also, but with the modified files by David in this topic.

Sander