On Wed, 2014-08-13 at 18:55 -0700, Marcel Holtmann wrote:
Hi Lennart,
Now that networkd can send the systems hostname to the dhcp server, I
would find it useful to have an option to override the hostname that gets
sent.
In my use case, I would like to setup a number of macvlans
Hi Dan,
Now that networkd can send the systems hostname to the dhcp server, I
would find it useful to have an option to override the hostname that gets
sent.
In my use case, I would like to setup a number of macvlans with different
hostnames.
Something as simple as
[DHCP]
Typically the send-hostname thing is actually used for DNS updates,
where you send the hostname to the DHCP server, which then gives you a
lease and sends the hostname + IP to the DNS server, so that your
machine is accessible via DNS automatically. I've never heard of it
being used as a
On Thu, 2014-08-14 at 14:29 -0700, Thomas Suckow wrote:
Typically the send-hostname thing is actually used for DNS updates,
where you send the hostname to the DHCP server, which then gives you a
lease and sends the hostname + IP to the DNS server, so that your
machine is accessible via DNS
It's used as a general identifier of the client in any situation, so
that the server can pass back specific options. Yes, this can be done
by looking at the client MAC address, but that's not sufficient in the
following cases:
1) non-Ethernet hardware addresses
2) dual-stack clients using
On Thu, 24.07.14 09:53, Thomas Suckow (thomas.suc...@pnnl.gov) wrote:
Now that networkd can send the systems hostname to the dhcp server, I would
find it useful to have an option to override the hostname that gets sent.
In my use case, I would like to setup a number of macvlans with
Hi Lennart,
Now that networkd can send the systems hostname to the dhcp server, I would
find it useful to have an option to override the hostname that gets sent.
In my use case, I would like to setup a number of macvlans with different
hostnames.
Something as simple as
[DHCP]
