From: Gregory Colpart <gcolpart@evolix.net>
To: linux-ppp@vger.kernel.org
Subject: Re: Error message with persist option
Date: Wed, 26 Oct 2005 22:36:53 +0000 [thread overview]
Message-ID: <20051026223653.GB26094@test-scsi> (raw)
In-Reply-To: <20051026194149.GA17341@test-scsi>
On Wed, Oct 26, 2005 at 10:18:18PM +0200, Gilles Espinasse wrote:
> with ppp-2.4.3 version, is it the debian package or standard ppp-2.4.3
> There is numerous ppp-2.4.3 flavour including some patches wich may help.
> You should try with the debian package or with ppp-2.4.4b1 wich should
> include all those fixes.
Yes, I use debian package then debian patches and this doesn't
fix my bug. I will try with version 2.4.4b1.
> > 21:00:03 pppd[29191]: Couldn't increase MTU to 1500. Using 1492
> > 21:00:03 pppd[29191]: Couldn't increase MRU to 1500. Using 1492
> I don't know for ipv6 but with ipv4,you could remove MTU/MRU\x1492
> This is only necessary with PPPoE and not PPPoA
Yes, no problem with IPv4. I use MTU/MRU\x1492 for IPv6 because I have
a problem with PMTU Discovery. PMTU Discovery works fine when I use
tracepath6 util but with real IPv6 connection, it seems broken...
I have no time to investigate this problem yet.
Thanks,
--
Gregory Colpart <reg@evolix.fr> GnuPG:1024D/C1027A0E
Evolix - Informatique et Logiciels Libres http://www.evolix.fr
next prev parent reply other threads:[~2005-10-26 22:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-26 19:41 Error message with persist option Gregory Colpart
2005-10-26 19:45 ` Marco d'Itri
2005-10-26 20:18 ` Gilles Espinasse
2005-10-26 22:22 ` Gregory Colpart
2005-10-26 22:23 ` Bill Unruh
2005-10-26 22:36 ` Gregory Colpart [this message]
2005-10-27 15:48 ` Clifford Kite
2005-10-27 21:33 ` Gilles Espinasse
2005-10-28 14:19 ` Clifford Kite
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=20051026223653.GB26094@test-scsi \
--to=gcolpart@evolix.net \
--cc=linux-ppp@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.