Bug 404663

hello, 

hmm I am not sure if I realy understand your problem but I think this is not a bug.
DHCP client update only ip adress and dns servers in /etc/resolv.conf where are DNS servers which you use for resolving hostnames. 

It doesn't update any record in bind zones informations.

Hello Robert,

    Thanks for looking into this with me. I agree with your statement about /etc/resolv.conf, but disagree about your conclusion regarding whether there is a bug. The /etc/resolve.conf is:

13:44 acrp205d~> cat /etc/resolv.conf
nameserver 192.168.6.17
search 3111skyline.com


    Specifically, since SuSE 8.0 pro, I have run servers with BIND configured to accept dynamic updates from dhcpd to update the forward and reverse zones. See:

/usr/share/doc/packages/dhcp-server/DDNS-howto.txt included in the 11.0 dhcp-server documentation.

<quote>

Short outline of how things work together:
  - DHCP clients send their preferred hostname along the request
  - dhcpd acknowledges the lease
  - dhcpd contacts named, asking it to update the zone, using an HMAC-MD5 key
    (TSIG, short for transaction signature) for authentication
  - named updates the zone (and rewrites the zone files periodically)
  - when the lease times out or is freed, named will remove it

</quote>

That is what is broken for 11.0 clients, whatever you call it. For some reason in the dhcp transaction with 11.0 clients, the zone files are not updated with the client preferred hostname and IP.

    For the above server "nirvana" it servers roughly 4-Win XP, 3-openSuSE 10.3, 1-vista and 1-opensuse 11.0 client. Every client except the 11.0 client properly cause the BIND zones to be updated with the preferred hostname and IP. For some reason the 11.0 client will not do this. That is the bug. It doesn't matter whether the 11.0 client establishes the connection via eth0 or wirelessly with ath0, the result is the same.

    Let me know what else I can send. Thanks.

sorry, forgot to change the status...

I have the same problem. After upgrading a client to 11.0 DynDNS on the server (10.3) was not working any more.

I found out that dhclient doesn't send the hostname during DHCPREQUEST. My DHCPD does not send a hostname to the clients (via setting a ddns-hostname) and so it has no hostname to update the zone.

There is an option in Yast -> Network settings -> General -> DHCP Client -> Hostname.
This option was set to AUTO, but even setting the hostname there does not help.

There is a forum post related to the problem: http://forums.opensuse.org/network-internet/387180-hostname-issues.html

They found a workaround by setting:
send host-name "computername";
in /etc/dhclient.conf.

It seems to me that the mentioned option in Yast does nothing at all.

from log:
Jun 25 22:08:46 acrp205d rcnetwork: Starting the NetworkManager
...

reassigned to NetworkManager maintainer

Confirmed here as well with 32-bit version of openSUSE 11.0. Version 10.3 worked fine.

Hello,

Not sure if my problem is related to the above bug. Am using the x86 (32-bit) version of openSUSE 11 & the following relates to that. 

The problem is as follows- (mentioned between the "=====" lines for
sake of clarity-
===============================================================================

On openSUSE 11.0 with updates (as of 27 Aug 08), the net connection using a DSL Router connected through a USB port (detected as eth1: TI NDIS USB Device, where TI = Texas Instruments) worked fine till now (installed a week ago) ; but by error I altered the connection settings to include DHCP (i.e. obtain DNS Name addresses via DHCP). Now, I cannot configure it connect using a static IP & using the DNS Servers that the ISP provides.

Now, the 'Update DNS data via DHCP' box remains checked (it is greyed out, as seen in the picture) & I cannot connect to the web. The screenshot is that of the Yast Network Configuration screen with the error is here -

http://lvznow.bay.livefilestore.com/y1p8roNEK4Ir1jpwshCeT66N06PsZGI5uIOHrNuoq7VAGwRfbcwHxg2Xrz2rIIcTYgg4mAY4olQsvo/Screenshot-Network%20Settings%20-%20YaST_28Aug08.jpg

I have a feeling that if I can get rid of the DHCP-enable option (the grayed-out button in the pict in url above), then after changing to static IP & DNS (ie I would enter them manually from provided by ISP), it would resolve the problem, since the past week, I had net access with the static IP option).  Any suggestions/further steps on how to resolve this?

PS:
- On shutting down the system yesterday, there was a message stating
the eth1 (TI NDIS USB Device) connection was not detected/changed &
that I should file a bugzilla report. It scrolled out too fast for to
note the exact message.

- I have not added any additional hardware or made any significant
system changes other checking the DHCP one (obtain IP Address & update
DNS address via DHCP) by mistake; that I can't seem to reverse now.

- eth0 is the inbuilt ethernet card (mcp73) of the mainboard (nvidia 610i chipset). I do not use this for networking or connecting to the net.
================================================================================

Thanks,

In 11.1 Beta3 I still need to set send host-name "computername"; in /etc/dhclient.conf.

Can this be fixed by RC1?

> In 11.1 Beta3 I still need to set send host-name "computername"; in
> /etc/dhclient.conf.

You can do that - go to NM's connection editor, choose the connection, click edit, go to "IPv4 Settings" tab and specify the host name in "DHCP Client ID" field.

(In reply to comment #9 from Tambet Ingo)
> > In 11.1 Beta3 I still need to set send host-name "computername"; in
> > /etc/dhclient.conf.
> 
> You can do that - go to NM's connection editor, choose the connection, click
> edit, go to "IPv4 Settings" tab and specify the host name in "DHCP Client ID"
> field.

No, this doesn't work.

"send dhcp-client-identifier" is not the same as "send host-name".  And according to the dhclient.conf that network manager generates it is sending a dhcp-client-identifier <value of DHCP Client ID box>.

Ah right, my mistake. You can configure "send host-name" directly in /etc/dhclient.conf file (as comment #4 already suggests). NM will overrider the "send dhcp-client-identifier" from that configuration file with the value from connection editor (if set), but all the other variables are still used.

What do you think of an idea of always using "send host-name" when static hostname is used? Would it produce any side effects?

(In reply to comment #11 from Tambet Ingo)
> What do you think of an idea of always using "send host-name" when static
> hostname is used? Would it produce any side effects?

I think this is reasonable. 

You may consider informing users that setting the hostname will cause the hostname to be advertised via DHCP. 

Or, just have a checkbox in the network manager to enable sending of the current /etc/HOSTNAME.

Thanks, Brandon

At some point (probably following an update to 11.0), the workaround described in comment #4 stopped working for me. The send host-name directive still appears in my /etc/dhclient.conf file, but it no longer seems to have an effect. Have others noticed this?

There hasn't been any NM updates for 11.0.

(In reply to comment #13 from Rob Hasselbaum)
> appears in my /etc/dhclient.conf file, but it no longer seems to have an
> effect. Have others noticed this?

Yes. Inspecting active processes with ksysguard, I found dhclient and its commandline: 
"/sbin/dhclient -d -sf /usr/lib/NetworkManager/nm-dhcp-client.action -pf /var/run/dhclient-eth0.pid -lf /var/run/dhclient-eth0.lease -cf /etc/dhclient-eth0.conf eth0"

No option -H <hostname>, and I couldn't figure out where this commandline was assembled. Then I noticed that a configfile is used per interface. I created therefore a config for both my interfaces (eth0 and wlan0). This solved the problem. At least for now.

(In reply to comment #15 from Caspar Maessen)
> Then I noticed that a configfile is used per interface. I created
> therefore a config for both my interfaces (eth0 and wlan0). This solved the
> problem. At least for now.

Ahh, thanks. Yes, I created /etc/dhclient-eth0.conf and /etc/dhclient-wlan0.conf containing only the send host-name directive and it works again. It will be nice to get this fixed for real in 11.1, though.

(In reply to comment #16)
> (In reply to comment #15 from Caspar Maessen)
> > Then I noticed that a configfile is used per interface. I created
> > therefore a config for both my interfaces (eth0 and wlan0). This solved the
> > problem. At least for now.
> 
> Ahh, thanks. Yes, I created /etc/dhclient-eth0.conf and
> /etc/dhclient-wlan0.conf containing only the send host-name directive and it
> works again. It will be nice to get this fixed for real in 11.1, though.

Should this become a FATE request for 11.2?

Cheers, Brandon

I'm having the same problem on 11.1 and none of the workarounds work, nor adding 'send host-name "computername";' to /etc/dhclient.conf neither creating a file called /etc/dhclient-wlan0.conf with the previous content.

Is this bug going to be solved?
Or is there another workaround?
Can I help somehow with more info?

This bug is now almost one year old! 8(

Thanks, Richard


openSUSE 11.1 64 bit
kernel-default-2.6.27.21-0.1.2
NetworkManager-0.7.0.r4359-15.2.2
dhcp-client-3.1.1-6.4.1

As the previous poster I can confirm that it is indeed not working on 11.1.
I'm happy to provide more info if needed.


Regards Harry

It should be works fine in 11.2 or 11.3.

David,

 It's a long time for this bug, could you try it in 11.2 or 11.3?

Noresponse. Feel free to contact me if any issue.

I can confirm that this bug is still present in 11.2 and 11.3.

Ian,

 So could provide more debug info about it, let's focus it in 11.3? Which mode do you use ifup or NetworkManager? And if with ifup, please attach the /var/log/messages, and also the /var/lib/dhcpd/*, if with NetworkManager, please attach the /var/log/NetworkManager, and also the /var/lib/dhclient/*

 Thanks!

I use NetworkManager. The bug is not present with ifup AFAIK.

The workarounds I've seen involve adding a 'send host-name "myhostname"' line to /etc/dhclient.conf (or /etc/dhclient-eth0.conf, or /etc/dhclient-wlan0.conf, or ...). I added the line to /etc/dhclient.conf and the DHCP server gets my hostname and sets DNS accordingly.

I'm assuming that 10.3 and earlier used the '-H hostname' option to dhclient to specify the hostname, and 11.0 and later don't.

I am attaching my /var/log/NetworkManager, with a mix of connecting to various networks by wired and wireless ethernet. I have no /var/lib/dhclient on my system.

Created attachment 392615 [details]
/var/log/NetworkManager

From the Comment#28, it should be same with bnc#557720.

Ian ,
I've make a patch for this, could test it?

http://download.opensuse.org/repositories/home:/BinLi:/branches:/openSUSE:/11.3:/Update:/Test/standard

The SWAMPID for this issue is 41130.
This issue was rated as low.
Please submit fixed packages until 2011-06-23.
Also create a patchinfo file using this link:
https://swamp.suse.de/webswamp/wf/41130

Done.

 71598  State:new     By:BinLi        When:2011-05-27T07:49:22
        submit:       home:BinLi:branches:openSUSE:11.3:Update:Test/NetworkManager  ->  openSUSE:11.3:Update:Test   
        Descr: send dhcp-hostname to server by default(bnc#404663,swampid#41130)

This is an autogenerated message for OBS integration:
This bug (404663) was mentioned in
https://build.opensuse.org/request/show/71598 11.3 / NetworkManager

update released

Update released for: NetworkManager, NetworkManager-debuginfo, NetworkManager-debugsource, NetworkManager-devel, NetworkManager-doc, NetworkManager-glib, NetworkManager-glib-debuginfo, NetworkManager-lang
Products:
openSUSE 11.3 (debug, i586, x86_64)
openSUSE 11.4 (debug, i586, x86_64)