Bug 97886 - multilink ppp hangs ifup script
Summary: multilink ppp hangs ifup script
Alias: None
Product: Fedora
Classification: Fedora
Component: initscripts   
(Show other bugs)
Version: rawhide
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
Whiteboard: bzcl34nup
Depends On:
TreeView+ depends on / blocked
Reported: 2003-06-23 17:55 UTC by Tomasz Kepczynski
Modified: 2014-03-17 02:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-06 23:55:55 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
ppp0 setup (403 bytes, text/plain)
2003-06-23 17:57 UTC, Tomasz Kepczynski
no flags Details
ppp1 setup (405 bytes, text/plain)
2003-06-23 17:58 UTC, Tomasz Kepczynski
no flags Details

Description Tomasz Kepczynski 2003-06-23 17:55:31 UTC
Description of problem:
  I created two modem/ppp devices using redhat-config-network. Both point to the
same telephone number and use the same login/password but different modems
(ttyI0 and ttyI1 actually but I am quite sure it is not relevant). In ppp
options I specified debug and mp to be able to create bundle.
  The first ppp device ('ifup ppp0') correctly starts.
  The second started with 'ifup ppp1' hangs in a script, however the connection
is made and bundle seems to be created.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create two ppp devices to connect to the same provider and specify 'mp' in
2. Connect using the first device, it is OK.
3. Connect using the second device, ifup script hangs.

Actual results:
ifup script hangs

Expected results:
ifup script finishes with exitcode 0

Additional info:

Comment 1 Tomasz Kepczynski 2003-06-23 17:57:58 UTC
Created attachment 92561 [details]
ppp0 setup

Comment 2 Tomasz Kepczynski 2003-06-23 17:58:33 UTC
Created attachment 92562 [details]
ppp1 setup

Comment 3 George Collins 2003-07-21 02:31:50 UTC
adding the option updetach to pppd command line will detach the process and
allow the script to exit, but the connection will also terminate (see

Comment 4 George Collins 2003-07-28 03:22:33 UTC
Bypassing ppp-watch and invoking pppd manually with the updetach option works
with no problem.

Comment 5 Bill Nottingham 2005-09-30 19:06:00 UTC
Closing bugs on older, no longer supported, releases. Apologies for any lack of
It sounds like what you want is a generic means to bypass ppp-watch for a
particular device?

Comment 6 Tomasz Kepczynski 2005-10-03 10:41:50 UTC
Honestly I don't care about technical means as long as it works. I cheated
a bit by specifying ppp options directly, maybe system-config-network
should be adapted to allow bundle creation?

Comment 7 Bug Zapper 2008-04-03 15:27:47 UTC
Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.

If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we're following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

Comment 8 Bug Zapper 2008-05-06 23:55:53 UTC
This bug has been in NEEDINFO for more than 30 days since feedback was
first requested. As a result we are closing it.

If you can reproduce this bug in the future against a maintained Fedora
version please feel free to reopen it against that version.

The process we're following is outlined here:

Note You need to log in before you can comment on or make changes to this bug.