[opensuse-factory] Strange hostname behaviour
Hello, I've got a problem with my hostname (I mean the one that can be seen at the default prompt or as the standard output of the "hostname" command). When I installed Tumbleweed, back in december 2015, it was the default hostname, as defined during the installation process. Strangely, in september or october, it became "minidlna". When I modify it (from Yast or from command line), it seems to work but when I reboot it is again minidlna. I have minidlna installed, but since the beginning! When I deactivate the network services, I can modify the hostname and it stays what I asked. But when I reactivate the network and then reboot, it is minidlna again. Having the minidlna activated at boot or not doesn't change anythin. Yesterday, I used a plugin of Foobar2000 (it works fine with wine) as a UPNP control point to send music to an external device… since then my hostname is foobar2000renderusernameminidlna (where username stands for my actual username). What can I do about that? It is an intended behaviour or a bug? Thank you. PA -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Sorry, I forgot to mention two important points: - I use wicked and not NetworkManager - the content of /etc/hostname is not affected (ie, it is always what I defined, even after multiple reboots… so yes, the hostname command *doesn't* return the content of /etc/hostname). Le 15/11/2016 à 11:58, Pierre-Amiel Giraud a écrit :
Hello,
I've got a problem with my hostname (I mean the one that can be seen at the default prompt or as the standard output of the "hostname" command).
When I installed Tumbleweed, back in december 2015, it was the default hostname, as defined during the installation process.
Strangely, in september or october, it became "minidlna". When I modify it (from Yast or from command line), it seems to work but when I reboot it is again minidlna. I have minidlna installed, but since the beginning! When I deactivate the network services, I can modify the hostname and it stays what I asked. But when I reactivate the network and then reboot, it is minidlna again. Having the minidlna activated at boot or not doesn't change anythin.
Yesterday, I used a plugin of Foobar2000 (it works fine with wine) as a UPNP control point to send music to an external device… since then my hostname is foobar2000renderusernameminidlna (where username stands for my actual username).
What can I do about that? It is an intended behaviour or a bug?
Thank you.
PA
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday 2016-11-15 12:08, Pierre-Amiel Giraud wrote:
Sorry, I forgot to mention two important points: - I use wicked and not NetworkManager - the content of /etc/hostname is not affected (ie, it is always what I defined, even after multiple reboots… so yes, the hostname command *doesn't* return the content of /etc/hostname).
/etc/sysconfig/network/dhcp: *SET_HOSTNAME* possibly a change in your router which now gives you that name. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Nov 15 2016, Jan Engelhardt
On Tuesday 2016-11-15 12:08, Pierre-Amiel Giraud wrote:
Sorry, I forgot to mention two important points: - I use wicked and not NetworkManager - the content of /etc/hostname is not affected (ie, it is always what I defined, even after multiple reboots… so yes, the hostname command *doesn't* return the content of /etc/hostname).
/etc/sysconfig/network/dhcp: *SET_HOSTNAME*
Note that DHCLIENT_SET_HOSTNAME is now a per-interface setting in /etc/sysconfig/network/ifcfg-*. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2016-11-15 11:58, Pierre-Amiel Giraud wrote:
What can I do about that? It is an intended behaviour or a bug?
It looks like you are using dhcp, and the dhcp server is telling you the machine name to use. You can allow this or disallow. It should be a tickbox in YaST. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Yes, that was it! Thank you (all of you) very much. I didn't know it was possible… Maybe I allowed it by mistake. PA Le 15/11/2016 à 14:04, Carlos E. R. a écrit :
On 2016-11-15 11:58, Pierre-Amiel Giraud wrote:
What can I do about that? It is an intended behaviour or a bug? It looks like you are using dhcp, and the dhcp server is telling you the machine name to use. You can allow this or disallow. It should be a tickbox in YaST.
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, 2016-11-15 at 11:58 +0100, Pierre-Amiel Giraud wrote:
Strangely, in september or october, it became "minidlna". When I modify it (from Yast or from command line), it seems to work but when I reboot it is again minidlna.
I suspect that this is related to mDNS in some way, like this: minidlna
announces its service in the LAN under the name "minidlna", your router
receives it and (wrongly) takes this as the host name, then sends it
back to your host at the next DHCP request ... or so.
I'd check my router configuration in the first place. Then I'd check
the DHCPREQUEST packets and the leases given out by the router, and
maybe check the mDNS status (avahi-browse -a). If all else fails,
you'll need to monitor DHCP/DNS and mDNS traffic with wireshark.
Martin
--
Dr. Martin Wilck
participants (5)
-
Andreas Schwab -
Carlos E. R. -
Jan Engelhardt -
Martin Wilck -
Pierre-Amiel Giraud