OPNsense Forum

Archive => 19.1 Legacy Series => Topic started by: Nico on February 01, 2019, 04:38:02 pm

Title: New OpenVPN Export does not work with Windows because of UDP instead of udp
Post by: Nico on February 01, 2019, 04:38:02 pm

Hi,

just upgraded to the newest production release and found the new OpenVPN export utility which I generally like. However it exports the config with

remote <ip> <port> UDP

which does not work with the Windows client. It needs to be "udp" instead and it will work flawlessly.

I haven't tested other OS or clients.

Title: Re: New OpenVPN Export does not work with Windows because of UDP instead of udp
Post by: AdSchellevis on February 01, 2019, 05:30:24 pm

can you try https://github.com/opnsense/core/commit/e9d1aa457903b335c980b10ef7f37b23b5518ce7 (https://github.com/opnsense/core/commit/e9d1aa457903b335c980b10ef7f37b23b5518ce7) ?

From the console, install using:

Code: [Select]

opnsense-patch e9d1aa4


Title: Re: New OpenVPN Export does not work with Windows because of UDP instead of udp
Post by: Antaris on February 02, 2019, 09:59:08 am

i also observed this and 'comp-lzo' not inserted in .OVPN file also.

Title: Re: New OpenVPN Export does not work with Windows because of UDP instead of udp
Post by: Nico on February 04, 2019, 09:44:02 am

Quote from: AdSchellevis on February 01, 2019, 05:30:24 pm

can you try https://github.com/opnsense/core/commit/e9d1aa457903b335c980b10ef7f37b23b5518ce7 (https://github.com/opnsense/core/commit/e9d1aa457903b335c980b10ef7f37b23b5518ce7) ?

From the console, install using:

Code: [Select]

opnsense-patch e9d1aa4


I'm sure this will work. As stated it is very clear what the issue is and I can manually update the generated file myself. It was more a hint for the next release since others may have issues with that as well since it seems to affect the Windows client in all versions.

Title: Re: New OpenVPN Export does not work with Windows because of UDP instead of udp
Post by: franco on February 04, 2019, 11:50:06 am

Hi Nico,

It's mentioned for reference for everyone who reads this and wants a quick and official solution. :)

It's also being fixed for 19.1.1 tomorrow.


Cheers,
Franco