From: Jonathan Kamens <jik@kamens.brookline.ma.us>
To: lartc@vger.kernel.org
Subject: [LARTC] MSS clamping doesn't work with masquerading through VPN?
Date: Fri, 23 May 2003 16:42:10 +0000 [thread overview]
Message-ID: <marc-lartc-105370823732142@msgid-missing> (raw)
My employer uses a Microsoft VPN concentrator. I followed the
instructions at pptpclient.sourceforge.net to add support for that
concentrator to my Linux machine; after doing so, I was able to
successfully connect to the VPN and access machines on the other side
of it from my Linux box.
However,, I found that I couldn't use rdesktop to connect to a
Terminal Services server at work. I tracked down the problem to my
MTU being too high, as documented here:
<URL:http://pptpclient.sourceforge.net/howto-diagnosis.phtml#connections_freeze>.
After setting the MTU and MRU for the VPN connection to 1000 as
documented there, I was able to use rdesktop from my Linux machine.
I have VMware installed on my Linux machine, and I run Windows XP
Professional inside of it. I wanted to be able to also access the VPN
from my VMware virtual machine, so I followed the instructions found
here: <URL:http://pptpclient.sourceforge.net/routing.phtml#lan-to-lan>
to set up the routing, including doing "iptables --append FORWARD
--protocol tcp --tcp-flags SYN,RST SYN --jump TCPMSS
--clamp-mss-to-pmtu" to ensure that the MTU would be reduced for the
traffic from my XP machine as well as the traffic from my Linux box.
Note that I have only one public IP address, the Linux box -- the
VMware virtual machine is on a private subnet and the Linux box does
routing and masquerading for it through the VPN (and SNAT through my
static IP connection).
Even with the MSS clamping in place, the Remote Desktop client on XP
doesn't work -- it fails in essentially the same way that rdesktop on
Linux was failing before I reduced the MTU. However, I was able to
get the XP client to work by editing the Windows registry to
explicitly set the MTU to 1000 there.
I thought that the MSS clamping was intended to achieve the same
thing. I'm at a loss to explain what I did wrong to prevent it from
working as intended :-).
I'd rather not leave the MTU set to 1000 for all packets leaving my XP
machine, because that'll reduce my throughput. I'd really rather have
things work as intended, i.e., have only traffic going through the VPN
be clamped.
Any suggestions for what I might be doing wrong and/or how to debug
the problem further?
Thank you,
Jonathan Kamens
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2003-05-23 16:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-105370823732142@msgid-missing \
--to=jik@kamens.brookline.ma.us \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.