Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 109601
| Summary: | /etc/init.d/network does not correctly handle xDSL connections | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Josi Romildo Malaquias <romildo> | ||||||
| Component: | initscripts | Assignee: | Bill Nottingham <notting> | ||||||
| Status: | CLOSED RAWHIDE | QA Contact: | Brock Organ <borgan> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 1 | CC: | prata, redhat, robatino, rvokal | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | 7.43-1 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2003-11-10 22:50:21 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: | |||||||||
| Attachments: |
|
||||||||
This is the same as bug #109411 and bug #108033. I applied the patch provided in the bug #109411 bug report and it fixed it for me (and the original reporter). *** Bug 109411 has been marked as a duplicate of this bug. *** *** Bug 108033 has been marked as a duplicate of this bug. *** Created attachment 95879 [details]
patch to fix this
Try the attached; it's a little more generic than the patch in the other bugs.
Same result as with the patch in bug #109411 - works perfectly on startup, but on shutdown there is no message Shutting down interface [xdsl interface name] : as there should be. Created attachment 95888 [details]
patch, take 2
This should fix one of the obvious ways that the ifdown step would get skipped.
Use this instead of the previous patch.
I patched and rebooted. It shut down the interface properly on shutdown, and brought it up properly on startup. I think it's fixed. Fixed in CVS, will be in 7.43-1. You might want to take another look at the patch. The last time I shutdown, I saw two identical shutdown messages for the xdsl interface, the first succeeded and the second failed (since the interface was already down). This is the first time out of several shutdowns where it happened. *** Bug 109884 has been marked as a duplicate of this bug. *** *** Bug 109607 has been marked as a duplicate of this bug. *** |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031030 Description of problem: To start up a xDSL connection, the script /etc/init.d/network calls ifup with the device name of the connection as its argument (ppp0 in my case), requiring the existence of a file named ifup-<device> (ifup-ppp0 in my case) in the /etc/sysconfig/network-scripts directory. But the internet-druid program, used to set up the connection, creates a file ifup-<proavider name>, named after the provider name (ifup-NetSuper in my case). As a consequence, the script fails to bring up the connection. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Configure a xDSL connection with internet-druid, setting the provider name to NetSuper, lets say. Also sets the connection to start at initialization time. 2. 3. Actual Results: At initialization time /etc/init.d/network fails to start the connection, with a message saying that ifup did not find the configuration file for the DEVICE used in the connection. Expected Results: The connection should be successfully stablished. Additional info: Making a symbolic link from /etc/sysconfig/network-scripts/ifcfg-<provider name> to /etc/sysconfig/network-scripts/ifcfg-<device name> solves the problem, but then the connection is started twice (and the second time the script fails because the connection is already up).