Opened 4 years ago

Closed 2 years ago

#37 closed Bug / Defect (worksforme)

Management Console inaccurate state information

Reported by: samuli Owned by:
Priority: major Milestone:
Component: Management Version: 2.1.0 / 2.1.1
Severity: Not set (if unsure, select this one) Keywords:
Cc:

Description

I am enabling the management telnet console. Sometimes when I connect and type state it reports back "WAITING" when actually the VPN is connected and can even be pinged over. It seems that the management console is out of sync with the actual VPN and giving inaccurate state information. A restart of the vpn fixes things, but it happens against some time later.

# openvpn --version
OpenVPN 2.1_rc11 i486-pc-linux-gnu [SSL] [LZO2] [EPOLL] [PKCS11] built on Sep 18 2008
Developed by James Yonan
Copyright (C) 2002-2008 Telethra, Inc. <sales@…>

## Certificate configuration
ca /etc/openvpn/ca.crt
cert /etc/openvpn/client.crt
key /etc/openvpn/client.key
dh client-dh2048.pem

ns-cert-type server
tls-remote "/C=AU/ST=QLD/L=Brisbane/O=XYZ/CN=client2/emailAddress=me@…"
tls-client

## Connections
remote XXX.domain.org 12103
port 12001

## We set up the two end points
ifconfig 172.1.103.2 172.1.103.1

## This script does stuff when the vpn comes up (mainly sets up rip)
up "/etc/openvpn/vpn_up.py 12103 12001"
script-security 2

dev tun1
proto udp
resolv-retry infinite
float
persist-tun
persist-key
cipher BF-CBC
comp-lzo
keepalive 5 30
verb 0

# Avoid black hole routers
tun-mtu 1500
fragment 1400
mssfix

# Management interface
management localhost 2001

Change History (2)

comment:1 Changed 4 years ago by samuli

Originally reported to SF.net bug tracker by Michael Cohen (username: scudette).

comment:2 Changed 2 years ago by dazo

  • Resolution set to worksforme
  • Status changed from new to closed

We have not had any reports on the newer 2.1 and 2.2 releases with this issue. If it re-appears again, feel free to reopen this ticket with more up-to-date info.

Note: See TracTickets for help on using tickets.