RedHat /Implicit/default connection(s)

[Thomas HUMMEL]

On 4/26/24 13:15, Thomas HUMMEL wrote:

> You're right, some profile would need to preexist.

It seems that the 'System <interface>' naming scheme comes from an 
ifcf-<interface> file which is omitting the 'NAME=' field.

I still don't understand what is creating this ifcfg-<int> from an empty 
image NM-profile-wise.

dracut --list-modules outputs both legacy and NM modules so I'm not sure 
(and don't know how to check it) which one is actually called.

Besides, my understanding is that either way, some parameters (like at 
least dhcp) would need to be passed on cmdline. So unless iPXE is able 
to do that (appending network config to cmdline) I still quite confused.

Thanks for your help

-- 
Thomas HUMMEL
> 
> I can rule out persistent info in /run as by nature my nodes are 
> stateless so nothing gets persisted.
> 
> Actually from notes I took from a previous thread here long time ago I 
> understood that profile auto-creation could happen in the following cases:
> 
> 1. some blutooth and wifi cases
> 2. eth device non matched by no-auto-default : temporary profile (the 
> but with mac recorded somewhere in order not to re-create it if temp 
> profile is deleted
> 3. externally configured deviced : not managed but a profile gets 
> created to reflect this external state
> 4. if someone issues a device connect and no matching profile is found : 
> this case beeing considerd a "false" autoactivation as it was initiated 
> somehow by the client.
> 
> I think:
> 
> 2. is the Wired #1 case ?
> 3. would match for instance a device manually configured by ip add <dev> 
> command for instance and NM corresponding auto-created profile would be 
> named with the interface name, not System <int> ?
> 4. What would be the profile name ?
> So, if I sum up, I could see no case where a profile named 
> icfg-<interface-name> would be autocreated by NM, correct ?
> 
> I have as you say to increase log level now to sort it out
> 
> Thanks for your help
>