pfSense openvpn connection suddenly down

[joe_g 0]

Hi,

Since a day my pfSense connection suddenly won't work anymore without any real reason (nothing has changed in my setup).

 

In Status / OpenVPN: Client UDP has status "down"

 

The logs say:

 

Nov 26 10:13:36 openvpn 16488 Server poll timeout, restarting

Nov 26 10:13:36 openvpn 16488 SIGUSR1[soft,server_poll] received, process restarting

Nov 26 10:13:36 openvpn 16488 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

Nov 26 10:13:36 openvpn 16488 Socket Buffers: R=[42080->42080] S=[57344->57344]

Nov 26 10:13:36 openvpn 16488 UDPv4 link local (bound): [AF_INET]192.168.1.73

Nov 26 10:13:36 openvpn 16488 UDPv4 link remote: [AF_INET]xxx.xxx.xxx.xxx:1194

Nov 26 10:13:38 openvpn 16488 MANAGEMENT: Client connected from /var/etc/openvpn/client1.sock

Nov 26 10:13:38 openvpn 16488 MANAGEMENT: CMD 'state 1'

Nov 26 10:13:38 openvpn 16488 MANAGEMENT: Client disconnected

Nov 26 10:13:41 openvpn 16488 MANAGEMENT: Client connected from /var/etc/openvpn/client1.sock

Nov 26 10:13:41 openvpn 16488 MANAGEMENT: CMD 'state 1'

Nov 26 10:13:41 openvpn 16488 MANAGEMENT: Client disconnected

 

If anyone has an idea how to troubleshoot this, I'd be most thankful

 

 

[cr00 1]

I got the same problem since 4 o'clock this morning.

Before today I did not have any problems with the pfsense-connection to airvpn.

 

Nov 26 10:49:02    openvpn    20079    MANAGEMENT: Client disconnected
Nov 26 10:49:02    openvpn    20079    MANAGEMENT: CMD 'status 2'
Nov 26 10:49:02    openvpn    20079    MANAGEMENT: CMD 'state 1'
Nov 26 10:49:02    openvpn    20079    MANAGEMENT: Client connected from /var/etc/openvpn/client2.sock
Nov 26 10:44:36    openvpn    20079    Initialization Sequence Completed

[..]

 

I Would be thankful too for any idea on this issue

[joe_g 0]

..and then, after a couple of hours it works again magically

 

I guess pfSense just keep trying to connect until it works with different servers..?

[cr00 1]

..and then, after a couple of hours it works again magically

 

I guess pfSense just keep trying to connect until it works with different servers..?

 

everything is fine now here too... magic(o)

[pfSense_fan 181]

I am also getting this and my logs are flooded with the same message. This is new, it has never been in my logs before.

 

I can still connect and seemingly use the vpn but it has frequent disconnects and my speeds are much lower than normal.

 

I've tried changing servers to no avail.

 

Nov 27 21:09:11 openvpn 32834 MANAGEMENT: Client connected from /var/etc/openvpn/client1.sock

Nov 27 21:09:06 openvpn 32834 MANAGEMENT: Client disconnected

Nov 27 21:09:06 openvpn 32834 MANAGEMENT: CMD 'status 2'

Nov 27 21:09:06 openvpn 32834 MANAGEMENT: CMD 'state 1'

Nov 27 21:09:06 openvpn 32834 MANAGEMENT: Client connected from /var/etc/openvpn/client1.sock

Nov 27 21:09:01 openvpn 32834 MANAGEMENT: Client disconnected

Nov 27 21:09:01 openvpn 32834 MANAGEMENT: CMD 'status 2'

Nov 27 21:09:01 openvpn 32834 MANAGEMENT: CMD 'state 1'

Nov 27 21:09:01 openvpn 32834 MANAGEMENT: Client connected from /var/etc/openvpn/client1.sock

Nov 27 21:08:51 openvpn 32834 MANAGEMENT: Client disconnected

Nov 27 21:08:51 openvpn 32834 MANAGEMENT: CMD 'status 2'

Nov 27 21:08:51 openvpn 32834 MANAGEMENT: CMD 'state 1'

Nov 27 21:08:51 openvpn 32834 MANAGEMENT: Client connected from /var/etc/openvpn/client1.sock

Nov 27 21:08:47 openvpn 32834 MANAGEMENT: Client disconnected

Nov 27 21:08:47 openvpn 32834 MANAGEMENT: CMD 'status 2'

Nov 27 21:08:47 openvpn 32834 MANAGEMENT: CMD 'state 1'

Nov 27 21:08:47 openvpn 32834 MANAGEMENT: Client connected from /var/etc/openvpn/client1.sock

Nov 27 21:08:45 openvpn 32834 Initialization Sequence Completed

 

 

I've been searching the web for a while now trying to pinpoint a cause, not finding anything helpful.

Staff, any insight what this may be and a resolution?

[zhang888 1066]

This is strictly a pfSense behavior, and it is caused by the main GUI querying the OpenVPN sockets regarding their status,

either from the main dashboard or from the status page. This is an alternative way instead of polling ifconfig directly.

You can reduce your verbosity level to a lower level like 3 or 2, if you want this not to be printed in the general logs.

The default is 4 and it includes these messages.

This might look confusing since it says "Connected" and "Disconnected", but it has nothing to do with the actual tunnel.

You can verify that in your status dashboard, or in the client area. This is just the way OpenVPN logs *nix sockets read/write.

[go558a83nk 362]

I've always had that management info in my openvpn logs in pfense.

[pfSense_fan 181]

I've never had it until yesterday when I was having connection issues. I could only get 2Mbps and was disconnecting frequently, so i checked my logs. Tried a number of servers, all the same. I did a web search and one of the top hits was this post. Seems odd though that a few of us had the same "issue" in such a small window.

 

It went back to normal late at night, but right now its back at 2Mbps. I'm going to try some things to see if I am throttled.

[zhang888 1066]

I've never had it until yesterday when I was having connection issues. I could only get 2Mbps and was disconnecting frequently, so i checked my logs. Tried a number of servers, all the same. I did a web search and one of the top hits was this post. Seems odd though that a few of us had the same "issue" in such a small window.

 

It went back to normal late at night, but right now its back at 2Mbps. I'm going to try some things to see if I am throttled.

 

The verbosity level changed somewhere in 2.2 or 2.3, what changed in 2.3.2 for sure is that the new dashboard now

refreshes itself more frequently, so it might be one of the reasons for you to see these entries.

Probably you never paid attention before to the management lines?

I actually don't believe that the issues of joe_g, cr00 and yours are related.

 

The only common thing between random disconnects and slow speeds is the frustration it causes.

 

Also, I just found a thread on pfSense forums where jimp confirmed that the management logs can

be ignored:

https://forum.pfsense.org/index.php?topic=84594.0