Bug 101651 - BAD: When activating the ppp0 get error 8
Summary: BAD: When activating the ppp0 get error 8
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: ppp   
(Show other bugs)
Version: 9
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Thomas Woerner
QA Contact: Jay Turner
Depends On:
TreeView+ depends on / blocked
Reported: 2003-08-05 08:37 UTC by Matthew
Modified: 2015-01-08 00:06 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-08-17 09:43:54 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Matthew 2003-08-05 08:37:47 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)

Description of problem:
BAD: When i try to activate my ppp0 connection in the network i get a error 8 
but i am able to dial-up and login using KPP and brows the internet and recive 
mail the reson i am trying to activate it is cause i am trying to get a win 98 
to route through the linux box but 
i am not able

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

How reproducible:

Steps to Reproduce:
1.Activate ppp0 connection
2.Activate ppp0 connection
3.Activate ppp0 connection

Actual Results:  ppp0 error 8

Expected Results:  Should dial-up and login then give me a activate on.

Additional info:

Comment 1 Edham Zainol 2003-09-12 03:44:34 UTC
I have a similar thing also. Furthermore Network Configuration Tool unable to 
detect my modem eventhough my modem already been installed properly. Without 
setting up thru this tool, however able me to communicate with my modem using 
wvdial - terminal based command. I looking for graphical interface for my 
customers. Thanks.

Comment 2 Thomas Woerner 2004-08-17 09:43:54 UTC
Please verify this with a newer version of Red Hat Enterprise Linux or
Fedora Core and reopen it against the new version if it still occurs.

Closing as "not a bug" for now.

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