I have a cable modem connected to a Netgear R7000P router. I have a windows 10 64 bit operating system with x64-based processor connected wirelessly to the router. I accessed the router and selected Enable VPN Service. I selected UCP the ports remained 12973 and 12974. Clicked the apply button. Clicked the download "for Windows". Got the following error message: [i]Currently your Dynamic DNS service is not enabled, and the IP address for your Internet connection will be used for client configurations. When the IP address for your Internet connection is changed, you will have to download and install the configuration files again.[/i] Clicked OK and zip downloaded to desktop. Unzipped to New folder on desktop. Folder contains 4 files including ca and client certificates and client1 OpenVPN config. Went to openvpn downloads. Downloaded Windows 64-bit MSI installer file OpenVPN-2.5.7-I602-amd64.msi [b](Question. Is this the correct file?)[/b] I then, from desktop, Tried to installed it. Got the following error message: [i]No readable configuration profiles (config files) found. Use the 'import file..' menu or copy your config files to : "C:\Program Files\OpenVPN\config\" or "C:\Users\MyName\OpenVPN\config\"[/i] None of the usual setup questions happened ie.[i] "Select components to Download", etc.[/i] So I moved all four files from desktop folder contains 4 files including ca and client certificates and client1 OpenVPN config to "C:\Program Files\OpenVPN\config\" Then went to OpenVPN GUI and selected reconnect. (OpenVPN is still on the desktop.) Got the following error message: [i]Mon Jun 27 13:17:23 2022 WARNING: Compression for receiving enabled. Compression has been used in the past to break encryption. Sent packets are not compressed unless "allow-compression yes" is also set. Mon Jun 27 13:17:23 2022 DEPRECATED OPTION: --cipher set to 'AES-128-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-128-CBC' to --data-ciphers or change --cipher 'AES-128-CBC' to --data-ciphers-fallback 'AES-128-CBC' to silence this warning. Mon Jun 27 13:17:28 2022 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.[/i] I will stop here and ask for suggestions. I have tried several things but no luck. Rather than telling you what did not work, thought i'd ask for your thoughts. THANK YOU IN ADVANCE!!

[quote=dropframe post_id=107198 time=1656354464 user_id=57398] I have tried several things [/quote]For example ? This may help you to get started: https://community.openvpn.net/openvpn/wiki/OpenVPN-GUI-New[quote=dropframe post_id=107198 time=1656354464 user_id=57398] Went to openvpn downloads. Downloaded Windows 64-bit MSI installer file OpenVPN-2.5.7-I602-amd64.msi (Question. Is this the correct file?) I [/quote]Yes. And it is not OpenVPN-Connect-Windows, which is where you originally posted and why your thread has been moved. BTW: We don't support your router, you're on your own there. Other help: https://community.openvpn.net/openvpn/wiki/HOWTO https://forums.openvpn.net/viewtopic.php?t=22603#p68963

MORE INFO After doing everything in original post I did the following: Went into Ethernet setting and changed TAP-Windows adapter Name to NETGEAR-VPN Then I went to Program Files>OpenVPN>config. I right clicked on "client1" and selected "Start OpenVPN on this config file" Got the following error message: [i]2022-06-29 11:59:58 WARNING: Compression for receiving enabled. Compression has been used in the past to break encryption. Sent packets are not compressed unless "allow-compression yes" is also set. 2022-06-29 11:59:58 DEPRECATED OPTION: --cipher set to 'AES-128-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-128-CBC' to --data-ciphers or change --cipher 'AES-128-CBC' to --data-ciphers-fallback 'AES-128-CBC' to silence this warning. 2022-06-29 11:59:58 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.[/i] What is my next step?

More info and things I've done: Added line [i]remote-cert-tls server[/i] to client1 opvn file. This gets rid of error message: [i]WARNING: No server certificate verification method has been enabled.[/i] [b]Question: Should I have added this line? [/b] Now when I run OpenVPN it gives the following error message: [i]WARNING: Compression for receiving enabled. Compression has been used in the past to break encryption. Sent packets are not compressed unless "allow-compression yes" is also set. Thu Jun 30 13:34:17 2022 DEPRECATED OPTION: --cipher set to 'AES-128-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-128-CBC' to --data-ciphers or change --cipher 'AES-128-CBC' to --data-ciphers-fallback 'AES-128-CBC' to silence this warning.[/i] AND stuck in "Current state: connecting" [b]Question: Should I worry about these error messages? Do I need to do anything about them?[/b] [b]Question: I have done nothing relating to Dynamic DNS. Do I need to set up Dynamic DNS? [/b] THANK YOU FOR YOUR HELP!!

[quote=dropframe post_id=107251 time=1656614541 user_id=57398] his gets rid of error message: WARNING: No server certificate verification method has been enabled. Question: Should I have added this line? [/quote]Yes. [quote=dropframe post_id=107251 time=1656614541 user_id=57398] Now when I run OpenVPN it gives the following error message: WARNING: Compression for receiving enabled. Compression has been used in the past to break encryption. Sent packets are not compressed unless "allow-compression yes" is also set. Thu Jun 30 13:34:17 2022 DEPRECATED OPTION: --cipher set to 'AES-128-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-128-CBC' to --data-ciphers or change --cipher 'AES-128-CBC' to --data-ciphers-fallback 'AES-128-CBC' to silence this warning. AND stuck in "Current state: connecting" Question: Should I worry about these error messages? Do I need to do anything about them? [/quote]Yes. [b]Disable[/b] compression and --cipher in your [b]server and client[/b]. [quote=dropframe post_id=107251 time=1656614541 user_id=57398] Question: I have done nothing relating to Dynamic DNS. Do I need to set up Dynamic DNS [/quote]Dynamic DNS usually helps.

[b]Question: How do I correct the following errors? Can't find any help.[/b] [i]WARNING: Compression for receiving enabled. Compression has been used in the past to break encryption. Sent packets are not compressed unless "allow-compression yes" is also set. Thu Jun 30 13:34:17 2022 DEPRECATED OPTION: --cipher set to 'AES-128-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-128-CBC' to --data-ciphers or change --cipher 'AES-128-CBC' to --data-ciphers-fallback 'AES-128-CBC' to silence this warning.[/i] How do I Disable compression and --cipher in your server and client THANKS EVERYONE and especially TinCan Tech

[quote=dropframe post_id=107253 time=1656622074 user_id=57398] How do I Disable compression and --cipher in your server and client [/quote] Have you ever heard of google ?

Last time I used Google I learned that the Earth is flat, that Trump is still president, JFK is alive snd well. I prefer to get my information from a more trusted place.

More things I've done: On my client1 .opvn file I replaced cipher line with: [i]cipher AES-256-GCM[/i] This replaces "cipher AES-128-CBC" [b]Question: Is this sufficient? Should I just delete the cipher line all together? Now what do I need to do on the router side regarding compression?[/b] I only have one error message now: [i]Fri Jul 1 12:35:47 2022 WARNING: Compression for receiving enabled. Compression has been used in the past to break encryption. Sent packets are not compressed unless "allow-compression yes" is also set.[/i] I am still NOT able to connect. When I select connect, it goes to "connecting" and stays there. Never connects.

Do [u]not[/u] use --[b]cipher[/b], it is deprecated, just as your log shows.

Netgear R7000P

TinCanTech

Start from scratch .. may be.

dropframe

Tech support from SurfShark told me that my router Netgear R7000P can only be set up as an OpenVPN server and NOT as an OpenVPN client.
does that make any sense to you?

Looks like I can make my computer go through a SurfShark ip in another country but not everything that goes through my router.

TinCanTech

We do not provide support for either Surfshark or your router.

If you require personal support then I am available for hire.

dropframe

Not looking for Surfshark support. Just telling you what they said about your product and looking for confirmation or another viewpoint.
Do you think OpenVPN can be used as a client on Netgear R7000P?

TinCanTech

OpenVPN Community edition is a server and client Open source program.

Your router is obviously trash.

dropframe

Why would you say my router is trash?
I got the impression that it would work with OpenVPN. I don't necessarily believe what I was told by another company.
Just wanted your opinion. I'm willing to do as you suggested and start over. If you think it has a chance of working.
Sounds like they don't know what they are talking about. The router has instructions "OpenVPN client setup instruction" right in their advanced setup menu.

dropframe

Since Surfshark has added a new protocol "Wireguard" and seems to automatically select it, do I need to specify UDP as the protocol with them since in my client.opvn file, proto is udp and none of the other proto choices are wireguard?

TinCanTech

dropframe wrote Why would you say my router is trash?

If you have read your router manual then it must be trash, otherwise you would understand how it works.:

dropframe

openvpn_inc

Hi drop,

This is the OpenVPN community forum. We do not support Wireguard here in any form. But they are a worthy project, feel free to check them out.

Regarding the "trash" comment, while I do try to be a bit more sensitive in my word choices (not always succeeding, haha) I can tell you this: the openvpn(8) software, as Tin noted, is both client AND server, in a single binary. It will be either, depending on the configuration you give it.

The fact that your router can only be a server means that the Netgear developers have artificially limited the software or the configuration. If they knew more about openvpn they would not have done that. From what I read in this thread (note: I have not done any research of your router product, just taking your word for it) it is apparent that these people do not know enough about openvpn to make a GUI for it.

So there you have it. I tend to see it in similar terms as Tin expressed.

regards, rob0

« Previous Page