nathansklero Hi to all and first of all thank you for your time. I'd like to share my configuration to receive your opinions and ideas about it, specially about the persistance of this : MULTI: bad source address from client [::], packet dropped (from client1 and randomly for others) I have 2 vps and 3 win7 machine : vps1 is the server and vps2 and client1 client2 client3 the clients, I want to share normal service via vpn on the 10.8.0.0/24 subnet vps n1 has public ip 172.xxx.xxx.xxx this is the vpn server with 10.8.0.1/24 vps n2 has public ip 90.xxx.xxx.xxx this is one client with ip 10.8.0.2/24 client 1 public ip (dinamic adsl) 72.xxx client 1 lan ip 192.168.1.x/24 client1 vpn ip 10.8.0.40 and in a different office: client 2 public ip (dinamic adsl) 52.xxx client 2 lan ip 192.168.1.y/24 client 2 vp 10.8.0.41 client 3 public ip (dinamic adsl) 52.xxx client 3 lan ip 192.168.1.z/24 client 3 vpn ip 10.8.0.42 port 1194 proto udp dev tun0 auth-nocache askpass parolach.pass ca ca.crt cert server.crt key server.key dh dh.pem topology subnet server 10.8.0.0 255.255.255.0 client-to-client #route 192.168.0.0 255.255.255.0 #route 172.xxx.xxx.xxx 255.255.255.0 #route 90.xxx.xxx.xxx 255.255.255.0 #push "route 172.xxx.xxx.xxx 255.255.255.0" #push "route 192.168.0.0 255.255.255.0" #push "route 90.xxx.xxx.xxx 255.255.255.0" #client-config-dir ccd #duplicate-cn ifconfig-pool-persist ipp.txt push "dhcp-option DNS 8.8.8.8" push "dhcp-option DNS 8.8.4.4" keepalive 10 120 tls-auth ta.key 0 cipher AES-256-CBC comp-lzo user nobody group nobody persist-key persist-tun status openvpn-status.log verb 4 log /var/log/openvpn.log log-append /var/log/openvpn.log explicit-exit-notify 1 client dev tun proto udp remote 172.xxx.xxx.xxx 1194 cipher AES-256-CBC resolv-retry infinite nobind persist-key persist-tun mute-replay-warnings askpass parolach.pass ca ca.crt cert uservps.crt key uservps.key tls-auth ta.key 1 remote-cert-tls server comp-lzo auth-nocache client dev tun proto udp remote 172.xxx.xxx.xxx 1194 cipher AES-256-CBC resolv-retry infinite nobind persist-key persist-tun mute-replay-warnings ca ca.crt cert user1.crt key user1.key tls-auth ta.key 1 remote-cert-tls server comp-lzo auth-nocache and finally (if used) the ccd/user1 and user2 and user3 iroute 192.168.1.0 255.255.255.0 and ccd/uservps iroute 90.xxx.xxx.xxx 255.255.255.0 and the pool list ipp.txt uservps,10.8.0.2 user1,10.8.0.40 user3,10.8.0.41 user2,10.8.0.42 Now the point is that everything is working fine, but i would like to understand why this error persist. also if an iroute is configured in ccd/ and push (route ..... ) in enabled in server.conf , problem still persist, actually services on lan are working fine. :o Thank you very much. nat
TinCanTech nathansklero wrote MULTI: bad source address from client [::], packet dropped This can be safely ignored. MULTI: bad source address from client [::], packet dropped [::] is an unroutable IPv6 address .. essentially the same as 127.0.0.1
nathansklero Thank you, from theorically point of view it should be routed or is unroutable by its nature ? Have a nice day nat
