public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 2/2] Tell pppd not to ask for IPv6 addresses during dial-up
Date: Thu, 08 Jul 2021 11:34:28 +0100	[thread overview]
Message-ID: <0A68CFA0-94FD-4491-A8E9-EFD5BD1FC0FE@ipfire.org> (raw)
In-Reply-To: <47f6b552-e533-2e20-3d0b-c7bad78c88ac@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1794 bytes --]

Hello,

> On 7 Jul 2021, at 20:49, Peter Müller <peter.mueller(a)ipfire.org> wrote:
> 
> pppd 2.4.9 supports IPv6 and asks for an IPv6 configuration by default.
> Setting the received prefix in the kernel will never work, however, as
> the rest of IPFire 2.x does not support IPv6.
> 
> pppd notices the ISP about this, and at least Otenet (GR) and British
> Telecom (several countries) decide to close a dial-up connection then.
> German DTAG seems to ignore such errors silently.
> 
> This patch adds an option to the pppd call to prevent asking for an
> IPv6 configuration, hence avoiding this errors.
> 
> To apply this patch, it is necessary to ship ppp 2.4.9 again. Since I
> have no access to a testing machine behind an ISP supporting IPv6, this
> patch unfortunately is untested.

In general, but especially for such critical things, this is unacceptable.

Please look for someone who can test this.

> 
> Fixes: #12651
> 
> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
> ---
> src/initscripts/networking/red | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/src/initscripts/networking/red b/src/initscripts/networking/red
> index ca0a8ae58..56f8ebb66 100644
> --- a/src/initscripts/networking/red
> +++ b/src/initscripts/networking/red
> @@ -410,7 +410,7 @@ case "${1}" in
> 			### Standard PPP options we always use
> 			#
> 			PPP_STD_OPTIONS="$PLUGOPTS usepeerdns defaultroute noipdefault noauth"
> -			PPP_STD_OPTIONS+=" default-asyncmap hide-password nodetach"
> +			PPP_STD_OPTIONS+=" default-asyncmap hide-password nodetach noipv6"
> 			PPP_STD_OPTIONS+=" noaccomp nodeflate nopcomp novj novjccomp"
> 			PPP_STD_OPTIONS+=" nobsdcomp user ${USERNAME} lcp-echo-interval 20"
> 			PPP_STD_OPTIONS+=" lcp-echo-failure 5 ${AUTH}"
> -- 
> 2.26.2


  reply	other threads:[~2021-07-08 10:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-07 19:49 [PATCH 1/2] Revert "Revert "ppp: update to 2.4.9"" Peter Müller
2021-07-07 19:49 ` [PATCH 2/2] Tell pppd not to ask for IPv6 addresses during dial-up Peter Müller
2021-07-08 10:34   ` Michael Tremer [this message]
2021-07-10 21:13     ` Peter Müller
2021-07-13 19:41       ` Call for testers: pppd 2.4.9 without IPv6 configuration, solving bug #12651 Peter Müller

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=0A68CFA0-94FD-4491-A8E9-EFD5BD1FC0FE@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox