Bug 39230 - ifup not returning after setting up a ppp link (sometimes)
Summary: ifup not returning after setting up a ppp link (sometimes)
Status: CLOSED DUPLICATE of bug 39543
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: initscripts
Version: 7.1
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-05-05 19:49 UTC by Carlos Rodrigues
Modified: 2014-03-17 02:20 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2001-05-12 01:27:43 UTC


Attachments (Terms of Use)

Description Carlos Rodrigues 2001-05-05 19:49:53 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.2-2 i686)

Description of problem:
Sometimes (I haven't figured out the causes) when I do /sbin/ifup pppX it
never returns altough the link is up and usable. I've tried with more than
one ISP and it still happens.
When the problem happens, running top shows two ppp-watch processes along
with pppd.

How reproducible:
Sometimes

Steps to Reproduce:
1. /sbin/ifup ppp0
2.
3.
	

Actual Results:  Sometimes I never get the command prompt back

Expected Results:  It should have returned to the command prompt after the
link was up.

Additional info:

I'm running ipcheck from /etc/ppp/ip-up.local to update my dyndns.org
account but it updates and returns normally (specifically when the problem
occurs).
I'm using ppp over a 56K modem line to my ISP.

Comment 1 Bill Nottingham 2001-05-07 13:45:36 UTC
ifup-ppp is syncrhonous. It should only return when the link goes down, or,
if you call it when it's already up, after initiating a redial.

Comment 2 Carlos Rodrigues 2001-05-07 22:50:27 UTC
I've always used /sbin/ifup to bring up my ppp link and /sbin/ifdown to bring 
it down and before redhat 7.1 it returned back to the command line 100% of the 
times, now it only returns 90%.

Comment 3 Carlos Rodrigues 2001-05-13 18:10:45 UTC

*** This bug has been marked as a duplicate of 39543 ***


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