Bug 12651 - pppd attempts to fetch an IPv6 configuration despite it should not
Summary: pppd attempts to fetch an IPv6 configuration despite it should not
Status: CLOSED FIXED
Alias: None
Product: IPFire
Classification: Unclassified
Component: --- (show other bugs)
Version: 2
Hardware: all All
: Will only affect a few users Crash
Assignee: Peter Müller
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-07-02 10:57 UTC by Peter Müller
Modified: 2021-11-27 18:04 UTC (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Müller 2021-07-02 10:57:03 UTC 
If the ISP terminates the dial-up connection in case of IPv6 failures - bad practice IMHO, but at least BT seems to do so -, this renders dial-up in Core Update 157 unusable.

We need to ensure pppd is not even _asking_ for an IPv6 configuration, hence avoiding these failures.

See also: https://www.ispreview.co.uk/index.php/2021/03/two-uk-broadband-isps-trial-new-internet-snooping-system.html
Comment 1 Michael Tremer 2021-07-02 14:43:13 UTC 
Okay, so I am rolling back the change in c158 so that we have enough time to fix this for good. If something goes wrong, we break people's systems.

I will also revert the change in Core Update 157, so that people who update won't destroy their systems any more (because once they lose connectivity installing another update becomes tricky).
Comment 2 Peter Müller 2021-07-02 16:24:21 UTC 
@Michael: Thank you.

I just observed I accidentally posted a wrong link initially: It should have been https://community.ipfire.org/t/core-update-157-pppd-tries-to-fetch-an-ipv6-configuration-despite-it-shouldnt-causing-dial-up-connections-to-be-terminated-by-some-isps/5654/11, to link to the corresponding community thread. Sorry.
Comment 3 Michael Tremer 2021-07-02 16:25:01 UTC 
(In reply to Peter Müller from comment #2)
> I just observed I accidentally posted a wrong link initially: It should have
> been
> https://community.ipfire.org/t/core-update-157-pppd-tries-to-fetch-an-ipv6-
> configuration-despite-it-shouldnt-causing-dial-up-connections-to-be-
> terminated-by-some-isps/5654/11, to link to the corresponding community
> thread. Sorry.

Yeah I was quite confused about what that should have meant :)
Comment 5 Peter Müller 2021-07-13 19:42:28 UTC 
Waiting for test feedback:

https://lists.ipfire.org/pipermail/development/2021-July/010794.html
Comment 6 Peter Müller 2021-07-15 17:37:52 UTC 
A user sitting behind British Telecom reported back, confirming ppp 2.4.9 is working fine with "noipv6": https://community.ipfire.org/t/core-update-157-pppd-tries-to-fetch-an-ipv6-configuration-despite-it-shouldnt-causing-dial-up-connections-to-be-terminated-by-some-isps/5654/15

@Michael: I think we now have the confidence we sought for. Would you mind merging the patchset?
Comment 7 Peter Müller 2021-09-04 09:59:10 UTC 
Waiting for https://patchwork.ipfire.org/project/ipfire/list/?series=2186 to land in Core Update 160 (or beyond)...
Comment 8 Peter Müller 2021-10-01 10:00:06 UTC 
- ping -
Comment 9 Michael Tremer 2021-10-01 10:01:08 UTC 
Who are you pinging? You might want to CC Arne on this.
Comment 10 Peter Müller 2021-10-02 10:01:33 UTC 
(In reply to Michael Tremer from comment #9)
> Who are you pinging? You might want to CC Arne on this.

Oh, I thought he already was. :-/

@Arne: May I ask you to have a look at https://patchwork.ipfire.org/project/ipfire/list/?series=2186 ? IMHO, this is ready for production now.