from client [10.8.0.6], packet dropped I suspect openvpn did not deal alright with the IP address change as nothing else happened (the gateway is connected via ethernet to a cable

OpenVPN/Routing - Secure Computing Wiki MULTI: bad source address from client [IP ADDRESS], packet dropped IP ADDRESS in that case would be the machine on client LAN which tried to talk through vpn, because openVPN has no clue what that address is. Once you give it the iroute statement, that changes. VPN: "MULTI: bad source address from client , packet May 10 18:59:08 central openvpnserver[6667]: /89.204.130.194:38953 MULTI: bad source address from client [10.148.20.194], packet dropped HOWTO setup OpenVPN server and client configuration files Introduction OpenVPN allows client computers to tunnel into a server over a single UDP or TCP port securely. This HOWTO article is a step-by-step guide that explains how to create the server and client OpenVPN configuration files that makes this possible.

Oct 19, 2008

Setup: I have the an openvpn client/server setup (config files at bottom), and I get the infamous MULTI: bad source address from client [192.168.x.x], packet dropped message at server. The server has a public IP address, while the client is behind NAT. Shortcomings of previously proposed solutions: The client-config-dir defined in the server config is currently empty. 317-qmulti-bad-source-address-from-client - OpenVPN Jan 30, 2014

They look like this: MULTI: bad source address from client [LAN_IP], packet dropped. Also, "What is iroute?" 3 There is a file, client.csr, generated by easy-rsa with the build-key command that is …

Jan 30, 2014 OpenVPN - MULTI: bad source address from client