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

Re: [Openvpn-users] MULTI: bad source address from client [217.164.246.54], packet dropped


  • Subject: Re: [Openvpn-users] MULTI: bad source address from client [217.164.246.54], packet dropped
  • From: "Peter Njiiri" <pnjiiri@xxxxxxxxx>
  • Date: Tue, 17 Jul 2007 09:37:32 +0400

Hi

I've a successful connection between my openVPN server (behind Linux firewall) and a roadwarrior (Windows XP client openVPN client which is NOT serving as a LAN gateway). However I receive the following error on the server when I connect successfully from the roadwarrior:


openvpn[17117]: petehome/217.164.246.54:1089 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication

nowsnme openvpn[17117]: petehome/217.164.246.54:1089 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA

openvpn[17117]: petehome/217.164.246.54:1089 MULTI: bad source address from client [217.164.246.54], packet dropped


 openVPNserver machine <----> gw (Linux firewall) <---->ISP <-------> client machine


10.0.0.10                         10.0.0.254                   80.122.134.2              217.164.256.54



I've enabled the following

1. push route LAN network

2. redirect-gateway

3. push dhcp-options

4. client-to-client


I don't need to create a ccd directory (as I've seen forums relating to this issue). Please note that without enabling the above options, my VPN works without errors, it's only when I want to push all traffic in the tunnel that I get this error. On the client/roadwarrior side I'm able to browse the internal network and use the internal Internet and there are no errors when connecting. iptables and routes have been added to openVPN server and LAN gateway/firewall according to the following on openvpn.net:

1. http://openvpn.net/howto.html#redirect

2. http://openvpn.net/howto.html#dhcp

3. http://openvpn.net/faq.html#ip-forward

4. http://openvpn.net/faq.html#firewall



I also tried connecting a roadwarrior (Linux) to the server and it gave the same error (only with a different IP instead of 217.164.246.54 seen above). Please advice as to what to do next to resolve this error. Thanks for your feedback.


Kind Regards

Peter


my sample server.conf file on the server is below:


# Configure server mode for ethernet bridging.

# You must first use your OS's bridging capability

# to bridge the TAP interface with the ethernet

# NIC interface.  Then you must manually set the

# IP/netmask on the bridge interface, here we

# assume 10.8.0.4/255.255.255.0.  Finally we

# must set aside an IP range in this subnet

# (start=10.8.0.50 end=10.8.0.100) to allocate

# to connecting clients.  Leave this line commented

# out unless you are ethernet bridging.

;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100


# Push routes to the client to allow it

# to reach other private subnets behind

# the server.  Remember that these

# private subnets will also need

# to know to route the OpenVPN client

# address pool (10.8.0.0/255.255.255.0)

# back to the OpenVPN server.

;push "route 192.168.10.0 255.255.255.0"

;push "route 192.168.20.0 255.255.255.0"

push "route 10.0.0.0 255.255.255.0"


# To assign specific IP addresses to specific

# clients or if a connecting client has a private

# subnet behind it that should also have VPN access,

# use the subdirectory "ccd" for client-specific

# configuration files (see man page for more info).


# EXAMPLE: Suppose the client

# having the certificate common name "Thelonious"

# also has a small subnet behind his connecting

# machine, such as 192.168.40.128/255.255.255.248.

# First, uncomment out these lines:

;client-config-dir ccd

;route 192.168.40.128 255.255.255.248

;route 10.0.0.0 255.255.255.0

# Then create a file ccd/Thelonious with this line:

#   iroute 192.168.40.128 255.255.255.248

# This will allow Thelonious' private subnet to

# access the VPN.  This example will only work

# if you are routing, not bridging, i.e. you are

# using "dev tun" and "server" directives.


# EXAMPLE: Suppose you want to give

# Thelonious a fixed VPN IP address of 10.9.0.1.

# First uncomment out these lines:

;client-config-dir ccd

;route 10.9.0.0 255.255.255.252

# Then add this line to ccd/Thelonious:

#   ifconfig-push 10.9.0.1 10.9.0.2


# Suppose that you want to enable different

# firewall access policies for different groups

# of clients.  There are two methods:

# (1) Run multiple OpenVPN daemons, one for each

