udp connection suddenly broken



  • Over the past 2 years, my pfsense router box has been running a vpn udp connection and connecting to the Windscribe server. No problem until last night. No UDP client connection. I even changed the Windscribe server hostname and still no connection. What changed? Pfsense software is at the latest version. What happened?

    Jul 30 22:10:05 openvpn 11694 TCP/UDP: Closing socket

    Jul 30 22:10:05 openvpn 11694 SIGUSR1[soft,ping-restart] received, process restarting

    Jul 30 22:10:05 openvpn 11694 Restart pause, 10 second(s)

    Jul 30 22:10:15 openvpn 11694 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.

    Jul 30 22:10:15 openvpn 11694 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

    Jul 30 22:10:15 openvpn 11694 Re-using SSL/TLS context

    Jul 30 22:10:15 openvpn 11694 LZO compression initializing

    Jul 30 22:10:15 openvpn 11694 Control Channel MTU parms [ L:1622 D:1140 EF:110 EB:0 ET:0 EL:3 ]

    Jul 30 22:10:15 openvpn 11694 Data Channel MTU parms [ L:1622 D:1450 EF:122 EB:406 ET:0 EL:3 ]

    Jul 30 22:10:15 openvpn 11694 Local Options String (VER=V4): 'V4,dev-type tun,link-mtu 1602,tun-mtu 1500,proto UDPv4,comp-lzo,keydir 1,cipher AES-256-CBC,auth SHA512,keysize 256,tls-auth,key-method 2,tls-client'

    Jul 30 22:10:15 openvpn 11694 Expected Remote Options String (VER=V4): 'V4,dev-type tun,link-mtu 1602,tun-mtu 1500,proto UDPv4,comp-lzo,keydir 0,cipher AES-256-CBC,auth SHA512,keysize 256,tls-auth,key-method 2,tls-server'

    Jul 30 22:10:15 openvpn 11694 TCP/UDP: Preserving recently used remote address: [AF_INET]207.189.22.2:80

    Jul 30 22:10:15 openvpn 11694 Socket Buffers: R=[42080->42080] S=[57344->57344]

    Jul 30 22:10:15 openvpn 11694 UDPv4 link local (bound): [AF_INET]192.168.1.XX:0

    Jul 30 22:10:15 openvpn 11694 UDPv4 link remote: [AF_INET]207.189.22.2:80

    Jul 30 22:11:15 openvpn 11694 [UNDEF] Inactivity timeout (--ping-restart), restarting

    Jul 30 22:11:15 openvpn 11694 TCP/UDP: Closing socket

    Jul 30 22:11:15 openvpn 11694 SIGUSR1[soft,ping-restart] received, process restarting

    Jul 30 22:11:15 openvpn 11694 Restart pause, 10 second(s)

    Jul 30 22:11:25 openvpn 11694 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.

    Jul 30 22:11:25 openvpn 11694 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

    Jul 30 22:11:25 openvpn 11694 Re-using SSL/TLS context

    Jul 30 22:11:25 openvpn 11694 LZO compression initializing

    Jul 30 22:11:25 openvpn 11694 Control Channel MTU parms [ L:1622 D:1140 EF:110 EB:0 ET:0 EL:3 ]

    Jul 30 22:11:25 openvpn 11694 Data Channel MTU parms [ L:1622 D:1450 EF:122 EB:406 ET:0 EL:3 ]

    Jul 30 22:11:25 openvpn 11694 Local Options String (VER=V4): 'V4,dev-type tun,link-mtu 1602,tun-mtu 1500,proto UDPv4,comp-lzo,keydir 1,cipher AES-256-CBC,auth SHA512,keysize 256,tls-auth,key-method 2,tls-client'

    Jul 30 22:11:25 openvpn 11694 Expected Remote Options String (VER=V4): 'V4,dev-type tun,link-mtu 1602,tun-mtu 1500,proto UDPv4,comp-lzo,keydir 0,cipher AES-256-CBC,auth SHA512,keysize 256,tls-auth,key-method 2,tls-server'

    Jul 30 22:11:25 openvpn 11694 TCP/UDP: Preserving recently used remote address: [AF_INET]207.189.22.2:80

    Jul 30 22:11:25 openvpn 11694 Socket Buffers: R=[42080->42080] S=[57344->57344]

    Jul 30 22:11:25 openvpn 11694 UDPv4 link local (bound): [AF_INET]192.168.1.XXX:0

    Jul 30 22:11:25 openvpn 11694 UDPv4 link remote: [AF_INET]207.189.22.2:80



  • @patrick0525 If you're completely certain that nothing on your end changed, it stands to reason that maybe something on their end did? I'm not familiar with the provider, but have you checked to see whether they have an updated configuration guide? Have you tried connecting to them from a PC instead of the pfSense machine? If they support TCP as well have you tried that? Just a few thoughts for preliminary troubleshooting steps.


 

© Copyright 2002 - 2018 Rubicon Communications, LLC | Privacy Policy