Note that the problem is not limited to Windows - some versions of Samba have the same problem - and, although it is generally a broadcast problem, it is occasionally not a Netbios/SMB broadcast.
Fundamentally, the problem is that *nix TCP/IP networking started with the assumption that a server would have a single adapter with a single IP address. The "Socket" interface is a standard way of dealing with that situation. Once you go to multiple adapters, each with multiple IP addresses, there is no standard interface, and the whole thing is OS dependent. I certainly have a lot of sympathy with the samba/linux/OSX/windows implementations that broadcast packets using the wrong source IP address. I've tried to find the correct IP address on a multi-homed server and sometimes there was nothing but pain. (david) -----Original Message----- From: Jan Just Keijser [mailto:janj...@nikhef.nl] Sent: Friday, 5 July 2013 10:16 AM To: joshua gross Cc: openvpn-users@lists.sourceforge.net Subject: Re: [Openvpn-users] Logs contain multiple "bad source address packet dropped" lines > this can happend when the clients are running Windows and when the file sharing protocol is bound to the tap-win32 adapter - in that case Windows sometimes uses the wrong source address. Unfortunately, there's little that can be done about this. HTH, JJK ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
