Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 70789

Summary: ppp ifup script error when trying to dialup, wvdial still works
Product: [Retired] Red Hat Linux Reporter: Need Real Name <matt>
Component: pppAssignee: Nalin Dahyabhai <nalin>
Status: CLOSED RAWHIDE QA Contact: Jay Turner <jturner>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0CC: srevivo
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-07-30 23:08:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 67218, 79579, 100644    

Description Need Real Name 2002-08-05 10:37:33 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.5 (X11; Linux i686; U;) Gecko/20020712

Description of problem:
/sbin/ifup hangs when I try to connect (either through the commandline or
through redhat-config-network, and /var/log/messages reads:
Aug  5 20:04:25 hive pppd[4314]: pppd 2.4.1 started by root, uid 0
Aug  5 20:04:25 hive ifup-ppp: pppd started for ppp0 on /dev/ttyS1 at 38400
Aug  5 20:04:25 hive pppd[4314]: Connect script failed
Aug  5 20:04:26 hive pppd[4314]: Exit.

ifup doesn't return (exit), but keeps trying, and the above message keeps
repeating until I ^C

wvdial still works fine.

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


How reproducible:
Always

Steps to Reproduce:
1.Configure modem and dial-up account
2./sbin/ifup ppp0
	

Actual Results:  as above - /var/log/messages reads "connect script failed" but
ifup keeps trying to connect

Expected Results:  connection to internet, ifup exits.

Additional info:

Comment 1 Nalin Dahyabhai 2002-08-13 02:20:01 UTC
Whoops, handling of --remotename on the command line fell up when we updated to
1.53.  Fixed in 1.53-5 and later.

Comment 2 Bill Nottingham 2003-07-30 23:08:29 UTC
Closing out some bugs that have been in MODIFIED state. Please reopen if they
persist.