wlan0 work in kde plasma but not in fvwm

English Network/Internet
1

I am just lost with the network config. It is a laptop and the most important connection is the wifi. In Yast, it use the Network manager. The default desktop is kde plasma. I succeeded to configure it and it work fine. The hardware is:

lspci
...
04:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 01)

When I logout plasma and login in fvwm, the network stop to work.

If I completely stop the network in Yast and with the following /etc/wpa_supplicant/wpa_supplicant.conf

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
update_config=1

network={
        ssid="HUAWEI-846B"
        psk="a490y1dn"
        proto=RSN
        key_mgmt=WPA_PSK
        pairwise=CCMP
        auth_alg=OPEN
}

and after running

wpa_supplicant -Dwext  -iwlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf

I get a connection but no ip. wpa_gui see wlan0, is able to scan the network, I can change the configuration, it connect but get no ip.

If I keep that conf file as it and go back in plasma, the network manager is not able to use that connection anymore. I must restore the wpa_supplicant config file in its original state and restart the Network Manager for that.

I also try to configure wicked with yast, it show no error message but the network is just dead. It is so many thread talking about similar issue that I am just lost. How can I configure that wlan0 in order to get connected at boot time and be able to use wpa_gui in any desktop I want to use?

2

I had a similar problem with LXQt but I found that checking the button in the Wi-fi settings to allow all users to access it in Plasma solved the problem. You still have to log in to Plasma after booting and give the root password and the kwallet password - ignore the fearsome messages about system rules - before you log in elsewhere. But it works fine for me (I tried to get wicked to run on LXQt without success before trying this).

3

I find a solution. It is to install stalonetray, run it in fvwm, and run nm-applet.:wink:

So now I can focus on how I want fvwm to look and feel.