NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
famousdavis
Aug 19, 2018Tutor
OpenVPN warning: No server certificate verification method has been enabled
Hi, I've got a new Orbi router (Model RBR20) and two satellites. The router's firmware is V2.1.4.16. I enabled OpenVPN on the Orbi router and it works fine with my mobile device. When I use OpenVP...
- Mar 03, 2019
try adding
remote-cert-tls server
to the end of your config file that should remove the warning
FURRYe38
Aug 20, 2018Guru - Experienced User
There will be separate files for the router and satellites.
- famousdavisAug 20, 2018TutorJust saw your reply, thx. Although, weirdly, on my iPhone and laptop, I can’t scroll down to see your full reply. ??? Not happening with other posts???
- famousdavisAug 20, 2018TutorN/M. It’s just your signature I can’t see in its entirety! :)
- FURRYe38Aug 20, 2018Guru - Experienced User
:smileywink:
- famousdavisAug 21, 2018Tutor
After downloading the latest f/w update for the Orbi router (v2.2.0.68), I've decided to forestall doing anything right now to my Orbi system.
The router's f/w update doesn't disclose what's been changed in the release notes. And the f/w is only for the RBR20 router, not the RBS20 satellites. The Netgear support site for the satellites still shows that f/w v2.1.4.16 is the latest.
It seems based upon my poking around and watching a few videos on the Netgear support site that it's best to keep the router and satellites on the same f/w version, so I'm hesitant to change the f/w right now to address my issue on the router, as that would put it out-of-sync with the f/w used by the satellites. Maybe it's not an issue at all, but I won't know that unless I tamper with a very stable network configuration.
And since the router's f/w release date was literally just a few days ago, I'd rather not be one of the first out of the gate. Having a stable network is a top priority for me more than addressing my OpenVPN warning.
I'll monitor the discussion chatter here and see if others have a similar warning as I've got, and if a firmware update specifically fixes that warning condition (and the MITM threat leading to the warning).
Thanks for your timely reply to my question! Great forum! :)