Re: Fwd: Re: (no subject)

On Sun, 30 Jan 2005 ceja@acsalaska.net wrote:

> I've managed to fix the problem after a really long night. I plan on emailing
> my discover to ACS (dunno if they care or not) just as a reference. I'm on a
> Suse 9.2 box. I just tried downloading the rp-pppoe src and I used that
> instead of crap suse comes with (which is btw rp-pppoe) and it works fine
> now. Go figure, It goes to show Auto config scripts and rpms are bad news.
> Thanks for all the help though.

Well, the Linux pppd PPPOE support comes from rp-pppoe.

There was a semi-known issue some time back.

Depending on the kernel version the software was built against, with older
rp-pppoe (including the version first included in the native pppd
software), it would fail to properly set MTU.

The PPPOE server would transmit MRU, pppd would then take the MRU value to
use as local MTU for the PPP interface, but would mis-apply it, leaving
the ppp interface with the wrong MTU.

The old work around was to use an ip-up script to set the ppp interface
MTU via ip of ifconfig. Course you would need to use 'ping -s' with
increasing values to determine the actual link MTU so you knew what to set
it to.

1492 is normal, but some systems/areas further reduce this through use of
L2TP transport from DSLAM to redback (MTA land). In theory 1462 is safe
almost anywhere, so many systems default to 1460 (including ACS).

Speaking only for me, myself and I

---------
To unsubscribe, send email to <aklug-request@aklug.org>
with 'unsubscribe' in the message body.
Received on Mon Jan 31 22:13:56 2005