http://bugzilla.novell.com/show_bug.cgi?id=570669 http://bugzilla.novell.com/show_bug.cgi?id=570669#c2 --- Comment #2 from Daniel Pecka 2010-01-15 07:36:36 UTC --- Hi dear Marcus .. What does the bloody hell (wtbh) *mts stands for .. i am suspecting something like "molest that scripts alone" ;) but honestly, i am expecting some needinfo request .. anyway, i report bad design of suse ifup-$nic scripts, which are really bad and weirdly complicated . one of the impact is, that dhcpcd ivoked by this scripts would never rewrite etc/resolv.conf .. to fix it, you have to rewrite it by hand or `pkill -9 dhcpcd` and launch it again with some more reasonable parameters .. btw, what was changed, that after dhcpcd murder is address still up. this changed since previous releases because killing dhcpcd led in past to bring iface down and flush address .. ave by daniel -- 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#c4 Marius Tomaschewski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |radmanic@novell.com Resolution| |WORKSFORME --- Comment #4 from Marius Tomaschewski 2010-01-15 09:24:24 UTC --- I think your problem is: /etc/sysconfig/network/dhcp ## Type: yesno ## Default: yes # # dhcpcd -E/--lastlease option # # This setting controls whether dhcpcd should try to use DHCP settings # provided in its last lease when the dhcp-server is not reachable and # the lease hasn't expired yet. # Set this variable to "no" to disable the fallback to the last lease. # DHCLIENT_USE_LAST_LEASE="yes" Further, I think you've modified your resolv.conf manually or changed the default settings -- see also output of "netconfig update". To fix it, ensure, that following settings are set: $ grep ^NETCONFIG_DNS /etc/sysconfig/network/config NETCONFIG_DNS_POLICY="auto" NETCONFIG_DNS_FORWARDER="resolver" NETCONFIG_DNS_STATIC_SEARCHLIST="" NETCONFIG_DNS_STATIC_SERVERS="" and call "netconfig update -f" to force it once. Further, enable "On Cable Connection" in yast2 for your interface, that is the following settings is in the ifcfg files: STARTMODE=ifplugd IFPLUGD_PRIORITY=0 When you have multiple interfaces (e.g. wireless and wired) you may have to set a different IFPLUGD_PRIORITY for both (10 for wired one and 20 to use wired when cable is plugged in, otherwise wireless). Note, that ifplugd does not work together with bridges. -- 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 changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME | --- Comment #6 from Daniel Pecka 2010-01-15 10:31:05 UTC --- not really .. i don't update resolv.conf manualy, i am using following method: # alias | grep dhc alias dhc0='pkill -9 dhcpcd; dhcpcd eth0' alias dhc1='pkill -9 dhcpcd; dhcpcd eth1' . 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 .. and btw i reported also that, compared to previous suse releases, iface still keeps a addresses even if cable is unplugged and dhcpcds' murder also doesn't bring iface down like in older suse, which is imho reasonable .. so what's resolved then? i can help myself and i don't need any mention howto workaround what i've described above .. thanks and regards by daniel -- 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#c8 Marius Tomaschewski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED CC| |mzugec@novell.com Resolution| |INVALID --- Comment #8 from Marius Tomaschewski 2010-01-15 12:12:12 UTC --- Honestly, don't kill with -9 (SIGKILL) unless you know what you're doing or don't complain later. Using kill -9 is *wrong*. The signals SIGKILL and SIGSTOP cannot be caught or ignored and dhcpcd can't do anything (no cleanup possible). When your really need to kill it manually, use dhcpcd -x interface (exit) and then dhcpcd -k interface (release lease). BTW: Reuse of the old lease (DHCLIENT_USE_LAST_LEASE="yes") has been enabled by default to make it consistent with ISC dhclient and to be RFC conform. (In reply to comment #6)

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.