What's new
  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

OpenVPN config file problem in .35_2

  • Thread starter Thread starter Deleted member 22630
  • Start date Start date
D

Deleted member 22630

Guest
Hi RMerlin,

In the OpenVPN server settings, I enabled "Extra HMAC authorization (tls-auth)" for Incoming (0). The generated config file then contains the line:
Code:
</tls-auth> 1
which cannot be parsed when importing into Android clients.

This should be:
Code:
</tls-auth>
key-direction 1
which is parsed and works properly.

Regards,
Scott.
 
Another problem with OpenVPN server config is that when using username/password authentication, a password with several "." (period) characters is neither displayed, nor works.
 
Another problem with OpenVPN server config is that when using username/password authentication, a password with several "." (period) characters is neither displayed, nor works.

Don't use three dots in a row - this is used to determine if a field is truncated or not.

The same issue would happen in a lot of other places on the webui BTW. This is something that will also happen with the original FW.
 
Hi RMerlin,

In the OpenVPN server settings, I enabled "Extra HMAC authorization (tls-auth)" for Incoming (0). The generated config file then contains the line:
Code:
</tls-auth> 1
which cannot be parsed when importing into Android clients.

This should be:
Code:
</tls-auth>
key-direction 1
which is parsed and works properly.

Regards,
Scott.

I'll have to take a look. The config generation code was developed by Asus, so there might be some issues still left with it as it's fairly new.
 
Hi RMerlin,

In the OpenVPN server settings, I enabled "Extra HMAC authorization (tls-auth)" for Incoming (0). The generated config file then contains the line:
Code:
</tls-auth> 1
which cannot be parsed when importing into Android clients.

This should be:
Code:
</tls-auth>
key-direction 1
which is parsed and works properly.

Regards,
Scott.

Thanks - should be fixed now.
 
I'll have to take a look. The config generation code was developed by Asus, so there might be some issues still left with it as it's fairly new.

I would think so too, seems that the details pages also does not show somehow for my old config, doing a factory reset then comes out fine.
 

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Back
Top