You are not logged in.
Hello,
Network configuration has always been a pain to me, and despite the really good documentation from Arch Wiki I still have troubles configuring the network side of my laptop.
Hopefully I can reach archlinux.org !
The symptoms are:
Wifi interface isn't always up after reboot
Inconsistent connectivity to some websites (ipv4 ones ?). Some days it's fine, some others it's not
From the troubleshooting part of the Network configuration Wiki:
Your network interface is listed and enabled.
The *wlan0* does not always shows up after reboot. Sometimes I've to reboot twice to get it listed
ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp5s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
link/ether a4:5d:36:d1:3a:83 brd ff:ff:ff:ff:ff:ff
4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
link/ether be:5e:93:1b:0b:2e brd ff:ff:ff:ff:ff:ff permaddr 48:5a:b6:42:81:f5
You are connected to the network.
ping -c1 archlinux.org
PING archlinux.org(archlinux.org (2a01:4f9:c010:6b1f::1)) 56 data bytes
64 bytes from archlinux.org (2a01:4f9:c010:6b1f::1): icmp_seq=1 ttl=49 time=40.0 ms
--- archlinux.org ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 39.968/39.968/39.968/0.000 ms
Your network interface has an IP address.
ip link
4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
link/ether be:5e:93:1b:0b:2e brd ff:ff:ff:ff:ff:ff permaddr 48:5a:b6:42:81:f5
Your routing table is correctly set up.
ip route show
*no output*
ip -6 route show
ip -6 route show
::1 dev lo proto kernel metric 256 pref medium
2a01:cb10:8064:6e00::/64 dev wlan0 proto ra metric 3004 mtu 1500 pref high
fe80::/64 dev wlan0 proto kernel metric 256 pref medium
default via fe80::628d:26ff:fe57:9c2c dev wlan0 proto ra metric 3004 mtu 1500 pref high
You can ping a local IP address
ping 192.168.1.32
ping: connect: Network is unreachable
You can ping a public IP address
ping archlinux.org
PING archlinux.org(archlinux.org (2a01:4f9:c010:6b1f::1)) 56 data bytes
64 bytes from archlinux.org (2a01:4f9:c010:6b1f::1): icmp_seq=1 ttl=49 time=38.4 ms
--- archlinux.org ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 38.373/38.373/38.373/0.000 ms
ping -c 1 8.8.8.8
ping: connect: Network is unreachable
Check if you can resolve domain names
getent hosts archlinux.org
2a01:4f9:c010:6b1f::1 archlinux.org
dhcpcd is installed and enabled:
systemctl status dhcpcd
● dhcpcd.service - dhcpcd on all interfaces
Loaded: loaded (/usr/lib/systemd/system/dhcpcd.service; enabled; vendor preset: disabled)
Active: active (running) since Wed 2021-12-01 13:03:51 CET; 22min ago
Process: 308 ExecStart=/usr/bin/dhcpcd -q -b (code=exited, status=0/SUCCESS)
Main PID: 313 (dhcpcd)
Tasks: 5 (limit: 9344)
Memory: 2.6M
CPU: 1.318s
CGroup: /system.slice/dhcpcd.service
├─ 313 "dhcpcd: [master] [ip4] [ip6]"
├─ 314 "dhcpcd: [privileged actioneer]"
├─ 315 "dhcpcd: [network proxy]"
├─ 316 "dhcpcd: [control proxy]"
└─2286 "dhcpcd: [BPF BOOTP] wlan0"
But starting it on the wlan0 interface returns an error:
systemctl start dhcpcd@wlan0
Job for dhcpcd@wlan0.service failed because the service did not take the steps required by its unit configuration.
See "systemctl status dhcpcd@wlan0.service" and "journalctl -xeu dhcpcd@wlan0.service" for details.
journalctl -xeu dhcpcd@wlan0.service
-- Boot ee1177c029924fb8855d5b7f96b2adde --
Dec 01 13:26:33 nomad systemd[1]: Starting dhcpcd on wlan0...
░░ Subject: A start job for unit dhcpcd@wlan0.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit dhcpcd@wlan0.service has begun execution.
░░
░░ The job identifier is 1633.
Dec 01 13:26:33 nomad systemd[1]: dhcpcd@wlan0.service: Can't open PID file /run/dhcpcd/wlan0.pid (yet?) after start: Operation not permitted
Dec 01 13:26:33 nomad systemd[1]: dhcpcd@wlan0.service: Failed with result 'protocol'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit dhcpcd@wlan0.service has entered the 'failed' state with result 'protocol'.
Dec 01 13:26:33 nomad systemd[1]: Failed to start dhcpcd on wlan0.
░░ Subject: A start job for unit dhcpcd@wlan0.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit dhcpcd@wlan0.service has finished with a failure.
░░
░░ The job identifier is 1633 and the job result is failed.
I'm using NetworkManager to manage network connection, but I've also installed (**messed with**) multiples wirless connection manager:
which wpa_supplicant iw iwd wireless_tools
/usr/bin/wpa_supplicant
/usr/bin/iw
which: no iwd in (/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl)
which: no wireless_tools in (/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl)
systemctl list-units --type=service
UNIT LOAD ACTIVE SUB DESCRIPTION
alsa-restore.service loaded active exited Save/Restore Sound Card State
dbus.service loaded active running D-Bus System Message Bus
dhcpcd.service loaded active running dhcpcd on all interfaces
● dhcpcd@wlan0.service loaded failed failed dhcpcd on wlan0
iwd.service loaded active running Wireless service
kmod-static-nodes.service loaded active exited Create List of Static Device Nodes
lightdm.service loaded active running Light Display Manager
NetworkManager.service loaded active running Network Manager
polkit.service loaded active running Authorization Manager
postgresql.service loaded active running PostgreSQL database server
systemd-backlight@backlight:intel_backlight.service loaded active exited Load/Save Screen Backlight Brightness of backlight:intel_backlight
systemd-fsck@dev-disk-by\x2duuid-9A1D\x2d6F91.service loaded active exited File System Check on /dev/disk/by-uuid/9A1D-6F91
systemd-journal-flush.service loaded active exited Flush Journal to Persistent Storage
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running User Login Management
systemd-modules-load.service loaded active exited Load Kernel Modules
systemd-random-seed.service loaded active exited Load/Save Random Seed
systemd-remount-fs.service loaded active exited Remount Root and Kernel File Systems
systemd-sysctl.service loaded active exited Apply Kernel Variables
systemd-tmpfiles-setup-dev.service loaded active exited Create Static Device Nodes in /dev
systemd-tmpfiles-setup.service loaded active exited Create Volatile Files and Directories
systemd-udev-trigger.service loaded active exited Coldplug All udev Devices
systemd-udevd.service loaded active running Rule-based Manager for Device Events and Files
systemd-update-utmp.service loaded active exited Record System Boot/Shutdown in UTMP
systemd-user-sessions.service loaded active exited Permit User Sessions
upower.service loaded active running Daemon for power management
user-runtime-dir@1000.service loaded active exited User Runtime Directory /run/user/1000
user@1000.service loaded active running User Manager for UID 1000
wpa_supplicant.service loaded active running WPA supplicant
Does anyone spot the issue and can guide me in the right direction ? An helping hand would be gratefully appreciated ...!
Thanks to the community for the awesome resources btw, sorry for not being able to understand it all on my own
Last edited by kawsay (2021-12-01 12:42:38)
Offline
Multiple network managers are more than likely the cause of your issues. Most of them are mutually exclusive. Disable and stop iwd, dhcpcd, dhcpcd@wlan0 and wpa_supplicant (it will be invoked by networkmanager on demand) in order to properly make use of networkmanager if that's your intended route
Offline
Thanks for your answer. Indeed, this is specified multiple times in the Wiki pages.
I've disable and stop everything except NetworkManager. Though wpa_supplicant stay started (disabled). Does NetworkManager starts it ? When I try to remove it, pacman returns that it is a NetworkManager dependency)
Everything is okay now, except IPv4. I've tried configuring an IPv4 address & route using nmcli, but even after rebooting it doesn't look effective:
cat /etc/NetworkManager/system-connections/<SSID>.nmconnection
[connection]
id=<SSID>
uuid=<UUID>
type=wifi
interface-name=wlan0
permissions=
timestamp=1638370901
[wifi]
mac-address-blacklist=
mode=infrastructure
ssid=<SSID>
[wifi-security]
auth-alg=open
key-mgmt=wpa-psk
psk=<PASSWORD>
[ipv4]
address1=192.168.1.42/24
dhcp-timeout=2147483647
dns-search=
method=auto
routes1=192.168.1.1/24
gateway=192.168.1.1/24
[ipv6]
addr-gen-mode=stable-privacy
dns-search=
method=auto
[proxy]
but:
ip route show
192.168.1.0/24 dev wlan0 proto static scope link metric 600
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.42 metric 600
I did not configured this 192.168.1.0, any idea from where it could come from ?
The valid route is 192.168.1.1/24
Last edited by kawsay (2021-12-01 15:29:58)
Offline
Does NetworkManager start it?
Yes.
I did not configured this 192.168.1.0, any idea from where it could come from?
routes1=192.168.1.1/24
gateway=192.168.1.1/24
192.168.1.0/24 is the canonical segment, "192.168.1.1/24" is semi-bogus form.
You don't have a default route, only for that segment (ie. your lan - you likely can "ping 192.168.1.1" but you cannot reach eg. 8.8.8.8)
Do you actually want a static IP or rather use dhcp (that's not dhcpcd, NM implements the protocol itself - it can use dhcpcd or dhclient as backend, though)
Last edited by seth (2021-12-01 15:47:50)
Offline
Edit: imafool
Last edited by seth (2021-12-01 15:47:39)
Offline
I cannot ping 192.168.1.1 nor 8.8.8.8
ping -c 1 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
--- 192.168.1.1 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
ping -c 1 8.8.8.8
ping: connect: Network is unreachable
I'll try using a DHCP (I know I've almost set up a static IP), I'll refer to nmcli documentation and come back here if I've troubles
(edit: not easy to do it "on my own" as serverfault isn't IPv6 ahah)
Last edited by kawsay (2021-12-01 15:57:06)
Offline
What's not easy to do? NM will go fo dhcp if you don't configure a static IP.
https://wiki.archlinux.org/title/Networ … i_examples
Edit: you probably want to delete that profile first
Last edited by seth (2021-12-01 16:08:57)
Offline
What's not easy to do?
Well, discovering new software as a beginner isn't always easy... Though it often looks more complicated than it really is.
From the link you provided and the section above (DHCP client), I tried to configure DHCP using dhclient
# Remove previous profile
rm /etc/NetworkManager/system-connections/<SSID>.nmconnection
# Set up initial connection
nmcli dev wifi connect <SSID> password <PASSWORD>
# Download a DHCP backend
pacman -S dhclient
# Configure NetworkManager to use dhclient
echo -e "[main]\ndhcp=dhclient" >> /etc/NetworkManager/conf.d/dhcp-client.conf
# Set up DHCP hostname
nmcli connection modify <SSID> ipv4.dhcp-hostname 192.168.1.1/24
# Verify changes on /etc/NetworkManager/system-connections/<SSID>-<UUID>.nmconnection
grep dhcp /etc/NetworkManager/system-connections/<SSID>-<UUID>.nmconnection
dhcp-hostname=192.168.1.1/24
# Apply changes
nmcli connection reload
At this point I was expecting to have an IPv4 address set up with a routing table.
As the Wiki says "By default NetworkManager uses its internal DHCP client" (DHCP client), I repeated the process described above without setting dhclient as backend (and removing /etc/NetworkManager/conf.d/dhcp-client.conf). Same result: no IPv4, not routing table...
Am I a help vampire ?
Last edited by kawsay (2021-12-01 16:41:16)
Offline
I think you are over complicating this greatly. Why are you manually setting a dhcp-hostname in the first place? I suggest you remove that profile and just try to connect. If that doesn't work post a journal
sudo journalctl -b
Last edited by V1del (2021-12-01 17:22:58)
Offline
I think you are over complicating this greatly. Why are you manually setting a dhcp-hostname in the first place? I suggest you remove that profile and just try to connect. If that doesn't work post a journal
sudo journalctl -b
Indeed, I ran the same command and it worked. Now I've an IPv4 & 6 and IPv4 & 6 routes.
I don't understand why, I ran this command 6 times yesterday...
For information, here's the corresponding log:
Dec 02 14:00:39 nomad NetworkManager[303]: <info> [1638450039.3486] audit: op="connection-update" uuid="bbacb7f1-ecc1-4406-bd96-9b91fae68fe0" name="<SSID>" args="connection.timestamp" pid=12582 uid=0 result="success"
Dec 02 14:00:39 nomad kernel: audit: type=1111 audit(1638450039.342:186): pid=303 uid=0 auid=4294967295 ses=4294967295 msg='op=connection-update uuid=bbacb7f1-ecc1-4406-bd96-9b91fae68fe0 name="<SSID>" args=connection.timestamp pid=12582 uid=0 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
Dec 02 14:00:39 nomad kernel: audit: type=1111 audit(1638450039.346:187): pid=303 uid=0 auid=4294967295 ses=4294967295 msg='op=connection-activate uuid=bbacb7f1-ecc1-4406-bd96-9b91fae68fe0 name="<SSID>" pid=12582 uid=0 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
Dec 02 14:00:39 nomad audit[303]: USYS_CONFIG pid=303 uid=0 auid=4294967295 ses=4294967295 msg='op=connection-update uuid=bbacb7f1-ecc1-4406-bd96-9b91fae68fe0 name="<SSID>" args=connection.timestamp pid=12582 uid=0 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
Dec 02 14:00:39 nomad audit[303]: USYS_CONFIG pid=303 uid=0 auid=4294967295 ses=4294967295 msg='op=connection-activate uuid=bbacb7f1-ecc1-4406-bd96-9b91fae68fe0 name="<SSID>" pid=12582 uid=0 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
Dec 02 14:00:39 nomad NetworkManager[303]: <info> [1638450039.3508] device (wlan0): Activation: starting connection '<SSID>' (bbacb7f1-ecc1-4406-bd96-9b91fae68fe0)
Dec 02 14:00:39 nomad NetworkManager[303]: <info> [1638450039.3510] audit: op="connection-activate" uuid="bbacb7f1-ecc1-4406-bd96-9b91fae68fe0" name="<SSID>" pid=12582 uid=0 result="success"
Dec 02 14:00:39 nomad NetworkManager[303]: <info> [1638450039.3511] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Dec 02 14:00:39 nomad NetworkManager[303]: <info> [1638450039.3515] manager: NetworkManager state is now CONNECTING
Dec 02 14:00:39 nomad NetworkManager[303]: <info> [1638450039.3534] device (wlan0): set-hw-addr: reset MAC address to 48:5A:B6:42:81:F5 (preserve)
Dec 02 14:00:39 nomad NetworkManager[303]: <info> [1638450039.4797] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Dec 02 14:00:39 nomad NetworkManager[303]: <info> [1638450039.4800] device (wlan0): Activation: (wifi) access point '<SSID>' has security, but secrets are required.
Dec 02 14:00:39 nomad NetworkManager[303]: <info> [1638450039.4801] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Dec 02 14:00:39 nomad NetworkManager[303]: <info> [1638450039.4803] sup-iface[4336b2b8b9ea12ca,0,wlan0]: wps: type pbc start...
Dec 02 14:00:39 nomad NetworkManager[303]: <info> [1638450039.4839] device (wlan0): supplicant interface state: disconnected -> interface_disabled
Dec 02 14:00:39 nomad NetworkManager[303]: <info> [1638450039.4853] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Dec 02 14:00:39 nomad NetworkManager[303]: <info> [1638450039.4857] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Dec 02 14:00:39 nomad NetworkManager[303]: <info> [1638450039.4863] device (wlan0): Activation: (wifi) connection '<SSID>' has security, and secrets exist. No new secrets needed.
Dec 02 14:00:39 nomad NetworkManager[303]: <info> [1638450039.4865] Config: added 'ssid' value '<SSID>'
Dec 02 14:00:39 nomad NetworkManager[303]: <info> [1638450039.4867] Config: added 'scan_ssid' value '1'
Dec 02 14:00:39 nomad NetworkManager[303]: <info> [1638450039.4867] Config: added 'bgscan' value 'simple:30:-70:86400'
Dec 02 14:00:39 nomad NetworkManager[303]: <info> [1638450039.4867] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Dec 02 14:00:39 nomad NetworkManager[303]: <info> [1638450039.4867] Config: added 'auth_alg' value 'OPEN'
Dec 02 14:00:39 nomad NetworkManager[303]: <info> [1638450039.4868] Config: added 'psk' value '<hidden>'
Dec 02 14:00:39 nomad NetworkManager[303]: <info> [1638450039.4895] device (wlan0): supplicant interface state: interface_disabled -> disconnected
Dec 02 14:00:39 nomad NetworkManager[303]: <info> [1638450039.5008] device (wlan0): supplicant interface state: disconnected -> scanning
Dec 02 14:00:40 nomad wpa_supplicant[382]: wlan0: SME: Trying to authenticate with 60:8d:26:57:9c:2c (SSID='<SSID>' freq=2462 MHz)
Dec 02 14:00:40 nomad kernel: wlan0: authenticate with 60:8d:26:57:9c:2c
Dec 02 14:00:40 nomad kernel: wlan0: send auth to 60:8d:26:57:9c:2c (try 1/3)
Dec 02 14:00:40 nomad kernel: wlan0: authenticated
Dec 02 14:00:40 nomad NetworkManager[303]: <info> [1638450040.5777] device (wlan0): supplicant interface state: scanning -> authenticating
Dec 02 14:00:40 nomad wpa_supplicant[382]: wlan0: Trying to associate with 60:8d:26:57:9c:2c (SSID='<SSID>' freq=2462 MHz)
Dec 02 14:00:40 nomad kernel: wlan0: associate with 60:8d:26:57:9c:2c (try 1/3)
Dec 02 14:00:40 nomad kernel: wlan0: RX AssocResp from 60:8d:26:57:9c:2c (capab=0x1411 status=0 aid=1)
Dec 02 14:00:40 nomad kernel: wlan0: associated
Dec 02 14:00:40 nomad wpa_supplicant[382]: wlan0: Associated with 60:8d:26:57:9c:2c
Dec 02 14:00:40 nomad wpa_supplicant[382]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Dec 02 14:00:40 nomad NetworkManager[303]: <info> [1638450040.5907] device (wlan0): supplicant interface state: authenticating -> associating
Dec 02 14:00:40 nomad NetworkManager[303]: <info> [1638450040.5936] device (wlan0): supplicant interface state: associating -> associated
Dec 02 14:00:40 nomad NetworkManager[303]: <info> [1638450040.6050] device (wlan0): supplicant interface state: associated -> 4way_handshake
Dec 02 14:00:40 nomad wpa_supplicant[382]: wlan0: WPA: Key negotiation completed with 60:8d:26:57:9c:2c [PTK=CCMP GTK=CCMP]
Dec 02 14:00:40 nomad wpa_supplicant[382]: wlan0: CTRL-EVENT-CONNECTED - Connection to 60:8d:26:57:9c:2c completed [id=0 id_str=]
Dec 02 14:00:40 nomad NetworkManager[303]: <info> [1638450040.6610] device (wlan0): supplicant interface state: 4way_handshake -> completed
Dec 02 14:00:40 nomad NetworkManager[303]: <info> [1638450040.6611] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "<SSID>"
Dec 02 14:00:40 nomad NetworkManager[303]: <info> [1638450040.6613] device (wlan0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Dec 02 14:00:40 nomad kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Dec 02 14:00:40 nomad NetworkManager[303]: <warn> [1638450040.6620] dhcp4: hostname '192.168.1.1/24' is invalid, will be ignored
Dec 02 14:00:40 nomad NetworkManager[303]: <info> [1638450040.6622] dhcp4 (wlan0): activation: beginning transaction (timeout in 10 seconds)
Dec 02 14:00:40 nomad NetworkManager[303]: <info> [1638450040.6771] dhcp4 (wlan0): state changed unknown -> bound, address=192.168.1.34
Dec 02 14:00:40 nomad NetworkManager[303]: <info> [1638450040.6792] device (wlan0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Dec 02 14:00:40 nomad dbus-daemon[302]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.1' (uid=0 pid=303 comm="/usr/bin/NetworkManager --no-daemon ")
Dec 02 14:00:40 nomad systemd[1]: Starting Network Manager Script Dispatcher Service...
Dec 02 14:00:40 nomad dbus-daemon[302]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dec 02 14:00:40 nomad NetworkManager[303]: <info> [1638450040.6963] device (wlan0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Dec 02 14:00:40 nomad NetworkManager[303]: <info> [1638450040.6967] device (wlan0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Dec 02 14:00:40 nomad NetworkManager[303]: <info> [1638450040.6971] manager: NetworkManager state is now CONNECTED_LOCAL
Dec 02 14:00:40 nomad NetworkManager[303]: <info> [1638450040.6976] manager: NetworkManager state is now CONNECTED_SITE
Dec 02 14:00:40 nomad NetworkManager[303]: <info> [1638450040.6977] policy: set '<SSID>' (wlan0) as default for IPv4 routing and DNS
Dec 02 14:00:40 nomad systemd[1]: Started Network Manager Script Dispatcher Service.
Dec 02 14:00:40 nomad audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 02 14:00:40 nomad NetworkManager[303]: <info> [1638450040.7015] device (wlan0): Activation: successful, device activated.
Dec 02 14:00:40 nomad kernel: audit: type=1130 audit(1638450040.696:188): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 02 14:00:40 nomad kernel: wlan0: Limiting TX power to 20 (20 - 0) dBm as advertised by 60:8d:26:57:9c:2c
Dec 02 14:00:40 nomad NetworkManager[303]: <info> [1638450040.9124] manager: NetworkManager state is now CONNECTED_GLOBAL
Dec 02 14:00:41 nomad wpa_supplicant[382]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-55 noise=9999 txrate=28900
Dec 02 14:00:42 nomad NetworkManager[303]: <info> [1638450042.1570] dhcp6 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Dec 02 14:00:42 nomad NetworkManager[303]: <info> [1638450042.1579] policy: set '<SSID>' (wlan0) as default for IPv6 routing and DNS
Dec 02 14:00:42 nomad NetworkManager[303]: <info> [1638450042.1662] dhcp6 (wlan0): state changed unknown -> bound
Dec 02 14:00:51 nomad systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Dec 02 14:00:51 nomad audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 02 14:00:51 nomad kernel: audit: type=1131 audit(1638450051.176:189): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
First I though 192.168.1.24 was already taken but it's not. I'm not sure to understand why this address is considered invalid
Dec 02 14:00:40 nomad NetworkManager[303]: <warn> [1638450040.6620] dhcp4: hostname '192.168.1.1/24' is invalid, will be ignored
Thanks for your help !
Offline
"192.168.1.1/24" is not a host but a network segment. It represents 192.168.1.1 … 192.168.1.255 and the usual form is "192.168.1.0/24"
Offline