Is vpn_loglevel still hardcoded at 3?

[Deleted member 27741]

Hello, I've been trying to alter the log level for the openvpn servers on my n66u. Is it still hardcoded at 3 or can I change it? It looks like it is changed when I do the nvram set/commit dance, but the logging does not seem to change at all?

 

[kvic]

I think you're referring to the nvram variable, vpn_loglevel. You can increase logging by changing this value.

Also, you can always override with standard openvpn option in custom config window. That's my preferred way. Read openvpn man page for details.

Btw, if you don't have a more functional syslog (the one shipped in Asus/Merlin is not), don't bother to enable more openvpn logging for daily use. It'll swamp your syslog.log.

 

[Deleted member 27741]

@kvic- what do you use as a syslog other than what comes with rmerlin?

I was actually asking about decreasing the log level. Can anyone confirm they have been able to decrease the amount of openvpn logging, not just decreasing the variable(s) but less writing to the log?

 

[kvic]

Then set vpn_loglevel to 0. It will only output fatal errors to syslog.log The value can be 0 to 9. Pick your favourable. Default in Merlin is 3.

Few convenient choices of a more capable syslog on Asuswrt/Merlin. I'm using syslog-ng from Entware at the moment.

 

[Deleted member 27741]

I have done that as I previously stated and it does not affect the amount of data actually logged to the syslog. Have you confirmed that setting vpn_loglevel to 0 actually works? If it does work for you, let me know what I am doing wrong. Setting vpn_loglevel to 0 does not change the amount openvpn writes to my log.

 

[kvic]

Try adding "verb 0" to the custom config window of your openvpn server page. See if this way works for u.

 

[Deleted member 27741]

That works, thanks!

I settled at verb 1, this still logs a connection but it writes 3 lines instead of 16 with my configuration- nice.

 

[john9527]

@000111 - By chance are you also running a VPN client on the router?

 

[Deleted member 27741]

Hello john! No sir, no VPN client.

vpn_loglevel in nvram was set to 0 (and still is), that doesn't seem to do anything while the verb setting in custom configuration works.

 

[john9527]

Hmmm....just tested here on both client and server and the vpn_loglevel setting is picked up correctly.

A couple of notes:
vpn_loglevel is common to both client and server
if you have a 'verb' statement in the custom config section it will override the the vpn_loglevel setting (you'll end up with 2 verb statements, but the last is the custom config).

If you'd like to investigate further...look at the output of the following

cat /etc/openvpn/server1/config.ovpn

in the first 'Automatically generated' section should be a verb statement based on the value of vpn_loglevel

if you added a verb statement, it will be in the 'Custom Configuration' section

 

[kvic]

Maybe openvpn was not manually restarted after changing vpn_loglevel

Repeated entries in config.opvn are non-issue. The last instance always prevails.

 

[Deleted member 27741]

Not sure what is going on with vpn_loglevel on my router! I am sticking with verb 1 in custom config.