Results 1 to 6 of 6
  1. #1
    Newbie
    Join Date
    Sep 2009
    Posts
    1

    Default read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)

    Hi,

    I am looking for some helpfull people, who might be able to help me out in this one...

    I successfully managed to set up an OpenVPN server.

    However, when I try to connect to it from my client with the OpenVPN GUI i get this:

    Sun Sep 06 00:50:50 2009 OpenVPN 2.0.9 Win32-MinGW [SSL] [LZO] built on Oct 1 2006
    Sun Sep 06 00:50:50 2009 IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA. OpenVPN 2.0-beta16 and earlier used 5000 as the default port.
    Sun Sep 06 00:50:50 2009 WARNING: No server certificate verification method has been enabled. See (URL removed due to first post) for more info.
    Sun Sep 06 00:50:50 2009 Control Channel Authentication: using 'ta.key' as a OpenVPN static key file
    Sun Sep 06 00:50:50 2009 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
    Sun Sep 06 00:50:50 2009 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
    Sun Sep 06 00:50:50 2009 LZO compression initialized
    Sun Sep 06 00:50:50 2009 Control Channel MTU parms [ L:1574 D:166 EF:66 EB:0 ET:0 EL:0 ]
    Sun Sep 06 00:50:50 2009 Data Channel MTU parms [ L:1574 D:1450 EF:42 EB:135 ET:32 EL:0 AF:3/1 ]
    Sun Sep 06 00:50:50 2009 Local Options hash (VER=V4): '17a243ba'
    Sun Sep 06 00:50:50 2009 Expected Remote Options hash (VER=V4): '350246c7'
    Sun Sep 06 00:50:50 2009 UDPv4 link local: [undef]
    Sun Sep 06 00:50:50 2009 UDPv4 link remote: 200.90.90.200:1194
    Sun Sep 06 00:50:50 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
    Sun Sep 06 00:50:52 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
    Sun Sep 06 00:50:54 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
    Sun Sep 06 00:50:55 2009 TCP/UDP: Closing socket
    Sun Sep 06 00:50:55 2009 SIGTERM[hard,] received, process exiting


    I have absolutely no clue of what to do...

    I have tried to add some rules for the 1194 port via iptables:

    -A ufw-user-input -p tcp -m tcp --dport 1194 -j ACCEPT
    -A ufw-user-input -p udp -m udp --dport 1194 -j ACCEPT

    With no success...

    I have HyperVM installed on my server, and by doing a port-stat, it comes back with a "connection timed out" message for port 1194.

    If anyone has any ideas, they would be much appreciated - I'm pretty lost here at the moment...

    Sincerely,

    Martin.

  2. #2
    Newbie
    Join Date
    Oct 2009
    Posts
    1

    Default TCP or UDP tunnel?

    It could be that your server is offering OpenVPN over TCP, and the client is configured to use OpenVPN over UDP.

    For example, Mikrotik units only support OpenVPN server over TCP, which produced also the same client error message when I tried to use the good-old UDP transport.

    ---

    Another issue is that you might need to (user plane) accept and forward traffic between the TUN or TAP interface (the VPN traffic) and the internal partner network. But this is after the UDP/TCP OpenVPN link first connects ok.

  3. #3
    Untangler
    Join Date
    Mar 2009
    Posts
    45

    Default

    Looks like your firewall block incoming traffic to port 1194.

    Or

    The port forwarding to port 1194 to your untangle with openVPN server was blocked.

  4. #4
    Untangler
    Join Date
    Apr 2009
    Posts
    40

    Default

    Just create a Portfowarding.... UDP 1194

    Setup -> network -> portfowarding

  5. #5
    Untangle Ninja raditude's Avatar
    Join Date
    Jan 2009
    Location
    Eugene, OR
    Posts
    1,143

    Default

    IF your running openvpn on UT, you dont have to do anything in port forwards, iptables, or the firewall in order to gain access. It sounds to me like the OP is not running UT.

  6. #6
    Untangle Ninja mrunkel's Avatar
    Join Date
    Jul 2008
    Posts
    3,040

    Default

    Quote Originally Posted by raditude View Post
    IF your running openvpn on UT, you dont have to do anything in port forwards, iptables, or the firewall in order to gain access. It sounds to me like the OP is not running UT.
    ditto. none of any of the other advice makes sense on an Untangle running OpenVPN.
    m.


    Big Frickin Disclaimer:
    While I'm pretty sure, I can't guarantee that I know what I'm doing. There might be a better way to do this, and this way might actually suck. Make sure you understand the implications of what you're doing before trying to follow these directions.

    It often helps troubleshooting if you have a good network map. Look here if you want my advice on how to draw one.
    Attention: Support and help on the Untangle Forums is provided by volunteers and community members like yourself.
    If you need Untangle support please call or email support@untangle.com

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

SEO by vBSEO 3.6.0 PL2