> It seems clearly MTU-related.
but if NAT gw machine has MTU already set do 1492, then there is no need for
"NATed" clients to change MTU.
i call pppoe with "-m 1412". if this helps you...
--
--
To UNSUBSCRIBE, email to debian-is...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
> > > i call pppoe with "-m 1412". if this helps you...
> >
> > The MTU of the PPP link (1492) seems fine, the router itself has no
> > problems. And remember, only MacOS has problems.
>
> The "-m 1412" causes pppoe to clamp the maximum TCP segment size to
> 1412. There is now kernel support to do this so that would probably be
> better. Infact use kernel support for pppoe if you can (although I
> don't know how mature it is).
I've been using the kernel support for pppoe since before it was actually
included in the standard kernel tree, and the mss clamp module for
iptables since it was introduced as well with great success. the setup is
rock steady, and the clamp module fixes the stupid path discovery issue
endemic to so many brane-dead dsl providers. note, that pppd also must be
patched to take advantage of this kernel support, and it is not available
in the standard debian package, although downloading the package source
and including the appropriate patch is pretty straight forward.
Brian
fa...@etc.etc.etc.
"You can't depend on your judgement when your imagination
is out of focus." -- Mark Twain