[Bug 570669] New: wired interface still keeps a address after carrier removal
http://bugzilla.novell.com/show_bug.cgi?id=570669 http://bugzilla.novell.com/show_bug.cgi?id=570669#c0 Summary: wired interface still keeps a address after carrier removal Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: nettezzaumanaa@gmail.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.15) Gecko/2009102100 SUSE/3.0.15-0.1 Firefox/3.0.15 hi suse developers .. my patience with suse network stack is over now in 11.2 : 1) interface keeps his address and is still up after carrier removal 2) dhcpcd must be killed if needed explicitely with SIGKILL, SIGTERM doesn't help. compared to previous releases after dhcpcd murder interface still keeps a address 3) dhcpcd doesn't correctly handle with his own etc/resolv.conf, it's done by fathomless design of if-{up,down} scripts regards by daniel Reproducible: Always Steps to Reproduce: simply put at beginning of ifup script : set -x; eval 2>/tmp/ifup-eth0.debug . and unplug and plug in again a cable and let's see, what all is script doing -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=570669
http://bugzilla.novell.com/show_bug.cgi?id=570669#c1
Marcus Meissner
http://bugzilla.novell.com/show_bug.cgi?id=570669
http://bugzilla.novell.com/show_bug.cgi?id=570669#c2
--- Comment #2 from Daniel Pecka
http://bugzilla.novell.com/show_bug.cgi?id=570669
http://bugzilla.novell.com/show_bug.cgi?id=570669#c3
--- Comment #3 from Daniel Pecka
http://bugzilla.novell.com/show_bug.cgi?id=570669
http://bugzilla.novell.com/show_bug.cgi?id=570669#c4
Marius Tomaschewski
http://bugzilla.novell.com/show_bug.cgi?id=570669
http://bugzilla.novell.com/show_bug.cgi?id=570669#c5
--- Comment #5 from Marius Tomaschewski
Further, I think you've modified your resolv.conf manually or changed
Further, because you've modified your resolv.conf manually ... netconfig refuses to overwrite your changes. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=570669
http://bugzilla.novell.com/show_bug.cgi?id=570669#c6
Daniel Pecka
http://bugzilla.novell.com/show_bug.cgi?id=570669
http://bugzilla.novell.com/show_bug.cgi?id=570669#c7
--- Comment #7 from Daniel Pecka
http://bugzilla.novell.com/show_bug.cgi?id=570669
http://bugzilla.novell.com/show_bug.cgi?id=570669#c8
Marius Tomaschewski
not really .. i don't update resolv.conf manualy, i am using following method:
Sorry, but this is also what you write in comment #3:
i need to manually correct resolv.conf
doing it once disables netconfig. => "netconfig update -f" to fix it. (In reply to comment #6)
.. but anyway, i don't consider this problem as resolved, because of it's then badly set *by default ..
if i choose in `yast2 lan` *traditional ifup/down method rather then dhcp and let there default "on cable connection" it won't work without additional changes ..
AFAIK yast2 network does this by default when you configure ethernet and wireless interface together -- at least at the installation time. Feel free to report a yast2 bug. Further, not everybody has same expectation as you have and don't want to stop the interface. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com