Description of problem: Every time after 'ifdown ppp0' command execution or during system reboot process, my DSL connection gets deleted, so I need to recreate it every time. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Create new DSL PPPoE connection via 'drakconnect' 2. Connect to internet 'ifup ppp0' 3. Bring interface down 'ifdown ppp0' 4. Try to bring interface up again 'ifup ppp0' [root@localhost]# ifup ppp0 RTNETLINK answers: No such device Cannot find device "ppp0" Using interface ppp0 Connect: ppp0 <--> /dev/pts/1 CHAP authentication succeeded CHAP authentication succeeded local IP address 82.199.xxx.xx remote IP address 82.199.xxx.x primary DNS address 82.199.xx.xxx secondary DNS address 82.199.xxx.xxx [root@localhost]# ifdown ppp0 pppoe: read (asyncReadFromPPP): Session 61919: Input/output error <-- this message is a norm. [root@localhost]# ifup ppp0 /etc/sysconfig/network-scripts/chat-ppp0 does not exist ifup-ppp for ppp0 exiting
To Thierry for starters because of 'drakconnect'.
Assignee: bugsquad => thierry.vignaudCC: (none) => lewyssmith
Some more investigation. 'drakconnect' creates at least two required files for TYPE=ADSL connection to work properly, /etc/sysconfig/network-scripts/ifcfg-ppp0 and /etc/ppp/peers/ppp0 What I've noticed is execution of 'ifdown ppp0' deletes /etc/ppp/peers/ppp0 file. Not sure if it's intended behaviour, but next execution of 'ifup ppp0' fails, because of absent /etc/ppp/peers/ppp0 file.
Created attachment 11184 [details] ifcfg-ppp0
Created attachment 11185 [details] /etc/ppp/peers/ppp0
As a workaround I had to manually alter generated ifcfg-ppp0 to use TYPE=xDSL instead. This TYPE uses external scripts for ifup/ifdown which are parts of rp-pppoe package.
I think this is the upstream fix for this https://github.com/deekej/initscripts/commit/f25f4828ea1c56c95d91586bec7403ab6cd48d76
CC: (none) => srowe
I confirm, applying the above changes fixes the initial problem.
CC: (none) => rolfpedersen
Bump, this still affects mga8.
As Simon said in comment 8 this bug still valid for mga8. And to make matters worse, the solution from comment 6 doesn't work anymore for me... What about you, Simon? The original link to that solution is dead, so here's another one: https://github.com/fedora-sysv/initscripts/pull/156/commits/f25f4828ea1c56c95d91586bec7403ab6cd48d76
Yes, I've just applied this change manually again.
Changing this.
Whiteboard: (none) => MGA7TOO MGA8TOOCC: (none) => ouaurelienVersion: 7 => CauldronTarget Milestone: --- => Mageia 9
Heh, that's really odd... In my case, /etc/ppp/peers/ppp0 file keeps being deleted after 'ifdown ppp0' command even now, regardless of changes made to /etc/sysconfig/network-scripts/ifdown-post script. And IIRC, the solution mentioned in comment 6 & now in comment 9, in my case, worked for about a month in mga7, but then stopped again for some unknown reasons.
Version: Cauldron => 7
Mageia 7 is EOL since July 1st 2021. There will not have any further bugfix for this release. You are encouraged to upgrade to Mageia 8 as soon as possible. @reporter, if this bug still apply with Mageia 8, please let us know it. @packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead. This bug report will be closed OLD if there is no further notice within 1st September 2021.
Yes, as mentioned in comment 8, this bug still affects mga8. Nothing has been changed since then.
CC: (none) => marja11Version: 7 => 8
We stopped supporting Mageia 8 almost 8 months ago https://blog.mageia.org/en/2023/12/30/mageia-8-end-of-life/ That means we also stopped fixing Mageia 8 bugs and that this bug report needs to be closed, regardless of whether it was fixed for Mageia 8 or not. If this particular bug did not get fixed for Mageia 8, then we do regret that. If this issue is still present in Mageia 9 or cauldron, then please reopen this report, write a comment and adjust the "Version:" field. If you are not yet a member of one or our teams, then please consider becoming one. https://wiki.mageia.org/en/Contributing Mageia is a community project, meaning that we, the users, make Mageia together. The more active contributors we have, the more bug reports will get fixed. Besides, being active in a team can be very rewarding. It was and is certainly rewarding to me :-D
Resolution: (none) => OLDStatus: NEW => RESOLVED