Bugzilla will be upgraded to version 5.0 on December 2, 2018. The outage period for the upgrade will start at 0:00 UTC and have a duration of 12 hours
Bug 612 - pppd doesn't check for its MTU/MRU limits; obscure error message and line drop results
pppd doesn't check for its MTU/MRU limits; obscure error message and line dro...
Product: Red Hat Linux
Classification: Retired
Component: ppp (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
Depends On:
  Show dependency treegraph
Reported: 1998-12-26 17:48 EST by aa8vb
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1998-12-31 14:32:33 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description aa8vb 1998-12-26 17:48:13 EST
Apparently, Redhat 5.2's pppd (2.3pl5) has internal
limits on MTU/MRU that it doesn't check for on the
command line.  Specifying an MTU/MRU that is beyond
these undocumented internal limits (e.g. 1524) on the
command line results in pppd starting up, taking these
values, negotiating them with the server, and only after the
line is up and a packet too big is received, generating an
obscure error message and exiting.  Here is the error it

Dec 26 14:48:01 blackbird-eth pppd[2895]: read: Value too
large for defined data type(75)
Comment 1 aa8vb 1998-12-26 17:49:59 EST
BTW, lowering the specified MTU to 1064 works around this pppd bug.
--Randall (aa8vb@pagesz.net)
Comment 2 David Lawrence 1998-12-31 14:32:59 EST
I tried this several times in the test lab and in all cases pppd did
the correct thing. If you specify a number larger that 1500 and both
ends have a max of 1500 then it will drop down to 1500 which is also
the default pppd will use if no mru and mtu are specified. When I
entered a number less that 1500 it used that number specifically. I
was unable to genrate the error that you were reporting.

One possibility is that the server you are dialing into is not using
Linux and their pppd server supports packet sizes larger that 1500
where the linux pppd client does not therefore generating the errors.

Note You need to log in before you can comment on or make changes to this bug.