Bug 109411 - xdsl problems if not named ppp0
Summary: xdsl problems if not named ppp0
Status: CLOSED DUPLICATE of bug 109601
Alias: None
Product: Fedora
Classification: Fedora
Component: rp-pppoe   
(Show other bugs)
Version: 1
Hardware: i686 Linux
Target Milestone: ---
Assignee: Ngo Than
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2003-11-07 16:23 UTC by M. Gregory
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 18:59:49 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Patch for network script to solve the xdsl start/stop problem. (1014 bytes, text/plain)
2003-11-08 04:50 UTC, Marcos Bellezi
no flags Details

Description M. Gregory 2003-11-07 16:23:43 UTC
Description of problem:

If name of provider is not ppp0 there is problems changing, shutting down

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

How reproducible:

every time.

Steps to Reproduce:
1. install fc1 from iso
2. use network config from system settings->network
3. new xdsl
4. name of provide: anything except ppp0
Actual results:
when rebooting ppp0 fails to shutdown.

Expected results:

ppp0 shuts down

Additional info:

Comment 1 Marcos Bellezi 2003-11-08 04:50:44 UTC
Created attachment 95817 [details]
Patch for network script to solve the xdsl start/stop problem.

Comment 2 M. Gregory 2003-11-08 20:26:53 UTC
Thats got it! Thanks. Mike

Comment 3 Andre Robatino 2003-11-10 04:46:20 UTC
  This is the same as bug #108033 for test3.

Comment 4 Andre Robatino 2003-11-10 15:59:56 UTC
  I applied the patch, and it works perfectly on startup, but there is
no message

Shutting down interface [xdsl interface name] :

on shutdown.

Comment 5 Bill Nottingham 2003-11-10 17:07:08 UTC

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

Comment 6 Red Hat Bugzilla 2006-02-21 18:59:49 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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