18547 openvpn

[Kid3t3rnity]

Spent all day trying to establish a VPN connection without success.
Never thought that it may be the updated 18547 that could be the cause !!
After many hours of trying nearly every server configuration I could from my VPN provider and not a single reply from their support I thought I would find a forum [emoji102] So here I am and I have just backdated my firmware to 3.0.0.4.380_7743-g2cf84e9 and setup an openvpn config and yes..... Connection 1st time.
Has anyone else had this problem with the new firmware and not being able to establish a VPN connection ?
Is there an easy work around as now I keep getting the update notification lol ?

P.s I'm new and I only know of one way to input my openvpn configs which I upload the openvpn.ovpn and CA.crt but then have to manually copy paste the client key/crt ! Is this normal ?

Kindest regards
Kid

Sent from my ONEPLUS A5000 using Tapatalk

 

[hp-snb]

Yep, same issue here.

I rolled my RT-AC68U back to build 830_7378 which works as advertised.

I am not aware of a work-around, so I stick with the 830 branch until either ASUS fixes this or until an Asuswrt-Merlin version for my router is available.

Did you report this issue to Asus?
I did, but it might help if more affected users do so.

Best regards,

 

[Kid3t3rnity]

Yep, same issue here.

I rolled my RT-AC68U back to build 830_7378 which works as advertised.

I am not aware of a work-around, so I stick with the 830 branch until either ASUS fixes this or until an Asuswrt-Merlin version for my router is available.

Did you report this issue to Asus?
I did, but it might help if more affected users do so.

Best regards,

I will look into reporting it for sure. Literally pulling my hair out all day ( might be why I'm bald [emoji102] ).

Sent from my ONEPLUS A5000 using Tapatalk

 

[hp-snb]

Literally pulling my hair out all day ( might be why I'm bald [emoji102] ).

Sounds familiar, I spent Saturday afternoon on this issue and I tried again with a fresh approach this morning. Both occasions same result

 

[Kid3t3rnity]

Sounds familiar, I spent Saturday afternoon on this issue and I tried again with a fresh approach this morning. Both occasions same result

I'm with cyberghost ! Who you with ?
I don't think I will be getting any discounts from CG after the messages I've been sending them lol [emoji44] might have to go and send apologies to them [emoji848]

Sent from my ONEPLUS A5000 using Tapatalk

 

[hp-snb]

I am with PIA, but that makes no difference at all for this issue.

I gathered there was something wrong with the FW when I updated from a working version to a build which would not connect to PIA. I just wanted to rule out configuration errors from my side, so I revisited the issue this morning.

In a way I am glad you are having this issue too, with another VPN provider, that rules out other causes

 

[Kid3t3rnity]

I am with PIA, but that makes no difference at all for this issue.

I gathered there was something wrong with the FW when I updated from a working version to a build which would not connect to PIA. I just wanted to rule out configuration errors from my side, so I revisited the issue this morning.

In a way I am glad you are having this issue too, with another VPN provider, that rules out other causes

Yes that's the reason I asked, just to clarify that it's not vendor specific but hardware with Asus firmware. [emoji106]

Sent from my ONEPLUS A5000 using Tapatalk

 

[Kid3t3rnity]

I am with PIA, but that makes no difference at all for this issue.

I gathered there was something wrong with the FW when I updated from a working version to a build which would not connect to PIA. I just wanted to rule out configuration errors from my side, so I revisited the issue this morning.

In a way I am glad you are having this issue too, with another VPN provider, that rules out other causes

Hi hp-snb

Just thought I would update on issue, I have today updated to latest firmware and all seems well again for me.

I updated without a factory reset. I'm not sure what the terminology for this method is in router land [emoji23] but it's like a dirty flash in android [emoji106] where we just update over existing firmwares without wiping.



Sent from my ONEPLUS A5000 using Tapatalk

 

[hp-snb]

Hi Kid3t3rnity,

I am glad you have the issue solved, congratulations!

I had less luck.
The issue has been escalated by our local ASUS representatives to Taiwan, so far no feedback from them.
I tried the 3.0.0.4.382.18881 build last week but it did not solve the issue here, all I noticed were some new issues (non-VPN client related). I did a factory reset - install dance though

When you read the various topics here on SNB forums it seems there are several fresh bugs in the latest 382 build, which is why I migrated to Asuswrt-Merlin yesterday.
So far it works like a charm for me, no issues whatsoever.
I am prepared to say goodbye to the stock firmware and stick with Merlin's magic

 

[Kid3t3rnity]

Anything specific needed to use Merlin ?
Is it a simple flash like we do when down grading firmware ?
Might give it a go if it's a simple process [emoji848]

Sent from my ONEPLUS A5000 using Tapatalk

 

[hp-snb]

It is pretty straightforward, even I with my deteriorating old brain could do it
VPN setup is quite different from stock firmware, but there is an excellent guide here.

 

[Kid3t3rnity]

Perfect, thanks for that. I will have a read through and may take to Merlin [emoji106]

Sent from my ONEPLUS A5000 using Tapatalk

 

[hp-snb]

Follow-up to message #9 .....

ASUS let me know that they can not duplicate the issue.
In order to duplicate it they would have to log-in to PIA, which they apparently did not do.
End of story.

I feel very fortunate there is a wonderful alternative in Merlin's firmware!

 

[hp-snb]

For the record, for completeness' sake, not knowing if you @Kid3t3rnity still visit these forums.......

I have fixed the problem on my side.
It appears that in firmware branch 382 and higher the OpenVPN client password length is limited to 16 characters. Mine was 20, hence the authorization error.
As soon as I shortened the password to 16 characters everything works as advertised.

Hope this helps,

 

[Kid3t3rnity]

For the record, for completeness' sake, not knowing if you @Kid3t3rnity still visit these forums.......

I have fixed the problem on my side.
It appears that in firmware branch 382 and higher the OpenVPN client password length is limited to 16 characters. Mine was 20, hence the authorization error.
As soon as I shortened the password to 16 characters everything works as advertised.

Hope this helps,

My passwords never exceeded 16 characters [emoji848] but my VPN provider used ipv6 so advised to enable ipv6 passthrough which solved my issue but no longer with the same provider and no further issues to date [emoji106]

Sent from my ONEPLUS A5000 using Tapatalk