| View previous topic :: View next topic |
| Author |
Message |
feindrial
n00b
Joined: 23 Sep 2022
Posts: 2
|
 Posted: Fri Sep 23, 2022 11:06 am Post subject: cannot connect wifi with wpa_supplicant and dhcpcd |
 |
|
Hi all,
After I installing gentoo and booting from hdd, wifi connection is not working anymore but I can connect on the livecd still setting up wpa_supplicant and dhcpcd.
Here is some command outputs:
lsusb
| Code: |
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0c45:6366 Microdia Webcam Vitade AF
Bus 001 Device 003: ID 0bda:b720 Realtek Semiconductor Corp. RTL8723BU 802.11b/g/n WLAN Adapter
Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 010: ID abcd:1234 LogiLink UDisk flash drive
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
|
lsmod
| Code: |
Module Size Used by
rtl8xxxu 114688 0
x86_pkg_temp_thermal 20480 0
efivarfs 16384 1
|
dmesg command output is pretty long and forum not let me to paste it here so here it is a link : https://pastebin.com/hJvjjy8A
ifconfig
| Code: |
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 192 bytes 15552 (15.1 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 192 bytes 15552 (15.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp0s21f0u7i2: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 24:18:c6:4e:28:e2 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
|
ls /sys/class/net
| Code: |
lo
sit0
wlp0s21f0u7i2
|
cat /etc/conf.d/net
| Code: |
modules_wlp0s21f0u7i2="wpa_supplicant"
config_wlp0s21f0u7i2="dhcp"
routes_wlp0s21f0u7i2="default via 192.168.1.1"
dns_servers_wlp0s21f0u7i2="192.168.0.1 192.168.1.1"
|
cat /etc/resolv.conf
| Code: |
# Generated by dhcpcd
# /etc/resolv.conf.head can replace this line
# /etc/resolv.conf.tail can replace this line
|
cat /etc/conf.d/wpa_supplicant
| Code: |
# conf.d file for wpa_supplicant
# uncomment this if wpa_supplicant starts up before your network interface
# is ready and it causes issues
# rc_want="dev-settle"
# Please check man 8 wpa_supplicant for more information about the options
# wpa_supplicant accepts.
#
wpa_supplicant_args="-B -M -c /etc/wpa_supplicant/wpa_supplicant.conf"
|
cat /etc/wpa_supplicant/wpa_supplicant.conf
| Code: |
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
update_config=1
network={
ssid="Zyxel_A281"
psk=bfe70c084c5da98a9c1dd2a928729636e139922d686f3ca3641488b72f94d4b1
}
|
find /etc/init.d/ -name "*net*"
| Code: |
/etc/init.d/netmount
/etc/init.d/net-online
/etc/init.d/net.lo
|
|
|
| Back to top |
|
 |
logrusx
Veteran
Joined: 22 Feb 2018
Posts: 1531
|
| Posted: Fri Sep 23, 2022 11:11 am Post subject: |
|
|
Is there any chance you're trying to connect to a TKIP secured network? If so, tkip for wpa_supplicant switched to disabled by default and such networks won't even show. So you could either fix the network encryption as TKIP is unsecure or if you can't - enable back tkip for wpa_supplicant
Regards,
Georgi |
|
| Back to top |
|
|
feindrial
n00b
Joined: 23 Sep 2022
Posts: 2
|
| Posted: Fri Sep 23, 2022 11:38 am Post subject: |
|
|
| logrusx wrote: | Is there any chance you're trying to connect to a TKIP secured network? If so, tkip for wpa_supplicant switched to disabled by default and such networks won't even show. So you could either fix the network encryption as TKIP is unsecure or if you can't - enable back tkip for wpa_supplicant
Regards,
Georgi |
I'm pretty sure it's using WPA2-PSK/CCMP. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54234
Location: 56N 3W
|
| Posted: Fri Sep 23, 2022 4:52 pm Post subject: |
|
|
feindrial,
Your dmesg is missing any attempt to start wlp0s21f0u7i2. That name is USB port dependent too, you will hate that.
Make a file /etc/udev/rules.d/70-persistent-net.rules, containing
| Code: | # Fix our names as we have USB WiFi.
# ether 24:18:c6:4e:28:e2 The Wifi Dongle MAC Addr
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="24:18:c6:4e:28:e2 ", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="feindrial" |
That will name the Wifi dongle with MAC Addr 24:18:c6:4e:28:e2 to feindrial.
Do not choose a name starting wlan. That will confuse the kernel.
How are you planning to command your wifi to start?
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| 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
