thanks jetchisel! I understand that the existence of multifunctional pci devices forced a new and much complex nomenclature. A superficial code inspection shows how names are constructed, however everything is explained on the begin as comment.I understand that anyway I couldn’t build more appropriate names. And so what now? Should we all live with devilspie + xdotool on startup, or look for other distributions where the network manager snaps correctly the wireless new names? Well, I have a backup from the initial installation stage with no wlan configuration. Don’t think badly about such backups, I am very suse confiant, I use suse as my OS since 9.3: but you know certainly that then we had to load into the kernel windows wireless drivers :’(
Well, I will also take a look on kubuntu and I will let you know. Tanks again.
OK, now everything seems to work!
Like already written, I have a backup from my raw install. This time (fourth attempt!) my wifi installed properly, and also my lan. I called them respectively Geraldine and Daphne.
Of course only in my head lol!
I didn’t do anything of special, just plain install. With the wifi properly installed also vmnet0 installed properly and subsequently the bridged connection. The problem was by my provider: they were making the maintenance and during a couple of days the wlan was coming and going: mostly I was providing the passfrase and the wifi was instead dead!
Again thanks for your help, it made me possible to understand immediately what was going on.
Since the introduction of systemd 197 the default policy will now name interfaces based closer to kernel-internal device identification schemes.
The following different naming schemes for network interfaces are now supported by udev natively:
Names incorporating Firmware/BIOS provided index numbers for on-board devices (example: eno1)