> > I'm happy to announce this problem has finally found its final solution
in
> > ppp version >= 11/28/2000: the new option "tcpmssfixup" (enabled by
> > default!) corrects the outgoing TCP MSS and solves the problem for good.
> > This functionality is strictly identical to what the tcpmssd port does,
but
> > it's now included in ppp, so no need to run an external program with
divert
> > sockets etc.
I've been watching this thread (since when I used to use DSL & PPPoE I used
to see this problem, although at the time I didn't know what it was) and am
amazed at how everyone's worked together to detect and fix this problem.
Now, I'm not trying to play devil's advocate (although that would make me a
friend of Chucky, right?) but I'm wondering if user-ppp is the right place
to make this change. Isn't the problem specific to PPPoE? If that's the
case, then shouldn't it be ng_pppoe that gets updated, so that anything that
uses ng_pppoe will have the option of enabling the 'tcpmssfixup' option?
--
Matthew Emmerton
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
