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

[Openvpn-users] Unroutable control packet received from ...


  • Subject: [Openvpn-users] Unroutable control packet received from ...
  • From: Javier Sanchez <sjllera@xxxxxx>
  • Date: Mon, 06 Sep 2004 03:28:49 +0200

Hello all,

im confused with an error i have started to get this afternoon on my vpn
connection.

When i start the vpn on the client side i continouslly get the following
errors.

: Unroutable control packet received from 172.16.96.233:5000 (si=3
op=P_ACK_V1)
Sep  6 03:16:49 src@torrejon01 openvpn[29667]: TLS Error: Unroutable
control packet received from 172.16.96.233:5000 (si=3 op=P_CONTROL_V1)
Sep  6 03:16:49 src@torrejon01 openvpn[29667]: TLS Error: Unroutable
control packet received from 172.16.96.233:5000 (si=3 op=P_CONTROL_V1)
Sep  6 03:16:49 src@torrejon01 openvpn[29667]: TLS Error: Unroutable
control packet received from 172.16.96.233:5000 (si=3 op=P_CONTROL_V1)
Sep  6 03:16:49 src@torrejon01 openvpn[29667]: TLS Error: Unroutable
control packet received from 172.16.96.233:5000 (si=3 op=P_CONTROL_V1)
Sep  6 03:16:50 src@torrejon01 openvpn[29667]: TLS Error: Unroutable
control packet received from 172.16.96.233:5000 (si=3 op=P_CONTROL_V1)
Sep  6 03:16:50 src@torrejon01 openvpn[29667]: TLS Error: Unroutable
control packet received from 172.16.96.233:5000 (si=3 op=P_CONTROL_V1)
Sep  6 03:16:50 src@torrejon01 openvpn[29667]: TLS Error: Unroutable
control packet received from 172.16.96.233:5000 (si=3 op=P_CONTROL_V1)
Sep  6 03:16:50 src@torrejon01 openvpn[29667]: TLS Error: Unroutable
control packet received from 172.16.96.233:5000 (si=3 op=P_CONTROL_V1)
Sep  6 03:16:50 src@torrejon01 openvpn[29667]: TLS Error: Unroutable
control packet received from 172.16.96.233:5000 (si=3 op=P_ACK_V1)

Im allready using another vpn with the same characteristics, and it
working fine, there are no network or routing related problems, i can
access the remote gateway with the vpn down with no problems. 

No matter how high i define the debugging i was not able to understood
whats going wrong, any ideas ???

Client and server configs are attached.

TIA
Cheers

Javier Sanchez
sjllera@xxxxxx


#
# Sample OpenVPN configuration file for
# office using SSL/TLS mode and RSA certificates/keys.
#
# '#' or ';' may be used to delimit comments.

# Use a dynamic tun device.
# For Linux 2.2 or non-Linux OSes,
# you may want to use an explicit
# unit number such as "tun1".
# OpenVPN also supports virtual
# ethernet "tap" devices.
dev tun0

# 10.1.0.1 is our local VPN endpoint (office).
# 10.1.0.2 is our remote VPN endpoint (home).
# ifconfig 172.16.104.1 172.16.104.2
ifconfig 172.16.96.169 172.16.96.170
# Our up script will establish routes
# once the VPN is alive.
up ./rutasaw.up

# In SSL/TLS key exchange, Office will
# assume server role and Home
# will assume client role.
tls-server

# Diffie-Hellman Parameters (tls-server only)
dh dh1024.pem

# Certificate Authority file
ca cacert.pem

# Our certificate/public key
cert angelcert.pem

# Our private key
key angelkey.pem

# OpenVPN uses UDP port 5000 by default.
# Each OpenVPN tunnel must use
# a different port number.
# lport or rport can be used
# to denote different ports
# for local and remote.
port 5000

# Downgrade UID and GID to
# "nobody" after initialization
# for extra security.
user nobody
group nogroup

# If you built OpenVPN with
# LZO compression, uncomment
# out the following line.
comp-lzo

# Send a UDP ping to remote once
# every 15 seconds to keep
# stateful firewall connection
# alive.  Uncomment this
# out if you are using a stateful
# firewall.
ping 15

# Uncomment this section for a more reliable detection when a system
# loses its connection.  For example, dial-ups or laptops that
# travel to other locations.
; ping 15
; ping-restart 45
; ping-timer-rem
; persist-tun
; persist-key

# Verbosity level.
# 0 -- quiet except for fatal errors.
# 1 -- mostly quiet, but display non-fatal network errors.
# 3 -- medium output, good for normal operation.
# 9 -- verbose, good for troubleshooting
verb 5
# Sample OpenVPN configuration file for
# home using SSL/TLS mode and RSA certificates/keys.
#
# '#' or ';' may be used to delimit comments.

# Use a dynamic tun device.
# For Linux 2.2 or non-Linux OSes,
# you may want to use an explicit
# unit number such as "tun1".
# OpenVPN also supports virtual
# ethernet "tap" devices.
dev tun1

# Our OpenVPN peer is the office gateway.
remote 172.16.96.233

# 10.1.0.2 is our local VPN endpoint (home).
# 10.1.0.1 is our remote VPN endpoint (office).
# ifconfig 172.16.104.2 172.16.104.1
ifconfig 172.16.96.170 172.16.96.169

# Our up script will establish routes
# once the VPN is alive.
up ./home.up

# In SSL/TLS key exchange, Office will
# assume server role and Home
# will assume client role.
tls-client

# Certificate Authority file
ca cacert.pem

# Our certificate/public key
cert javicert.pem

# Our private key
key javikey.pem

# OpenVPN uses UDP port 5000 by default.
# Each OpenVPN tunnel must use
# a different port number.
# lport or rport can be used
# to denote different ports
# for local and remote.
; port 5000

# Downgrade UID and GID to
# "nobody" after initialization
# for extra security.
user nobody
group nogroup

# If you built OpenVPN with
# LZO compression, uncomment
# out the following line.
comp-lzo

# Send a UDP ping to remote once
# every 15 seconds to keep
# stateful firewall connection
# alive.  Uncomment this
# out if you are using a stateful
# firewall.
ping 15

# Uncomment this section for a more reliable detection when a system
# loses its connection.  For example, dial-ups or laptops that
# travel to other locations.
; ping 15
; ping-restart 45
; ping-timer-rem
; persist-tun
; persist-key

# Verbosity level.
# 0 -- quiet except for fatal errors.
# 1 -- mostly quiet, but display non-fatal network errors.
# 3 -- medium output, good for normal operation.
# 9 -- verbose, good for troubleshooting
verb 4