[OpenVPN home] [Date Prev] [Date Index] [Date Next]
[OpenVPN mailing lists] [Thread Prev] [Thread Index] [Thread Next]
Google
 
Web openvpn.net

Re: [Openvpn-users] Error message: SIGUSR1(soft, connnection-reset) received process restarting


  • Subject: Re: [Openvpn-users] Error message: SIGUSR1(soft, connnection-reset) received process restarting
  • From: Andrew Guenther <andrew@xxxxxxxxxxxxxxxx>
  • Date: Thu, 27 Sep 2007 20:34:49 -0400


Andrew Guenther
ACE Technology Group
610 640 4223 x2

On Sep 25, 2007, at 4:59 PM, "Jim McCleneghen" <mcclenjim@xxxxxxxxxxx>  
wrote:

> I'm trying to connect in a simple, one client mode from within a  
> customer's premises.  OpenVPN worked fine for two years and then all  
> of a sudden last week I could not connect.
>
> After many attempts I'm able to connect to the openvpn server, but I  
> get the above repeating error.  I see a few posts that reference the  
> same error, with some responses about what causes it; but no  
> responses on how to fix.  Can anyone help?
>
> My Server, Config and Log files are below.
>
> Appreciate any help,
>
> JimM
>
> Server
>
> Maintain a record of client <-> virtual IP address
> # associations in this file.  If OpenVPN goes down or
> # is restarted, reconnecting clients can be assigned
> # the same virtual IP address from the pool that was
> # previously assigned.
> ifconfig-pool-persist ipp.txt
>
> # Configure server mode for ethernet bridging.
> # You must first use your OS's bridging capability
> # to bridge the TAP interface with the ethernet
> # NIC interface.  Then you must manually set the
> # IP/netmask on the bridge interface, here we
> # assume 10.8.0.4/255.255.255.0.  Finally we
> # must set aside an IP range in this subnet
> # (start=10.8.0.50 end=10.8.0.100) to allocate
> # to connecting clients.  Leave this line commented
> # out unless you are ethernet bridging.
> ;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100
>
> # Push routes to the client to allow it
> # to reach other private subnets behind
> # the server.  Remember that these
> # private subnets will also need
> # to know to route the OpenVPN client
> # address pool (10.8.0.0/255.255.255.0)
> # back to the OpenVPN server.
> ;push "route 192.168.10.0 255.255.255.0"
> ;push "route 192.168.20.0 255.255.255.0"
>
> # To assign specific IP addresses to specific
> # clients or if a connecting client has a private
> # subnet behind it that should also have VPN access,
> # use the subdirectory "ccd" for client-specific
> # configuration files (see man page for more info).
>
> # EXAMPLE: Suppose the client
> # having the certificate common name "Thelonious"
> # also has a small subnet behind his connecting
> # machine, such as 192.168.40.128/255.255.255.248.
> # First, uncomment out these lines:
> ;client-config-dir ccd
> ;route 192.168.40.128 255.255.255.248
> # Then create a file ccd/Thelonious with this line:
> #   iroute 192.168.40.128 255.255.255.248
> # This will allow Thelonious' private subnet to
> # access the VPN.  This example will only work
> # if you are routing, not bridging, i.e. you are
> # using "dev tun" and "server" directives.
>
> # EXAMPLE: Suppose you want to give
> # Thelonious a fixed VPN IP address of 10.9.0.1.
> # First uncomment out these lines:
> ;client-config-dir ccd
> ;route 10.9.0.0 255.255.255.252
> # Then add this line to ccd/Thelonious:
> #   ifconfig-push 10.9.0.1 10.9.0.2
>
> # Suppose that you want to enable different
> # firewall access policies for different groups
> # of clients.  There are two methods:
> # (1) Run multiple OpenVPN daemons, one for each
> #     group, and firewall the TUN/TAP interface
> #     for each group/daemon appropriately.
> # (2) (Advanced) Create a script to dynamically
> #     modify the firewall in response to access
> #     from different clients.  See man
> #     page for more info on learn-address script.
> ;learn-address ./script
>
> # If enabled, this directive will configure
> # all clients to redirect their default
> # network gateway through the VPN, causing
> # all IP traffic such as web browsing and
> # and DNS lookups to go through the VPN
> # (The OpenVPN server machine may need to NAT
> # the TUN/TAP interface to the internet in
> # order for this to work properly).
> # CAVEAT: May break client's network config if
> # client's local DHCP server packets get routed
> # through the tunnel.  Solution: make sure
> # client's local DHCP server is reachable via
> # a more specific route than the default route
> # of 0.0.0.0/0.0.0.0.
> ;push "redirect-gateway"
>
> # Certain Windows-specific network settings
> # can be pushed to clients, such as DNS
> # or WINS server addresses.  CAVEAT:
> # http://openvpn.net/faq.html#dhcpcaveats
> ;push "dhcp-option DNS 10.8.0.1"
> ;push "dhcp-option WINS 10.8.0.1"
>
> # Uncomment this directive to allow different
> # clients to be able to "see" each other.
> # By default, clients will only see the server.
> # To force clients to only see the server, you
> # will also need to appropriately firewall the
> # server's TUN/TAP interface.
> ;client-to-client
>
> # Uncomment this directive if multiple clients
> # might connect with the same certificate/key
> # files or common names.  This is recommended
> # only for testing purposes.  For production use,
> # each client should have its own certificate/key
> # pair.
> #
> # IF YOU HAVE NOT GENERATED INDIVIDUAL
> # CERTIFICATE/KEY PAIRS FOR EACH CLIENT,
> # EACH HAVING ITS OWN UNIQUE "COMMON NAME",
> # UNCOMMENT THIS LINE OUT.
> ;duplicate-cn
>
> # The keepalive directive causes ping-like
> # messages to be sent back and forth over
> # the link so that each side knows when
> # the other side has gone down.
> # Ping every 10 seconds, assume that remote
> # peer is down if no ping received during
> # a 120 second time period.
> keepalive 10 120
>
> # For extra security beyond that provided
> # by SSL/TLS, create an "HMAC firewall"
> # to help block DoS attacks and UDP port flooding.
> #
> # Generate with:
> #   openvpn --genkey --secret ta.key
> #
> # The server and each client must have
> # a copy of this key.
> # The second parameter should be '0'
> # on the server and '1' on the clients.
> tls-auth ta.key 0 # This file is secret
>
> # Select a cryptographic cipher.
> # This config item must be copied to
> # the client config file as well.
> ;cipher BF-CBC        # Blowfish (default)
> cipher AES-256-CBC   # AES
> ;cipher DES-EDE3-CBC  # Triple-DES
>
> # Enable compression on the VPN link.
> # If you enable it here, you must also
> # enable it in the client config file.
> comp-lzo
>
> # The maximum number of concurrently connected
> # clients we want to allow.
> ;max-clients 100
>
> # It's a good idea to reduce the OpenVPN
> # daemon's privileges after initialization.
> #
> # You can uncomment this out on
> # non-Windows systems.
> ;user nobody
> ;group nobody
>
> # The persist options will try to avoid
> # accessing certain resources on restart
> # that may no longer be accessible because
> # of the privilege downgrade.
> persist-key
> persist-tun
>
> # Output a short status file showing
> # current connections, truncated
> # and rewritten every minute.
> status openvpn-status.log
>
> # By default, log messages will go to the syslog (or
> # on Windows, if running as a service, they will go to
> # the "\Program Files\OpenVPN\log" directory).
> # Use log or log-append to override this default.
> # "log" will truncate the log file on OpenVPN startup,
> # while "log-append" will append to it.  Use one
> # or the other (but not both).
> ;log         openvpn.log
> ;log-append  openvpn.log
>
> # Set the appropriate level of log
> # file verbosity.
> #
> # 0 is silent, except for fatal errors
> # 4 is reasonable for general usage
> # 5 and 6 can help to debug connection problems
> # 9 is extremely verbose
> verb 3
>
> # Silence repeating messages.  At most 20
> # sequential messages of the same message
> # category will be output to the log.
> mute 20
>
> Client:
>
> # Specify that we are a client and that we
> # will be pulling certain config file directives
> # from the server.
> client
>
> # Use the same setting as you are using on
> # the server.
> # On most systems, the VPN will not function
> # unless you partially or fully disable
> # the firewall for the TUN/TAP interface.
> ;dev tap
> dev tun
>
> # Windows needs the TAP-Win32 adapter name
> # from the Network Connections panel
> # if you have more than one.  On XP SP2,
> # you may need to disable the firewall
> # for the TAP adapter.
> dev-node TAP-Win32-tcp
>
> # Are we connecting to a TCP or
> # UDP server?  Use the same setting as
> # on the server.
> port 443
> proto tcp
> ;proto udp
>
> # The hostname/IP and port of the server.
> # You can have multiple remote entries
> # to load balance between the servers.
> remote seikan.dcsanswires.com
> ;remote seikanmd.dcsanswires.com
> ;remote seikanca.dcsanswires.com
> ;remote my-server-2 1194
>
> # Choose a random host from the remote
> # list for load-balancing.  Otherwise
> # try hosts in the order specified.
> ;remote-random
>
> # Keep trying indefinitely to resolve the
> # host name of the OpenVPN server.  Very useful
> # on machines which are not permanently connected
> # to the internet such as laptops.
> resolv-retry infinite
>
> # Most clients don't need to bind to
> # a specific local port number.
> # nobind
>
> # Downgrade privileges after initialization (non-Windows
>
> only)
> ;user nobody
> ;group nobody
>
> # Try to preserve some state across restarts.
> persist-key
> persist-tun
>
> # If you are connecting through an
> # HTTP proxy to reach the actual OpenVPN
> # server, put the proxy server/IP and
> # port number here.  See the man page
> # if your proxy server requires
> # authentication.
> ;http-proxy-retry # retry on connection failures
> http-proxy 10.244.2.18 8080
>
> # Wireless networks often produce a lot
> # of duplicate packets.  Set this flag
> # to silence duplicate packet warnings.
> ;mute-replay-warnings
>
> # SSL/TLS parms.
> # See the server config file for more
> # description.  It's best to use
> # a separate .crt/.key file pair
> # for each client.  A single ca
> # file can be used for all clients.
> ca ca.crt
> cert jpm.crt
> key jpm.key
>
> # Verify server certificate by checking
> # that the certicate has the nsCertType
> # field set to "server".  This is an
> # important precaution to protect against
> # a potential attack discussed here:
> #  http://openvpn.net/howto.html#mitm
> #
> # To use this feature, you will need to generate
> # your server certificates with the nsCertType
> # field set to "server".  The build-key-server
> # script in the easy-rsa folder will do this.
> ns-cert-type server
>
> # If a tls-auth key is used on the server
> # then every client must also have the key.
> tls-auth ta.key 1
>
> # Select a cryptographic cipher.
> # If the cipher option is used on the server
> # then you must also specify it here.
> cipher AES-256-CBC #AES
>
> # Enable compression on the VPN link.
> # Don't enable this unless it is also
> # enabled in the server config file.
> comp-lzo
>
> # Set log file verbosity.
> verb 7
>
> # Silence repeating messages
> mute 20
>
> Log File:
>
> Tue Sep 25 15:08:59 2007 us=877592 Current Parameter Settings:
> Tue Sep 25 15:08:59 2007 us=877636   config = 'jpm.ovpn'
> Tue Sep 25 15:08:59 2007 us=877645   mode = 0
> Tue Sep 25 15:08:59 2007 us=877654   show_ciphers = DISABLED
> Tue Sep 25 15:08:59 2007 us=877662   show_digests = DISABLED
> Tue Sep 25 15:08:59 2007 us=877670   show_engines = DISABLED
> Tue Sep 25 15:08:59 2007 us=877678   genkey = DISABLED
> Tue Sep 25 15:08:59 2007 us=877687   key_pass_file = '[UNDEF]'
> Tue Sep 25 15:08:59 2007 us=877696   show_tls_ciphers = DISABLED
> Tue Sep 25 15:08:59 2007 us=877704   proto = 2
> Tue Sep 25 15:08:59 2007 us=877713   local = '[UNDEF]'
> Tue Sep 25 15:08:59 2007 us=877723   remote_list[0] =  
> {'seikan.dcsanswires.com', 443}
> Tue Sep 25 15:08:59 2007 us=877731   remote_random = DISABLED
> Tue Sep 25 15:08:59 2007 us=877740   local_port = 443
> Tue Sep 25 15:08:59 2007 us=877748   remote_port = 443
> Tue Sep 25 15:08:59 2007 us=877757   remote_float = DISABLED
> Tue Sep 25 15:08:59 2007 us=877765   ipchange = '[UNDEF]'
> Tue Sep 25 15:08:59 2007 us=877774   bind_local = ENABLED
> Tue Sep 25 15:08:59 2007 us=877782   dev = 'tun'
> Tue Sep 25 15:08:59 2007 us=877790   dev_type = '[UNDEF]'
> Tue Sep 25 15:08:59 2007 us=877798 NOTE: --mute triggered...
> Tue Sep 25 15:08:59 2007 us=877815 178 variation(s) on previous 20  
> message(s) suppressed by --mute
> Tue Sep 25 15:08:59 2007 us=877828 OpenVPN 2.0.9 Win32-MinGW [SSL]  
> [LZO] built on Oct  1 2006
> Tue Sep 25 15:08:59 2007 us=883918 Control Channel Authentication:  
> using 'ta.key' as a OpenVPN static key file
> Tue Sep 25 15:08:59 2007 us=883947 Outgoing Control Channel  
> Authentication: Using 160 bit message hash 'SHA1' for HMAC  
> authentication
> Tue Sep 25 15:08:59 2007 us=883962 Outgoing Control Channel  
> Authentication: HMAC KEY: f7f8426b d1fb1068 167fc03a 4360b886 47572af1
> Tue Sep 25 15:08:59 2007 us=883974 Incoming Control Channel  
> Authentication: Using 160 bit message hash 'SHA1' for HMAC  
> authentication
> Tue Sep 25 15:08:59 2007 us=883988 Incoming Control Channel  
> Authentication: HMAC KEY: 9f3eaf7c 62112148 b296c252 80e86605 4749a884
> Tue Sep 25 15:08:59 2007 us=884026 LZO compression initialized
> Tue Sep 25 15:08:59 2007 us=884042 MTU DYNAMIC mtu=0, flags=1, 0 ->  
> 168
> Tue Sep 25 15:08:59 2007 us=884054 PID packet_id_init  
> seq_backtrack=0 time_backtrack=0
> Tue Sep 25 15:08:59 2007 us=884106 PID packet_id_init  
> seq_backtrack=0 time_backtrack=0
> Tue Sep 25 15:08:59 2007 us=884117 PID packet_id_init  
> seq_backtrack=0 time_backtrack=0
> Tue Sep 25 15:08:59 2007 us=884162 PID packet_id_init  
> seq_backtrack=0 time_backtrack=0
> Tue Sep 25 15:08:59 2007 us=884180 Control Channel MTU parms [ L: 
> 1560 D:168 EF:68 EB:0 ET:0 EL:0 ]
> Tue Sep 25 15:08:59 2007 us=884207 MTU DYNAMIC mtu=1450, flags=2,  
> 1560 -> 1450
> Tue Sep 25 15:08:59 2007 us=884218 REMOTE_LIST len=1 current=0
> Tue Sep 25 15:08:59 2007 us=884226 [0] seikan.dcsanswires.com:443
> Tue Sep 25 15:08:59 2007 us=888161 RESOLVE_REMOTE flags=0x0001  
> phase=1 rrs=0 sig=-1 status=1
> Tue Sep 25 15:08:59 2007 us=888179 Data Channel MTU parms [ L:1560 D: 
> 1450 EF:60 EB:135 ET:0 EL:0 AF:3/1 ]
> Tue Sep 25 15:08:59 2007 us=888210 Local Options String: 'V4,dev- 
> type tun,link-mtu 1560,tun-mtu 1500,proto TCPv4_CLIENT,comp- 
> lzo,keydir 1,cipher AES-256-CBC,auth SHA1,keysize 256,tls-auth,key- 
> method 2,tls-client'
> Tue Sep 25 15:08:59 2007 us=888222 Expected Remote Options String:  
> 'V4,dev-type tun,link-mtu 1560,tun-mtu 1500,proto TCPv4_SERVER,comp- 
> lzo,keydir 0,cipher AES-256-CBC,auth SHA1,keysize 256,tls-auth,key- 
> method 2,tls-server'
> Tue Sep 25 15:08:59 2007 us=888298 Local Options hash (VER=V4):  
> '2f2c6498'
> Tue Sep 25 15:08:59 2007 us=888312 Expected Remote Options hash  
> (VER=V4): '9915e4a2'
> Tue Sep 25 15:08:59 2007 us=888351 Attempting to establish TCP  
> connection with 10.244.2.18:8080
> Tue Sep 25 15:08:59 2007 us=958343 TCP connection established with 10.244.2.18 
> :8080
> Tue Sep 25 15:08:59 2007 us=958370 Send to HTTP proxy: 'CONNECT  
> seikan.dcsanswires.com:443 HTTP/1.0'
> Tue Sep 25 15:09:05 2007 us=810722 HTTP proxy returned: 'HTTP/1.1  
> 200 Connection established'
> Tue Sep 25 15:09:07 2007 us=811881 Socket Buffers: R=[8192->8192] S= 
> [8192->8192]
> Tue Sep 25 15:09:07 2007 us=811970 TCPv4_CLIENT link local: [undef]
> Tue Sep 25 15:09:07 2007 us=811984 TCPv4_CLIENT link remote: 10.244.2.18 
> :8080
> Tue Sep 25 15:09:07 2007 us=911583 TCPv4_CLIENT WRITE [42] to 10.244.2.18 
> :8080: P_CONTROL_HARD_RESET_CLIENT_V2 kid=0 pid=[ #1 ] [ ] pid=0  
> DATA len=0
> Tue Sep 25 15:09:07 2007 us=976178 Connection reset, restarting [0]
> Tue Sep 25 15:09:07 2007 us=976277 PID packet_id_free
> Tue Sep 25 15:09:07 2007 us=976470 PID packet_id_free
> Tue Sep 25 15:09:07 2007 us=976518 PID packet_id_free
> Tue Sep 25 15:09:07 2007 us=976554 PID packet_id_free
> Tue Sep 25 15:09:07 2007 us=976647 PID packet_id_free
> Tue Sep 25 15:09:07 2007 us=976666 PID packet_id_free
> Tue Sep 25 15:09:07 2007 us=976681 PID packet_id_free
> Tue Sep 25 15:09:07 2007 us=976697 PID packet_id_free
> Tue Sep 25 15:09:07 2007 us=976717 TCP/UDP: Closing socket
> Tue Sep 25 15:09:07 2007 us=976830 PID packet_id_free
> Tue Sep 25 15:09:07 2007 us=976867 SIGUSR1[soft,connection-reset]  
> received, process restarting
> Tue Sep 25 15:09:07 2007 us=976907 Restart pause, 5 second(s)
>
> _________________________________________________________________
> Discover sweet stuff waiting for you at the Messenger Cafe.  Claim  
> your treat today! http://www.cafemessenger.com/info/info_sweetstuff.html?ocid=TXT_TAGHM_SeptHMtagline2
>
>
> --- 
> ----------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Openvpn-users mailing list
> Openvpn-users@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/openvpn-users


Jim,

Can you confirm that your local http proxy has not changed recently?  
Can you disable any local port 443 filtering and test if you can  
connect then? (make sure you comment out your http proxy line on your  
client).

Also, can you do a telnet test to your server to verify nothing has  
changed on the firewall there? Try "telnet <remote server> <port>"  
from any windows or Linux box at your client side location. If you get  
anything except 'connection refused' you are probably fine on that  
side. This only works because you are running tcp instead on normal udp.

______________________
OpenVPN mailing lists
https://lists.sourceforge.net/lists/listinfo/openvpn-users