| View previous topic :: View next topic |
| Author |
Message |
jankom
Guru
Joined: 30 Aug 2021
Posts: 365
Location: USA
|
 Posted: Fri Aug 26, 2022 7:02 pm Post subject: WiFi cannot connect (outside US) - SOLVED with iwd |
 |
|
Edited 8/27/22, then again on 8/28/22 - removed long quoted outputs, additional info added at bottom - continuing debugging, still need help!
After arriving to Hungary from the US WiFi on my fitlet2 box cannot connect. Same AP worked in February. In the meantime my Gentoo system has been updated regularly. Presently using wpa_supplicant-2.10-r1.
My XUbuntu laptop had no problem connecting here in Hungary, and the fitlet2 worked fine in the US up until my travel.
Spent days searching Internet info, postings, Gentoo Wiki and the relevant doc in /usr/share. Finally I am looking for help from the Gentoo community.
08/27/22 additional info; modified 8/28/22:
(1) Tested the fitlet box with an older Gentoo based boot stick and it could connect to WiFi. It is using wpa_supplicant v2.6
(2) Starting wpa_supplicant manually from root command line the process completes successfully; activating "dhcpcd interface" completes OK, but | Quote: | andraslinux /home/janos # /usr/sbin/wpa_supplicant -i wlp1s0 -c /etc/wpa_supplicant/wpa_supplicant.conf
Successfully initialized wpa_supplicant
wlp1s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=EU
^Cwlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
nl80211: deinit ifname=wlp1s0 disabled_11b_rates=0
wlp1s0: CTRL-EVENT-TERMINATING
andraslinux /home/janos #
andraslinux /var/run # /usr/sbin/wpa_supplicant -i wlp1s0 -c /etc/wpa_supplicant/wpa_supplicant.conf
Successfully initialized wpa_supplicant
janos@andraslinux ~ $ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000
link/sit 0.0.0.0 brd 0.0.0.0
3: wlp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether c8:e2:65:42:5f:a4 brd ff:ff:ff:ff:ff:ff
janos@andraslinux ~ $
|
Looks like the problem is with no carrier in the interface. Could it be due to EU vs US?
Hope, this helps - jankom
Last edited by jankom on Wed Sep 07, 2022 4:11 pm; edited 1 time in total |
|
| Back to top |
|
 |
madmin
n00b
Joined: 04 Nov 2018
Posts: 29
|
| Posted: Wed Aug 31, 2022 4:46 pm Post subject: |
|
|
Hi,
- The NO-CARRIER on your wlp1s0 shall mean that this card is not connected to some AP (access Point).
- To check if your WIFI card is connected to some AP, you can use "iw" command from net-wireless/iw or "iwconfig" from net-wireless/wireless-tools
As WIFI is not my favorite thing, I prefer to use iwconfig which can be run without argument:
| Code: | $ iwconfig
lo no wireless extensions.
wlp82s0 IEEE 802.11 ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=-2147483648 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:on
eth0 no wireless extensions. |
- wpa_supplicant 2.10 is certainly your issue. As you said, with earlier version it works and here, once this 2.10 compiled, I also lost my WIFI connection.
To get my WIFI working again, I had to lower the security offered by wpa_supplicant in that new version by using "ieee80211w=1" in wpa_supplicant configuration file (generally /etc/wpa_supplicant/wpa_supplicant.conf but the name can differ).
I added "ieee80211w=1" in "network={}" section as it seems to me the right place: issue with one network, new configuration item in that network conf...
Hoping this helps, cheers |
|
| Back to top |
|
|
jankom
Guru
Joined: 30 Aug 2021
Posts: 365
Location: USA
|
| Posted: Wed Aug 31, 2022 7:16 pm Post subject: @madmin - edited Sep 7, 2022 |
|
|
Thank you for your reply. It is getting late here ion Budapest, and I'll be away for two days, but at the atest Saturday, I'll try your suggestion.
In the meantime I decided to try iwd as a method to connect to WiFi network since the fitlet box has Intel processor and devices. I did the necessary kernel configuration adjustments, and BINGO - I was able to connect. I write this on my fitlet machine.
Just to complete this issues for proper closing I'll add more edit to my original posting Saturday, Sep 3, '22.
Thanks again for all your interest - jankom
EDIT - more info, Sep 7, 2022:
Marked original post as SOLVED with iwd
Tried your suggestion for wpa_supplicant without success. I consider the original issue partially solvedL I do have WiFi access now with iwd. Will edit again after Sep 21, 2022 upon my return home to US to make sure WiFi works there as well, that is the "iwd" is the correct solution of this issue.
I'll open another issue experienced while away from home: | Quote: | | OVPN name resolution |
jankom |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
