As we are getting out of our lockdown, I had the chance to run some tests at our lab/test bench
no joy whatsoever.
no way to have the wlan adapter alive if any eth cable is plugged in. Again, all the eth are process automation controllers LANs, unmanaged (so we normally set static addresses to the nic with the DHCP either diabled or not, in the test we disbaled them just in case...)
if the cable is plugged the wlan is forced down by something
I tried (stabbing in the dark):
which returns the msg:
Code: Select all
RTNETLINK answers: Operation not possible due to RF-kill
any idea?
we do need the the Wifi nic working (VPN + remote desktop mainly) at the same time as the eth(s). kinda critical actually for our
project
PS: I tried also to set freesbee to "ignore" eth, to no avail, the wlan adapter is reported to not even being there
[!!!] (when eth is plugged in)
IP info - Network information - wireless tab:
Code: Select all
Wireless configuration:
No wireless extension detected.
and the "Interfaces" tab shows only eth and the loopabck, no wlan
also,
rfkill list returns
Code: Select all
0: dell-rbtn: wlan
Soft blocked: no
Hard blocked: no
1: phy0: wlan
Soft blocked: no
Hard blocked: yes
rfkill unblock 1
or
rfkill unblock phy0
produce no changes
but as soon as I unplug all the eth, the wifi pops up alive and hooks up to the web with no problems.
and of course:
Code: Select all
1: phy0: wlan
Soft blocked: no
Hard blocked: no