#     group, and firewall the TUN/TAP interface

#     for each group/daemon appropriately.

# (2) (Advanced) Create a script to dynamically

#     modify the firewall in response to access

#     from different clients.  See man

#     page for more info on learn-address script.

;learn-address ./script


# If enabled, this directive will configure

# all clients to redirect their default

# network gateway through the VPN, causing

# all IP traffic such as web browsing and

# and DNS lookups to go through the VPN

# (The OpenVPN server machine may need to NAT

# the TUN/TAP interface to the internet in

# order for this to work properly).

# CAVEAT: May break client's network config if

# client's local DHCP server packets get routed

# through the tunnel.  Solution: make sure

# client's local DHCP server is reachable via

# a more specific route than the default route

# of 0.0.0.0/0.0.0.0.

;push "redirect-gateway"

push "redirect-gateway"


# Certain Windows-specific network settings

# can be pushed to clients, such as DNS

# or WINS server addresses.  CAVEAT:

# http://openvpn.net/faq.html#dhcpcaveats

;push "dhcp-option DNS 10.8.0.1"

;push "dhcp-option WINS 10.8.0.1"

push "dhcp-option DNS 10.8.0.1"

push "dhcp-option DNS 10.0.0.25"

push "dhcp-option DNS 10.0.0.114"


# Uncomment this directive to allow different

# clients to be able to "see" each other.

# By default, clients will only see the server.

# To force clients to only see the server, you

# will also need to appropriately firewall the

# server's TUN/TAP interface.

client-to-client


# Uncomment this directive if multiple clients

# might connect with the same certificate/key

# files or common names.  This is recommended

# only for testing purposes.  For production use,

# each client should have its own certificate/key

# pair.

#

# IF YOU HAVE NOT GENERATED INDIVIDUAL

# CERTIFICATE/KEY PAIRS FOR EACH CLIENT,

# EACH HAVING ITS OWN UNIQUE "COMMON NAME",

# UNCOMMENT THIS LINE OUT.

;duplicate-cn


# The keepalive directive causes ping-like

# messages to be sent back and forth over

# the link so that each side knows when

# the other side has gone down.

# Ping every 10 seconds, assume that remote

# peer is down if no ping received during

# a 120 second time period.

keepalive 10 120


# For extra security beyond that provided

# by SSL/TLS, create an "HMAC firewall"

# to help block DoS attacks and UDP port flooding.

#

# Generate with:

#   openvpn --genkey --secret ta.key

#

# The server and each client must have

# a copy of this key.

# The second parameter should be '0'

# on the server and '1' on the clients.

tls-auth /etc/openvpn/easy-rsa/keys/ta.key 0 # This file is secret


# Select a cryptographic cipher.

# This config item must be copied to

# the client config file as well.

;cipher BF-CBC        # Blowfish (default)

;cipher AES-128-CBC   # AES

;cipher DES-EDE3-CBC  # Triple-DES


# Enable compression on the VPN link.

# If you enable it here, you must also

# enable it in the client config file.

comp-lzo


# The maximum number of concurrently connected

# clients we want to allow.

;max-clients 100


# It's a good idea to reduce the OpenVPN

# daemon's privileges after initialization.

#

# You can uncomment this out on

# non-Windows systems.

user nobody

group nobody


# The persist options will try to avoid

# accessing certain resources on restart

# that may no longer be accessible because

# of the privilege downgrade.

persist-key

persist-tun


# Output a short status file showing

# current connections, truncated

# and rewritten every minute.

status openvpn-status.log


# By default, log messages will go to the syslog (or

# on Windows, if running as a service, they will go to

# the "\Program Files\OpenVPN\log" directory).

# Use log or log-append to override this default.

# "log" will truncate the log file on OpenVPN startup,

# while "log-append" will append to it.  Use one

# or the other (but not both).

;log         openvpn.log

;log-append  openvpn.log


# Set the appropriate level of log

# file verbosity.

#

# 0 is silent, except for fatal errors

# 4 is reasonable for general usage

# 5 and 6 can help to debug connection problems

# 9 is extremely verbose

verb 3


# Silence repeating messages.  At most 20

# sequential messages of the same message

# category will be output to the log.

;mute 20