Re: persistent name from ifcfg-internal

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 12/11/18 12:54 PM, Rick Stevens wrote:
On 12/11/18 8:52 AM, sean darcy wrote:
On 12/11/18 12:54 AM, Samuel Sieb wrote:
On 12/10/18 4:22 PM, sean darcy wrote:
I'm trying to get the interface on a multi-homed machine named
"internal"

ifconfig
enp1s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
          ether 50:7b:9d:0b:8a:ab  txqueuelen 1000  (Ethernet)

Is that the full ifconfig output for that interface or does it have
the right IP address as well?

I haven't connected the port yet. Before I do I need to make sure I've
got the correct internet name.

That's the device (ethernet port) name, NOT the host name. The host name
is controlled by the contents of the /etc/hostname file, which is read
at boot time and sets the FQDN (fully qualified domain name) of the
machine.

That was fat finger syndrome. I meant interface name !

The stuff in the /etc/sysconfig/network-scripts/ifcfg-* files (and NM's
configurations) control how the interfaces themselves are configured
and do not affect the hostname of the machine.

As I understand, NM scans the ifcfg files for HWADDR's. If there's a
match, it names the interface the DEVICE name.

I believe NM uses the DEVICE _or_ the HWADDR to set up the interface.
Whichever one matches the hardware config first is what gets used (I'm
not sure which has precedence). And don't be confused...the values in
the NM config are only used to match the hardware.

And in answer to your second message, NM doesn't do any renaming of
devices. That's still done by the udev rules.

If so, why doesn't the udev rule work ? But I think nm now does device renaming:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/networking_guide/sec-understanding_the_device_renaming_procedure

sean

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux