Many thanks Thomas - very helpful.
On 23/07/2021 20:42, Thomas Haller wrote:
On Fri, 2021-07-23 at 17:24 +0100, Mark Corbin wrote:
Hello
I'm trying to control a device hostname independently of
NetworkManager,
but am unable to disable NetworkManager's hostname management. I'm
u
On Fri, 2021-07-23 at 17:24 +0100, Mark Corbin wrote:
> Hello
>
> I'm trying to control a device hostname independently of
> NetworkManager,
> but am unable to disable NetworkManager's hostname management. I'm
> using
> NM version 1.28.2
>
> I'v
Hello
I'm trying to control a device hostname independently of NetworkManager,
but am unable to disable NetworkManager's hostname management. I'm using
NM version 1.28.2
I've added the following to the configuration file:
[main]
hostname-mode=none
When NM starts at boot
On Wed, 2021-01-20 at 08:00 +0100, Thomas Haller wrote:
> On Tue, 2021-01-19 at 17:44 -0700, Kevin Locke via networkmanager-list wrote:
>> Perhaps this is because the property does not support having a default
>> value configured, as it is not listed in NetworkManager.conf(5)
>> (although the error
On Tue, 2021-01-19 at 17:44 -0700, Kevin Locke via networkmanager-list
wrote:
> Hi All,
>
> I'm trying to make a device which frequently roams between untrusted
> wireless networks (in non-pandemic times) less easy to uniquely
> identify
> by not sending the hostname in DHC
Hi All,
I'm trying to make a device which frequently roams between untrusted
wireless networks (in non-pandemic times) less easy to uniquely identify
by not sending the hostname in DHCP requests (in addition to other
measures like MAC address randomization). It seems that this c
On 4/27/20 7:54 PM, Thomas HUMMEL wrote:
What do you think ?
Hello,
I thinks this is related to this
https://github.com/systemd/systemd/pull/15624
prompted by the following thread I opened :
https://lists.freedesktop.org/archives/systemd-devel/2020-April/044395.html
Thanks for your help
-
On 4/27/20 7:05 PM, Thomas HUMMEL wrote:
hostname(1) change the transient/kernel hostname but as
systemd-hostnamed does not poll /proc/sys/kernel/hostname (which was
confirmed to my in the systemd-devel list) for a change, this out-of-NM
set hostname is not seen by NM, which then restores
On 4/27/20 5:34 PM, Thomas HUMMEL wrote:
On 4/27/20 5:20 PM, Beniamino Galvani wrote:
It uses systemd-hostnamed, and falls back to gethostname() in case of
failure [1].
I should then try to remove hostnamed just to figure out why in
1) hostname from initrd : fqdn
2) NM starts : hostname
On 4/27/20 5:20 PM, Beniamino Galvani wrote:
It uses systemd-hostnamed, and falls back to gethostname() in case of
failure [1].
I should then try to remove hostnamed just to figure out why in
1) hostname from initrd : fqdn
2) NM starts : hostname-originial == fqdn
3) dhcp : short name
4) an
On 4/27/20 5:22 PM, Beniamino Galvani wrote:
Still the hostnamectl delay is a thing unexplained to me.
I don't know the cause of the delay, it didn't expect it.
Ok. Thanks again.
--
TH.
___
networkmanager-list mailing list
networkmanager-list@gno
On Mon, Apr 27, 2020 at 11:35:47AM +0200, Thomas HUMMEL wrote:
> On 4/27/20 11:13 AM, Thomas HUMMEL wrote:
>
> > I notices that
> >
> > hostnamectl --static set-hostname
> >
> > behavior was not the same according to the value of hostname-mode setting :
>
On Wed, Apr 22, 2020 at 08:18:24PM +0200, Thomas HUMMEL wrote:
> Hello,
>
> using NetworkManager-1.20.0-5.el8_1.x86_64 on CentOS 8.1 I tried to figure
> out the hostname-mode semantics beyond what the manual says (I've got
> another thread for this but somehow unrelated to th
On 4/27/20 11:13 AM, Thomas HUMMEL wrote:
I notices that
hostnamectl --static set-hostname
behavior was not the same according to the value of hostname-mode setting :
- if set to 'none' : there's a delay for the transient hostname to be
automatically set to the manually
On 4/22/20 8:18 PM, Thomas HUMMEL wrote:
Hello,
using NetworkManager-1.20.0-5.el8_1.x86_64 on CentOS 8.1 I tried to
figure out the hostname-mode semantics beyond what the manual says (I've
got another thread for this but somehow unrelated to the following
question).
What's not c
Hello,
using NetworkManager-1.20.0-5.el8_1.x86_64 on CentOS 8.1 I tried to
figure out the hostname-mode semantics beyond what the manual says (I've
got another thread for this but somehow unrelated to the following
question).
In this post, I'd like to clarify this NetworkMana
gured out:
- the original hostname, which NM reads from dbus is indeed setup by
dracut/initrd/dhclient-scripts
a) when no postcsript adding a second NM manual profile is not run,
results and reasons are, as expected :
- hostname-mode == none : maestro-1000.maestro.pasteur.fr (original
maestro.pasteur.fr NetworkManager[25235]:
> > > [1586350409.2521] policy: get-hostname:
> > > "maestro-1000.maestro.pasteur.fr" (from dbus)
> > > Apr 08 14:53:29 maestro-1000.maestro.pasteur.fr NetworkManager[25235]:
> > > [1586350409.2521] policy: hostn
On 4/9/20 10:59 AM, Beniamino Galvani wrote:
alking about D-Bus, I see this in the begining of all 3 (default, none,
dhcp) traces :
Apr 08 14:53:29 maestro-1000.maestro.pasteur.fr NetworkManager[25235]:
[1586350409.2521] policy: get-hostname:
"maestro-1000.maestro.pasteur.fr" (from
On Thu, Apr 09, 2020 at 11:20:17AM +0200, Thomas HUMMEL wrote:
> On 4/9/20 10:59 AM, Beniamino Galvani wrote:
>
> > > how is this hostname fully qualified who sets it ? The original hostname
> > > always seems to be this one.
> >
> > I don't know, it is
On 4/9/20 10:59 AM, Beniamino Galvani wrote:
how is this hostname fully qualified who sets it ? The original hostname
always seems to be this one.
I don't know, it is set before NM starts.
Ok, I'll look into this but this is not related to my initial problem
indeed.
In the
On Wed, Apr 08, 2020 at 04:18:32PM +0200, Thomas HUMMEL wrote:
> Hello, thanks for your answer
>
> On 4/8/20 10:25 AM, Beniamino Galvani wrote:
>
> >> - step2 (I guess) puts HOSTNAME=maestro-1000 in /etc/sysconfig/network
> >
> > AFAIK, NetworkManager doesn'
On 4/8/20 4:18 PM, Thomas HUMMEL wrote:
>> b) : NM just don't play with the transient name and sets a static
hostname
>> coming from /etc/sysconfig/network
>
> NM sets the transient host name. It doesn't know about
> /etc/sysconfig/network. The hostname is d
Hello, thanks for your answer
On 4/8/20 10:25 AM, Beniamino Galvani wrote:
>> - step2 (I guess) puts HOSTNAME=maestro-1000 in /etc/sysconfig/network
>
> AFAIK, NetworkManager doesn't do that.
Although I saw that it was the postscript which wrote into this file, I
thought N
- something
> like 'maestro-1000') hostname or a fqdn hostname
> (maestro-1000.maestro.pasteur.fr). This is related to the process network is
> configured according to the following procedure :
>
> 1. node PXE boots the stateless osimage and ends up having a dhcp NM profile
&g
Hello,
I'm trying to figure out how exactly my stateless HPC nodes (CentOS
8.1/NetworkManager-1.20.0) get their hostnames.
As a matter of fact, they can either get a "short" (non fqdn - something
like 'maestro-1000') hostname or a fqdn hostname
(maestro-1000.mae
On Sun, 19 May 2019 10:55:52 +0200
Thomas Haller wrote:
> On Sat, 2019-05-18 at 21:08 -0500, Robby Workman wrote:
> > The attached patch can be applied to master and 1.12 branches.
> > It's specific to the hostname handling on Slackware, so it
> > sh
On Sat, 2019-05-18 at 21:08 -0500, Robby Workman wrote:
> The attached patch can be applied to master and 1.12 branches.
> It's specific to the hostname handling on Slackware, so it
> shouldn't affect anyone else.
>
Hi,
Merged to upstream.
Since the patch only affects S
The attached patch can be applied to master and 1.12 branches.
It's specific to the hostname handling on Slackware, so it
shouldn't affect anyone else.
-RW
>From 53676bdf67e1132df02b61416fe03027213afdcc Mon Sep 17 00:00:00 2001
From: "Patrick J. Volkerding"
Date: Mon, 13
On Sat, 19 Aug 2017 03:17:31 +
"Soule, Michael" wrote:
> The hostname configured for the interface network script is set. The
> proper hostname is shown when checking nmcli for the
> ipv4.dhcp-hostname option, the ipv4.dhcp-send-hostname, and when
> viewing t
The hostname configured for the interface network script is set. The proper
hostname is shown when checking nmcli for the ipv4.dhcp-hostname option, the
ipv4.dhcp-send-hostname, and when viewing the generated interface configuration
for send host-name option. With everything set and "dhc
they get their IP from the DHCP server and report their hostname
perfectly. This allows me to access the KVM's anywhere on my network
using just their hostname.
The issue is if my router reboots. The KVM's interface don't seem to
notice anything went down since they are beh
On Fri, 2016-04-22 at 20:49 -0500, Robby Workman wrote:
> On Slackware, the expectation is for output of "hostname" without
> options
> to be the same as "hostname --short" whereas "hostname --fqdn" would
> be
> used if the full hostname+domain is
On Slackware, the expectation is for output of "hostname" without options
to be the same as "hostname --short" whereas "hostname --fqdn" would be
used if the full hostname+domain is desired.
With NM-1.2.x, using persistent hostname setting and pulling it from
/et
GFileMonitor *hostname_monitor;
- guint hostname_monitor_id;
+ GDBusProxy *hostnamed;
char *hostname;
GFileMonitor *ifcfg_monitor;
guint ifcfg_monitor_id;
+ GDBusConnection *bus;
guint owner_id;
NMIfcfgRH *dbus_ifcfg;
} SCPlugin
On Tue, 2016-01-26 at 22:48 +, Joel Holdsworth wrote:
> If the hostname file is a symbolic link, follow it to find where the
> real file is located, otherwise g_file_set_contents will attempt to
> replace the link with a plain file.
> ---
Hi Joel,
patch v3 merged to ma
On Tue, 2016-01-26 at 22:48 +, Joel Holdsworth wrote:
> If the hostname file is a symbolic link, follow it to find where the
> real file is located, otherwise g_file_set_contents will attempt to
> replace the link with a plain file.
> ---
Ok, then it sounds like we should do th
On Wed, 2016-01-27 at 16:16 +, Joel Holdsworth wrote:
> - keyfile - not needed; at the moment we don't support any medium
> that
> needs a keyfile
> - /etc/NetworkManager/system-connections/ - sym-linked to
> /var/lib/NetworkManager/system-connections/
btw, "keyfile" plugin is always used
Thereby, it would also be interesting how you run NetworkManager with a
read-only /etc. Do you set keyfile.path configuration option?
Is the hostname thing your only remaining issue, or do you have other
issues NM and a read-only /etc? How does it work with handling
resolv.conf?
So at the
Hi Joel,
Hi
diff --git a/src/settings/nm-settings.c b/src/settings/nm-settings.c
index f6f8c37..fc2eb29 100644
--- a/src/settings/nm-settings.c
+++ b/src/settings/nm-settings.c
@@ -1532,11 +1532,11 @@ write_hostname (NMSettingsPrivate *priv,
const char *hostname)
char
If the hostname file is a symbolic link, follow it to find where the
real file is located, otherwise g_file_set_contents will attempt to
replace the link with a plain file.
---
src/settings/nm-settings.c | 13 +++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git a/src
On Mon, 2016-01-25 at 22:57 +, Joel Holdsworth wrote:
> If the hostname file is a symbolic link, follow it to find where the
> real file is located, otherwise g_file_set_contents will attempt to
> replace the link with a plain file.
> ---
> src/settings/nm-settings.c | 14
If the hostname file is a symbolic link, follow it to find where the
real file is located, otherwise g_file_set_contents will attempt to
replace the link with a plain file.
---
src/settings/nm-settings.c | 14 --
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/src
If the hostname file is a symbolic link, resolve the link until the
real file is located, otherwise g_file_set_contents will attempt to
replace the link with a plain file.
---
src/settings/nm-settings.c | 14 --
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/src
On Sat, 2015-05-02 at 19:54 +0200, Jan Heidbrink wrote:
> Hi,
>
> I found that my Ubuntu machine always sends its hostname when doing a
> DHCP request. I also found that for DHCP requests NetworkManager uses a
> config-file /var/lib/NetworkManager/dhclient-eth0.conf which is based
Hi,
I found that my Ubuntu machine always sends its hostname when doing a
DHCP request. I also found that for DHCP requests NetworkManager uses a
config-file /var/lib/NetworkManager/dhclient-eth0.conf which is based on
/etc/dhcp/dhclient.conf and then modified by NetworkManager.
One of these
> I've backported those patches to F20 for you, can you try:
>
> https://admin.fedoraproject.org/updates/NetworkManager-0.9.9.0-46.git20131003.fc20
>
> and let me know if it fixes the issue?
Thank you for building that package - unfortunately it doesn't work for
me (h
d these lines:
>
> >> DHCP_HOSTNAME=wont-be-used
> >> DHCP_SEND_HOSTNAME=no
>
> to
> /etc/sysconfig/network-scripts/ifcfg-
>
> Did anything change in this regard? How can I prevent hostname
> disclosure via DHCP requests nowadays?
I'm not quite sure why
work on a F20
now? (I upgraded from F19 -> F20).
I'm using:
NetworkManager-0.9.9.0-45.git20131003.fc20.x86_64
and added these lines:
>> DHCP_HOSTNAME=wont-be-used
>> DHCP_SEND_HOSTNAME=no
to
/etc/sysconfig/network-scripts/ifcfg-
Did anything change in
As every new SSID generates a new ifcfg-.. file, one additional question
came up:
Is there a way to make
"DHCP_SEND_HOSTNAME=no"
be in every new ifcfg- file by default?
(adding it after the fact it was created would be pointless since the
hostname would have been submitted alrea
s also given.
Hi Dan,
I'm sorry to bother you again but I still see the hostname (option 12)
on the wire: "wont-be-used" (instead of no hostname option).
NM version:
NetworkManager-0.9.8.8-2.fc19.x86_64
I tried it in my FC20 VM, there it works fine, I guess I have one more
reason
so I went
> ahead and added "DHCP_SEND_HOSTNAME=no" to
> /etc/sysconfig/network-scripts/ifcfg-
>
> (a WIFI connection)
>
> unfortunately I still see my hostname in the DHCP Request packets
> (wireshark).
> I even tried a reboot to see if this change requires a r
t to use "DHCP_SEND_HOSTNAME=no" in the ifcfg file for
> the connection in /etc/sysconfig/network-scripts/
/etc/NetworkManager/system-connections is an empty folder so I went
ahead and added "DHCP_SEND_HOSTNAME=no" to
/etc/sysconfig/network-scripts/ifcfg-
(a WIFI connection)
On Fri, 2014-01-03 at 22:59 +, Robert Horovitz wrote:
> Hi Dan,
>
> thanks for your reply.
>
> > If you're using 'keyfile' configuration files, you can add the line
> > "dhcp-send-hostname=false" to the [ipv4] block to prevent sending the
Hi Dan,
thanks for your reply.
> If you're using 'keyfile' configuration files, you can add the line
> "dhcp-send-hostname=false" to the [ipv4] block to prevent sending the
> hostname to the DHCP server. I don't believe it's exposed anywhere in
> t
orkManager/dhclient-em1.conf
>
> When that place in the source code is found,
> it is easy to remove it. ( easier as adding code to the right place )
If you're using 'keyfile' configuration files, you can add the line
"dhcp-send-hostname=false" to the [ipv4] block
> The (graphical) user interface of Network Manager
> has an option named 'DHCP client ID'
"dhcp-client-identifier" (option 61) has nothing to do with the
"host-name" (option 12). Your hint does not solve the problem.
___
networkmanager-list mailing l
Op 2013-12-23 om 20:33 schreef Robert Horovitz:
> > Mark in /etc/dhcp/dhclient.conf 'send host-name' as comment.
>
> Since the resulting file is created by merging /etc/dhcp/dhclient.conf
> into /var/lib/NetworkManager/dhclient-em1.conf that does not do the trick.
>
> The final file looks like:
>
> Mark in /etc/dhcp/dhclient.conf 'send host-name' as comment.
Since the resulting file is created by merging /etc/dhcp/dhclient.conf
into /var/lib/NetworkManager/dhclient-em1.conf that does not do the trick.
The final file looks like:
-
# Created by NetworkManager
# Merged from /etc/dhcp/dh
gt; Is it possible to configure networkmanager in a way that instructs
> dhclient to not send the hostname in DHCP requests to the DHCP server
> (option 12)?
>
> I tried to manually modify
> /var/lib/NetworkManager/dhclient-em1.conf
>
> to remove the "send host-name" line, but tha
Hi,
I'm a Fedora user and I asked this question before on the fedora-users
mailing list [1], but since I didn't get any response I wanted to ask
here - on a more specific mailing list - again.
Is it possible to configure networkmanager in a way that instructs
dhclient to not send the h
- Original Message -
> From: "Henri Wahl"
> Hello,
> is it possible to tell NetworkManager (0.9.6.4) to send the client
> hostname in its DHCPv6 solicit requests?
It has been for some time in master and will be delivered in 0.9.6.8. I don't
advise you to back
Hello,
is it possible to tell NetworkManager (0.9.6.4) to send the client
hostname in its DHCPv6 solicit requests? The underlaying dhclient has
this feature, so it might be easily used by NetworkManager too.
Regards
Henri Wahl
--
Henri Wahl
IT Department
Leibniz-Institut für Festkörper- u
I have my hostname set to a short name, because this is a laptop and will
move to different domains.
In /etc/hosts, I see:
10.32.112.220 nbecker1# Added by NetworkManager
127.0.0.1 localhost.localdomain localhost
::1 nbecker1localhost6.localdomain6 localhost6
Now
Salı 09 Kasım 2010 günü (saat 01:12:17) Robby Workman şunları yazmıştı:
>
> On the other hand, if your goal is to have a persistent hostname
> that never changes, then you want something like this:
>
> [rwork...@liberty ~]$ cat /etc/NetworkManager/NetworkManager.conf
> # /
On Mon, 08 Nov 2010 14:02:38 +
Roy Marples wrote:
> Hi
>
> I'm not on the list, but was CC'ed, so direct responses please.
> I'm also upstream author for dhcpcd.
>
> On 08/11/2010 13:45, Ozan Çağlayan wrote:
> > I'm really confused how the hostn
Hi
I'm not on the list, but was CC'ed, so direct responses please.
I'm also upstream author for dhcpcd.
On 08/11/2010 13:45, Ozan Çağlayan wrote:
I'm really confused how the hostname things are handled in NM. I'm trying to
understand looking through the code but I&#
On Mon, 2010-11-08 at 15:45 +0200, Ozan Çağlayan wrote:
> Should it update machine's hostname when I modify the hostname file?
cat /etc/sysconfig/network
NETWORKING=yes
HOSTNAME=segulix
on fedora you set hostname at /etc/sysconfig/network
--
Sérgio M. B.
smime.p7s
Description
Hi,
I'm really confused how the hostname things are handled in NM. I'm trying to
understand looking through the code but I'm completely lost as there are
methods which wraps methods which wraps methods, etc.
Here's the setup:
* NetworkManager 0.8.1
* DHCP client is dhcpcd
2010-06-14 at 23:16 +0300, Fırat Birlik wrote:
> > > > > > I experience a problem with hostname manipulation of
> > > > > > NetworkManager and the X session. DHCP server sends a
> > > > > > hostname within the dhcp offer, which is different the
>
On Tue, 2010-06-22 at 10:06 +0200, Ludwig Nussel wrote:
> Dan Williams wrote:
> > On Tue, 2010-06-22 at 09:14 +0200, Ludwig Nussel wrote:
> > > Dan Williams wrote:
> > > > On Mon, 2010-06-14 at 23:16 +0300, Fırat Birlik wrote:
> > > > > I exper
Dan Williams wrote:
> On Tue, 2010-06-22 at 09:14 +0200, Ludwig Nussel wrote:
> > Dan Williams wrote:
> > > On Mon, 2010-06-14 at 23:16 +0300, Fırat Birlik wrote:
> > > > I experience a problem with hostname manipulation of NetworkManager
> > > > and th
On Tue, 2010-06-22 at 09:14 +0200, Ludwig Nussel wrote:
> Dan Williams wrote:
> > On Mon, 2010-06-14 at 23:16 +0300, Fırat Birlik wrote:
> > > I experience a problem with hostname manipulation of NetworkManager
> > > and the X session. DHCP server sends a hostname
Dan Williams wrote:
> On Mon, 2010-06-14 at 23:16 +0300, Fırat Birlik wrote:
> > I experience a problem with hostname manipulation of NetworkManager
> > and the X session. DHCP server sends a hostname within the dhcp
> > offer, which is different the current one. T
On Mon, 2010-06-21 at 14:57 +0300, Fırat Birlik wrote:
> 2010/6/17 Dan Williams :
> > On Mon, 2010-06-14 at 23:16 +0300, Fırat Birlik wrote:
> >> Hi there,
> >>
> >> I experience a problem with hostname manipulation of NetworkManager
> >> and the X sess
2010/6/17 Dan Williams :
> On Mon, 2010-06-14 at 23:16 +0300, Fırat Birlik wrote:
>> Hi there,
>>
>> I experience a problem with hostname manipulation of NetworkManager
>> and the X session. DHCP server sends a hostname within the dhcp
>> offer, which is differ
On Mon, 2010-06-14 at 23:16 +0300, Fırat Birlik wrote:
> Hi there,
>
> I experience a problem with hostname manipulation of NetworkManager
> and the X session. DHCP server sends a hostname within the dhcp
> offer, which is different the current one. There is no persistent
> h
2010/6/14 Robby Workman :
> On Mon, 14 Jun 2010 15:26:06 -0500
> Robby Workman wrote:
>
>> On Mon, 14 Jun 2010 23:16:52 +0300
>> Fırat Birlik wrote:
>>
>> > Hi there,
>> >
>> > I experience a problem with hostname manipulation of Netwo
On Mon, 14 Jun 2010 15:26:06 -0500
Robby Workman wrote:
> On Mon, 14 Jun 2010 23:16:52 +0300
> Fırat Birlik wrote:
>
> > Hi there,
> >
> > I experience a problem with hostname manipulation of NetworkManager
> > and the X session. DHCP server sends a hostname
Hi there,
I experience a problem with hostname manipulation of NetworkManager
and the X session. DHCP server sends a hostname within the dhcp
offer, which is different the current one. There is no persistent
hostname definition within the 'nm-system-settings.conf' as this is
On Sun, 2010-01-31 at 15:10 +0800, cee1 wrote:
> Hmm, I wasn't expecting this sort of thing. I guess we need
> to
> monitor /etc as well to get events when the file gets added
> back or
> renamed to /etc/hostname. Any chance you
>
> Hmm, I wasn't expecting this sort of thing. I guess we need to
> monitor /etc as well to get events when the file gets added back or
> renamed to /etc/hostname. Any chance you could do a patch for that?
> There's some directory monitoring code in
> system-settin
On Fri, 2010-01-22 at 16:33 +0800, cee1 wrote:
> Hi all,
>
>
> It seems editing /etc/hostname with vim, the original /etc/hostname
> will be removed first, then the inotify watch is also removed. The
> following changes of /etc/hostname are detectable by
> nm-system-settin
Hi all,
It seems editing /etc/hostname with vim, the original /etc/hostname will be
removed first, then the inotify watch is also removed. The following changes
of /etc/hostname are detectable by nm-system-settings, unless restart it.
BTW, "*if (!(evt.mask & IN_IGNORED))*"
On Sunday 18 October 2009 11:59:59 Gene Czarcinski wrote:
> Unfortunately, in order to set these variables for the hostname, you
> currently need to use you favorite text editor such as vi. In the case
> of a system connection (a connection available to all users), you can use
> s
Gene Czarcinski a écrit :
> One of the things that can be done if you run a dhcp service and a dns
> service is that you can dynamically update the dns (named) for your
> hostname with the ip address assigned by dhcpd.
By the way DNS was not really designed to be "dynamic&qu
One of the things that can be done if you run a dhcp service and a dns service
is that you can dynamically update the dns (named) for your hostname with the
ip address assigned by dhcpd. If you run dnsmasq, it will also dynamically
update its dns with your hostname for the ip address supplied
On Wed, 2009-03-04 at 14:51 +0800, Bin Li wrote:
> Hi,
>
> NM support it or not?
Hmm, it appears not to. That's an oversight. The hostname doesn't get
from the DHCP handling code to anywhere else. NM *will* try to do
reverse-address lookup on your IP address if you have n
Hi,
NM support it or not?
Thanks!
Sincerely Yours,
Bin Li
http://cn.opensuse.org
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
From: Dan Williams
Subject: Re: setting network hostname for Auto eth0
Date: Fri, 30 Jan 2009 11:35:58 -0500
> On Fri, 2009-01-30 at 09:06 -0500, Peter F. Patel-Schneider wrote:
> > Hi:
> >
> > I'm having a minor problem getting network manager (0.7.0 under Fedora
On Fri, 2009-01-30 at 09:06 -0500, Peter F. Patel-Schneider wrote:
> Hi:
>
> I'm having a minor problem getting network manager (0.7.0 under Fedora
> 10) to set my network hostname when it automatically connects to a
> network.
Are you using different hostnames for differe
Hi:
I'm having a minor problem getting network manager (0.7.0 under Fedora
10) to set my network hostname when it automatically connects to a
network.
Using system-config-network, I can set
DHCP Settings:
Hostname (optional): x.y.z
for eth0 and then when I connect to System
of today (11/20). My networkmanager package version is
> "0.7~~svn20081018t105859-0ubuntu1", as reported by aptitude.
>
> So I start my computer up normally. The /etc/init.d/hostname script runs
> and sets my hostname to northbound, like it should be. Then,
> NetworkManager runs
9-0ubuntu1", as reported by aptitude.
So I start my computer up normally. The /etc/init.d/hostname script runs
and sets my hostname to northbound, like it should be. Then,
NetworkManager runs and changes it to localhost.localdomain. Boo. Here's
an example session that I set up to show
On Mon, 2008-10-06 at 17:27 +0200, Alexander Sack wrote:
> Implement system hostname support for debian/ubuntu
>
> Make nm-inotify-helper from ifcfg-fedora plugin usable
> for other plugins too
r4150 and r4151, thanks! (broke the inotify helper move into a separate
On Mon, 2008-10-06 at 17:38 +0200, Michael Biebl wrote:
> Alexander Sack wrote:
> > Implement system hostname support for debian/ubuntu
> >
>
> Will this automatically overwrite /etc/hostname, if you receive a
> hostname from dhcp?
No. It is persistent user-specified ho
Alexander Sack wrote:
> Implement system hostname support for debian/ubuntu
>
Will this automatically overwrite /etc/hostname, if you receive a
hostname from dhcp?
If so, this would be a bad idea imho.
If it would only be a D-Bus interface to *configure* the hostname when
explicitely req
Implement system hostname support for debian/ubuntu
Make nm-inotify-helper from ifcfg-fedora plugin usable
for other plugins too
=== modified file 'ChangeLog'
--- a/ChangeLog 2008-10-03 21:51:57 +
+++ b/ChangeLog 2008-10-06 08:22:23 +
@@ -1,8 +1,36 @@
+2008-10-03 Alex
Implement system hostname support for debian/ubuntu
Fix "only system-setting plugins with
NM_SYSTEM_CONFIG_INTERFACE_CAP_MODIFY_HOSTNAME
are considered a valid hostname provider"
Make nm-inotify-helper from ifcfg-fedora plugin usable
for other plugins too
- Alexander
=== mod
Dan Williams wrote:
On Thu, 2008-09-25 at 19:28 +0200, Alexander Sack wrote:
On Thu, Sep 25, 2008 at 05:23:17AM -0700, Howard Chu wrote:
I realize there are a lot of different use cases being targeted here, but
I don't believe that overriding a non-NULL current hostname is a good
beh
1 - 100 of 139 matches
Mail list logo
