|
Bugzilla – Full Text Bug Listing |
| Summary: | ifup configured eth0 does not work anymore after recent updates | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 13.1 | Reporter: | Forgotten User OvlPd7Jcli <forgotten_OvlPd7Jcli> |
| Component: | Network | Assignee: | wicked maintainers <wicked-maintainers> |
| Status: | RESOLVED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | chcao, forgotten_OvlPd7Jcli, jo.oiongen, mail, pwieczorkiewicz, rvpittman+novell, smartysmart34 |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Forgotten User OvlPd7Jcli
2014-03-20 15:29:44 UTC
ifup did not work for me. But, running "dhclient" and then setting default route manually in CLI worked. Appears to affect ALL network connections including eth1 and a rndis "usb0" connection for my smartphone. A workaround is to enable network manager or as a last resort reinstall the opensuse 13.1 dvd choosing "update" which downgrades whatever update is causing the issue. In testing I found the problem occurs even if the only 4 libraries you have enabled are: 1) Opensuse-Current OSS 2) Opensuse-Current Non-OSS 3) Opensuse-Current OSS Updates 4) Opensuse-Current Non-OSS Updates The bug is talked about here: http://forums.opensuse.org/showthread.php/496398-Latest-updates-on-Opensuse-13-1-X64-makes-network-unreachable-if-you-are-using-ifup?p=2632182&posted=1#post2632182 I "solved" the problem as follows: 1. Open YaST -> Network Devices 2. Switch to NetworkManager, and accept changes. 3. Reopen YaST -> Network Devices 4. Locate your network card and use 'Delete' to remove its configuration. Accept the changes. 5. Re-open YaST -> Network Devices 6. Edit your network card (you will likely notice that the card is set to start 'At Boot', while before it was set to start 'On cable connection' before removing the configuration). Accept changes. 7. Switch back to ifup I am not sure if these steps are all required, but they worked on all my machines. I suspect it has something to do with the activation "On cable connection", but I have no way to investigate this because my machines are now working properly. If you could try to just switch to "At boot" before deleting the configuration, and then reboot, it would probably help. Regards Alberto's method did not work for me. My network cards were set to start 'At boot' initially. Same for me. Went to Network manager, back to ifup. went from dhcp to static and back to dhcp. In any case: The card does not come up when starting the system. I have to manually "ifup" it. Maybe this is linked to the controllers? Mine is a realtek RTL8111/8168B Deleting and then adding the card again worked for me. There is a lengthy analysis session here that might lead to some hint (initrd-devices messed up by whatever). Please note, that regardless of that, the "systemctl status network.service" command renders different outputs depending on whether it is run with the new sysconfig-network package or with the previous one. http://forums.opensuse.org/showthread.php/496398-Latest-updates-on-Opensuse-13-1-X64-makes-network-unreachable-if-you-are-using-ifup/page4 ifup belongs to wicked-service, please assign to maintainer Hi Alberto, this product does not longer get updates, would you please double check whether this issue still exists and you can reproduce it on a newer version? In that case please open a new bug and provide a reference to this bug and close this one. Thank you! The problem cannot be reproduced in OpenSUSE Leap 42.1. I would say you can safely close this issue. Alberto, thank you for double checking. @ wicked-maintainers, would you like to help close this issue? Thank you! The issue is not reproducible with wicked. |