Project

General

Profile

Bug #826

Status > OpenVPN hangs when using TCP w/OpenVPN Int. "any"

Added by Chris Buechler about 9 years ago. Updated over 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
OpenVPN
Target version:
Start date:
08/16/2010
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.0
Affected Architecture:

Description

When using TCP with OpenVPN, even where specifying 'local' to bind to a specific IP, the server binds itself to 127.0.0.1 as well. Then the Status > OpenVPN page hangs because the OpenVPN server is binding to the management port on 127.0.0.1. So the status page actually connects to the OpenVPN server rather than the management interface, which returns nothing to its queries.

Three issues here.
1) If the OpenVPN management interface does not respond, it should give up after several seconds, rather than completely hang up the web interface.
2) When using "any" with TCP, the management interface must use a different port than the one OpenVPN is using.
3) why is the server apparently binding to 127.0.0.1 where it shouldn't be (or is that not actually the issue)

Associated revisions

Revision a8abc4b3 (diff)
Added by Jim Pingle about 9 years ago

End processing when we receive an ERROR line. Part of ticket #826

Revision 19e3d450 (diff)
Added by Ermal Luçi about 9 years ago

Ticket #826. Add timeout of 1 second for all read/write actions performed on the socket. This should fix point 1) on the ticket.

Revision 71ca2cb2 (diff)
Added by Ermal Luçi about 9 years ago

Ticket #826. Convert to unix domain sockets for management interface so we do not have problems when interface is any.

Revision b0140675 (diff)
Added by Ermal Luçi about 9 years ago

Ticket #826. Add more bandage to notice when a reading on socket timeouts.

History

#1 Updated by Jim Pingle about 9 years ago

The binding seems to be correct, but the status connection wasn't being parsed properly.

The status command to the management daemon doesn't work correctly for static key servers, you get back this error:

ERROR: The 'status' command is not supported by the current daemon mode

#2 Updated by Ermal Luçi about 9 years ago

  • Status changed from New to Feedback

#3 Updated by Chris Buechler over 8 years ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF