View previous topic :: View next topic |
Author |
Message |
Spanik l33t
Joined: 12 Dec 2003 Posts: 943 Location: Belgium
|
Posted: Mon Jul 11, 2022 11:19 am Post subject: no dhcp when using wifi |
|
|
This weekend I noticed that my laptop does not do dhcp when using wifi. Normally the laptop uses a cable when I use it at home at the desk. And then it does dhcp all right. This was not always the case. I changed a few settings of my network configuration after this thread here: https://forums.gentoo.org/viewtopic-t-1151246.html
When it starts I see this in dmesg (cable is connected as well):
Code: | [ 2.997691] e100: Intel(R) PRO/100 Network Driver
[ 2.998748] e100: Copyright(c) 1999-2006 Intel Corporation
[ 2.999799] e1000: Intel(R) PRO/1000 Network Driver
[ 3.000824] e1000: Copyright (c) 1999-2006 Intel Corporation.
[ 3.001857] e1000e: Intel(R) PRO/1000 Network Driver
[ 3.002868] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[ 3.003937] r8169 0000:0c:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 3.005755] kworker/u16:6 (138) used greatest stack depth: 14344 bytes left
[ 3.006277] r8169 0000:0c:00.0 eth0: RTL8168evl/8111evl, b8:88:e3:e2:fd:59, XID 2c9, IRQ 29
[ 3.007799] r8169 0000:0c:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]
....
[ 7.463891] r8169 0000:0c:00.0 enp12s0: renamed from eth0
[ 7.482823] Intel(R) Wireless WiFi driver for Linux
[ 7.485264] iwlwifi 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 7.486008] Loading firmware: iwlwifi-2030-6.ucode
[ 7.490592] iwlwifi 0000:03:00.0: loaded firmware version 18.168.6.1 2030-6.ucode op_mode iwldvm
[ 7.503402] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUG disabled
[ 7.503412] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
[ 7.503417] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TRACING enabled
[ 7.503421] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Wireless-N 2230 BGN, REV=0xC8
[ 7.531640] mc: Linux media interface: v0.10
[ 7.542394] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
.......
[ 7.597733] iwlwifi 0000:03:00.0 wlp3s0: renamed from wlan0
.......
[ 11.994759] iwlwifi 0000:03:00.0: Radio type=0x2-0x0-0x0
[ 12.261771] iwlwifi 0000:03:00.0: Radio type=0x2-0x0-0x0
[ 12.394077] Loading firmware: rtl_nic/rtl8168e-3.fw
[ 12.395931] RTL8211E Gigabit Ethernet r8169-0-c00:00: attached PHY driver (mii_bus:phy_addr=r8169-0-c00:00, irq=MAC)
[ 12.608621] ip (1785) used greatest stack depth: 10504 bytes left
[ 12.609181] r8169 0000:0c:00.0 enp12s0: Link is Down
[ 13.130854] wlp3s0: authenticate with 14:cc:20:46:54:1d
[ 13.134583] wlp3s0: send auth to 14:cc:20:46:54:1d (try 1/3)
[ 13.137388] wlp3s0: authenticated
[ 13.138195] wlp3s0: associate with 14:cc:20:46:54:1d (try 1/3)
[ 13.142183] wlp3s0: RX AssocResp from 14:cc:20:46:54:1d (capab=0x1431 status=0 aid=3)
[ 13.162459] wlp3s0: associated
[ 13.207502] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
[ 15.650537] r8169 0000:0c:00.0 enp12s0: Link is Up - 1Gbps/Full - flow control off
[ 15.650556] IPv6: ADDRCONF(NETDEV_CHANGE): enp12s0: link becomes ready |
After this I log in and start X (which gets me into KDE) and then I have a window from wpa_gui. In that the wifi network is listed and the connection is made. But I do not get an IP address. If I now disconnect from the wifi, start dhcpcd (rc-service dhcpcd start) and then connect again with wpa_gui the wifi gets an IP address.
I do have a link net.wpls3s0 and /etc/conf.d/net is:
Code: | dns_domain_lo="thuis"
config_enp12s0="dhcp"
modules_wlp3s0="wpa_supplicant"
config_wlp3s0="dhcp" |
Previously I had dhcpcd running in level default. and then it worked. But to get the nas at boot I had to remove that from default. OTOH I do not understand why the cabled connection does get dhcp and the wifi doesn't. _________________ Expert in non-working solutions |
|
Back to top |
|
|
Spanik l33t
Joined: 12 Dec 2003 Posts: 943 Location: Belgium
|
Posted: Sun Jul 17, 2022 10:00 am Post subject: |
|
|
Nobody an idea? _________________ Expert in non-working solutions |
|
Back to top |
|
|
pjp Administrator
Joined: 16 Apr 2002 Posts: 20067
|
Posted: Sun Jul 17, 2022 2:45 pm Post subject: |
|
|
What's the output of rc-update ? I noticed in the other thread its output doesn't show wpa_supplicant.
The only difference I have in conf.d/net is logging and whatever !plug does (I don't see documentation for it): Code: | modules_wlp3s0="!plug wpa_supplicant"
wpa_supplicant_wlp4s0="-Dnl80211 -dd -f /var/log/wpa_supplicant.log" | Otherwise I don't have any net.* automatically started, nor do I have dhcp automatically started. wpa_supplicant handles both.
I don't often use wired, which I just tested, and it automatically switches between wired & wireless. _________________ Quis separabit? Quo animo? |
|
Back to top |
|
|
Spanik l33t
Joined: 12 Dec 2003 Posts: 943 Location: Belgium
|
Posted: Sun Jul 17, 2022 3:00 pm Post subject: |
|
|
RC-update looks like this:
Code: | ~ $ rc-update
binfmt | boot
bootmisc | boot
cgroups | sysinit
dbus | default
devfs | sysinit
dmesg | sysinit
fsck | boot
hostname | boot
hwclock | boot
keymaps | boot
killprocs | shutdown
kmod-static-nodes | sysinit
local | default nonetwork
localmount | boot
loopback | boot
modules | boot
mount-ro | shutdown
mtab | boot
net.enp12s0 | default
netmount | default
ntp-client | default
ntpd | default
procfs | boot
root | boot
save-keymaps | boot
save-termencoding | boot
savecache | shutdown
swap | boot
sysctl | boot
sysfs | sysinit
sysklogd | default
systemd-tmpfiles-setup | boot
systemd-tmpfiles-setup-dev | sysinit
termencoding | boot
udev | sysinit
udev-trigger | sysinit
urandom | boot
wpa_supplicant | default
~ $
|
Should I put net.wpls also in default? _________________ Expert in non-working solutions |
|
Back to top |
|
|
pjp Administrator
Joined: 16 Apr 2002 Posts: 20067
|
Posted: Sun Jul 17, 2022 3:16 pm Post subject: |
|
|
No, I think it should not be there. Neither my wireless nor wired net.* scripts are automatically started.
Your conf.d includes config_enp12s0="dhcp", so I'd remove it from any run levels (I believe: rc-update del net.enp12s0 would do that).
On my system, it appears that wpa_supplicant handles both interfaces. _________________ Quis separabit? Quo animo? |
|
Back to top |
|
|
|