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

Re: [Openvpn-users] Windows client, mysterious routes and MTU issues


  • Subject: Re: [Openvpn-users] Windows client, mysterious routes and MTU issues
  • From: Erich Titl <erich.titl@xxxxxxxx>
  • Date: Sun, 05 Feb 2006 22:21:44 +0100

John

John A. Sullivan III wrote:
Hello, all.  We are seeing some bizarre behavior with our Windows
OpenVPN clients.  We are not seeing the same behavior in the Linux
clients.  Our setup is an OpenVPN gateway running openswan connecting to
other offices via openswan.  I am just now beginning to peruse the more
obscure configuration settings and do some extensive testing but, if
anyone knows the answer off the top of their head, it will save me many
hours.

Whenever the windows client accesses a station in one of the offices,
i.e., across the openswan VPN, an entry for that station is added to the
Windows routing table. Although that is surprising, it would not be too
bad except that the MTU on the route is set to 576!

Did you disable PMTU discovery on Windoze? The reduced MTU size could be one of the indications. The surprising thing is, how else would the windows client know that his OpenVPN connection is futher tunneled through an OpenSwan connection?


The result is
massive packet fragmentation.

:-) No surprise

cheers

Erich



____________________________________________
Openvpn-users mailing list
Openvpn-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/openvpn-users


Warning: require_once(../../../archive_common.php) [function.require-once]: failed to open stream: No such file or directory in /home/openvpn/domains/openvpn.net/public_html/archive/openvpn-users/2006-02/msg00070.html on line 196

Fatal error: require_once() [function.require]: Failed opening required '../../../archive_common.php' (include_path='/usr/local/lib/php') in /home/openvpn/domains/openvpn.net/public_html/archive/openvpn-users/2006-02/msg00070.html on line 196