Starting WiFi i/f messed up

[philip]

After a number of updates to my WiFi set up and the latest emerge -uDN @world starting my Wifi seems messed up

I use

[eccerr0r]

If you use NetworkManager, /etc/conf.d/net isn't actually used, and wpa_supplicant config is handled by NetworkManager. You should not have the link in /etc/init.d/net.wlXXXX -> net.lo as you'll not be using this, and rc-update delete net.wlXXXX from startup.

For NetworkManager you'll need to make sure in the applet or nmtui or whatever that you have a connection that's marked as "automatically connect" and "available to all users".

If you don't want to use NetworkManager you should disable it.
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?

[philip]

This, at least made one difference:
System tray Networks -> Configure Network Connection -> Chosing <name-of-SSID> -> Connection name -> Ticking "All users may connect to thois network" .
Now my WiFi is automatically connected after boot. It is a bit strange, since I previously used the "Advanced..." option and put my username in the right pane as the one user that: "Users allowed to activate the connection". This option should work, but obvioulsy do not.

I removed /etc/conf.d/net which confirms it is not needed,

I still have the error messages in the boot sequence though.

About

[eccerr0r]

NetworkManager is a service that lets users to manipulate network settings. Typically networks is a root-only task. With today's laptops and mobile devices, it gets kind of silly having to su to root every time you migrate to another network, and nm-applet and networkmanager lets you do it seamlessly and via a GUI. No, NetworkManager is not "necessary" but you'll lose out on the convenience on machines that you switch networks often. If you want to run nm-applet, which is the GUI, yes you do need the underlying networkmanager.

Yes you need "all users" because during boot time, nobody is logged in, and the system is not allowed to connect to the network...at least that's the theory behind why allowing all users is necessary.

I think /etc/conf.d/net should be a skeleton file, having it there does not affect the system.

I don't know why you have the /etc/init.d/net.enp0s25 and net.wlp3s0 files. Those links are typically user generated and I don't know of any scripts that would automatically populate them. They are OK to remove, though you should disable them from openrc first:

# rc-update del net.wlp3s0
# rc-update del net.enp0s25

After running these you shouldn't see the errors anymore without removing the links.
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?

[philip]

Thanks a lot for exhaustive feedback and tips.

I definitely need the convenience Networkmanager brings, since I travel extensively and wish to be able to connect to a vast number of WiFi networks in hotels, conference rooms and offices.

The /etc/init.d/net.enp0s25 and net.wlp3s0 files are still a mystery. It may be that I followed this reference when I configured my Wireless (see the lines just before the "Gentoo configuration" heading):

http://gentoo-en.vfose.ru/wiki/Wireless/Configuration

If I do # rc-update show and # rc-status before I attempt to remove the /etc/init.d/net.enp0s25 and net.wlp3s0 symlinks I get:

# rc-update show

[eccerr0r]

Actually, NetworkManager handles your wpa_supplicant for you - you don't need to muck with wpa_supplicant config files at all. But when not using NM, yes, wpa_supplicant does support multiple networks by adding multiple entries.

Hmm. I have not experimented much with automatic configuration. For me, most things are done manually. I might have to run a fresh stage 3, as the behavior you're seeing doesn't seem to exist in my older installations. Yes, rc_hotplug="*" is probably causing the problem you're seeing. You should try rc_hotplug="!net*" to disable network autoconfig.

And yes, the documentation can be confusing if you're not sure what the options are - and it sort of requires you to use both if you eventually want to use NM. My take on how to install Gentoo:

1. During initial bootstrap/install, you have to follow the original OpenRC "manual" configuration with wpa_supplicant config if you don't have Ethernet to download the Stage 3 install.

2. However once you get into the chroot you have to take a step back and make a decision:

a) If your machine is fairly static, doesn't move much - or you like su root and mucking with the wifi config that way - you can continue to use the "manual" configuration and repeat the steps done in step 1.

b) if you want dynamic configuration via GUI you have a choice (but not really that much of one)...
If you're using a simple windowmanager you could optionally use wicd and configure you network as in step a.
If you're using a desktop environment that supports nm-applet you would install NetworkManager.

Since you're in a chroot you're using the net config in step 1, and would continue to do the install with the already configured network, as you need to download packages.

3. When you're done with the chroot and boot onto your real root disk, now NetworkManager or OpenRC manual config will take effect. Chances are, OpenRC should start up fine. NetworkManager will require you to boot into the GUI and make configuration (or use the nmcli tool) so that your network comes up.
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?

[necktwi]

I'm facing similar problem with RTL8188CUS.

[charles17]

[necktwi]

yes, I do have /sys/class/net/wlp0s29f7u4.