Thank you for the idea,
unfortunately, when old-style-names are used, the MAC/name mappings are
saved in /etc/udev/rules.d/70-persistent-net.rules, so replacing NICs or
cloning installations results in increasing numbers, eth0, eth1, eth2,
... eth10.
Cheers,
Alkis
On 6/17/21 4:56 PM, B. Coo
Would this help as well?
kernel parameter: net.ifnames=0
https://man7.org/linux/man-pages/man8/systemd-udevd.service.8.html
net.ifnames=
Network interfaces are renamed to give them predictable names
when possible. It is enabled by default; specifying 0
disa
On 16/06/2021 09:10, Alkis Georgopoulos wrote:
> Hi, from the dnsmasq man page:
>
>> The special address 0.0.0.0 is taken to mean
>> "the address of the machine running dnsmasq"
>
> This is for DHCP.
> Can I do the same for DNS queries, in some way?
> So that I could map "webserver" to the dnsmas
If I'm reading this correctly, it needs an extra step, to discover and
list all the interfaces, both after the initial installation and after
cloning and after motherboard/NIC replacements, e.g.
interface-name=webserver,enp2s0
interface-name=webserver,enp4s0
interface-name=webserver,enp5s0
It
Hi, from the dnsmasq man page:
> The special address 0.0.0.0 is taken to mean
> "the address of the machine running dnsmasq"
This is for DHCP.
Can I do the same for DNS queries, in some way?
So that I could map "webserver" to the dnsmasq IP,
and DNS clients would be able to bookmark and use http
