Re: Setting MTU (fwd)

MegaZone (megazone@livingston.com)
Sun, 29 Dec 1996 20:00:51 -0800 (PST)

Once upon a time Tom Samplonius shaped the electrons to say...
>best with a different MTU size, it should ask for it. If it can't ask for
>it, it should be fixed, rather than have the access server ram a single
>MTU size down everybody's throught.

Clients can ask for, and will get, whatever MTU they want as long as it
is valid under the RFC - I believe we max at 1500 (the RFC allows for
larger packets).

Joe seems to want to be able ot specify the size of the packets transmitted
to the user. Which isn't what PPP is desinged to do - each end tells the
other end the max size it can *receive*. So when you dial into a PM the
PM tells the client it's MTU - and the client tells us the max size to
send to it.

If 1500 is too large, the *client* must specify a smaller size.

1500 has always worked fine for me, as long as the stack wasn't buggy
(like Trumpet 2.0b).

>clients. This is NOT what PPP was designed for. It was designed for
>client and server to negotiate agreeable protocol parameters.

Exactly.

-MZ

--
Livingston Enterprises - Chair, Department of Interstitial Affairs
Phone: 800-458-9966 510-426-0770 FAX: 510-426-8951 megazone@livingston.com
For support requests: support@livingston.com  <http://www.livingston.com/> 
Snail mail: 4464 Willow Road, Pleasanton, CA 94588