From: Russ Cox rsc@research.att.com
Subject: ppp fix for mtu
Date: Sun, 1 Sep 1996 15:47:46 -0400 [thread overview]
Message-ID: <19960901194746.Gvsdyf2Qt4nR3-LQVvFAcDO4gTuDpYZLSrqlculnaWs@z> (raw)
I have (attempted to) fix ppp so that it respects
the remote's wishes as far as MTU is concerned.
There is a boddle on plan9.bell-labs.com in
/cm/cs/who/rsc/ppp.rc and stip.rc. Use at your
own risk.
ppp.rc needs to be applied in /sys/src/cmd/ppp
and also contains the changes that were in ppp.bod
from forsyth.
stip.rc needs to be applied in /sys/src/9/port
and changes the setip message. An MTU parameter
is added to the end, and if there is a '-' for
any parameter, it is treated as if it wasn't there.
Thus,
setip 135.104.3.9 255.255.255.0
is the same as
setip 135.104.3.9 255.255.255.0 - -
This is used by ppp, which does:
setip 135.104.3.9 255.255.255.0 - mtu
and lets ipmuxctl figure out what the third
parameter should be.
Russ
reply other threads:[~1996-09-01 19:47 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=19960901194746.Gvsdyf2Qt4nR3-LQVvFAcDO4gTuDpYZLSrqlculnaWs@z \
--to=9fans@9fans.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).