Opened 14 years ago
Last modified 14 years ago
#13 closed Bug / Defect
Not using --push on server makes client sending PUSH_REQUEST continuously — at Version 1
Reported by: | David Sommerseth | Owned by: | |
---|---|---|---|
Priority: | critical | Milestone: | beta 2.2 |
Component: | Configuration | Version: | OpenVPN git master branch (Community Ed) |
Severity: | Not set (select this one, unless your'e a OpenVPN developer) | Keywords: | |
Cc: |
Description (last modified by )
Reported to sf.net bug tracker:
http://sourceforge.net/tracker/?func=detail&atid=454719&aid=3009984&group_id=48978
When not using --push on the server side, the client sends new PUSH_REQUESTS which blocks the tunnel being set up properly.
Adding either --tcp-nodelay (even though we're using UDP) or a --push statement resolves this issue.
Confirmed on 2.1.1 and openvpn-testing.git (commit bdd699ccafd4f566e87e3ed127)
Attached config files for reproducing this issue from the openvpn-testing.git source tree.
Change History (3)
Changed 14 years ago by
Attachment: | nopush_server.conf added |
---|
comment:1 Changed 14 years ago by
Description: | modified (diff) |
---|
Note: See
TracTickets for help on using
tickets.
Reproducer: Server side config