[SOLVED] Network Is not working

WhiteySpicy · 2021-11-06 17:34:52

I have tried both NetworkManager and dhcpcd. Network Manager doesnt assign a inet4 ip address to my main network interface but when I use dhcpcd it assigns a inet4 ip address with the value "196.254.xx.xx"

"ip addr show" returns this:

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 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 2c:f0:5d:7e:90:7c brd ff:ff:ff:ff:ff:ff
    inet6 fe80::f306:7536:aa6d:4157/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: enp0s20f0u8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether 86:49:6b:48:32:ab brd ff:ff:ff:ff:ff:ff
    inet 192.168.195.95/24 brd 192.168.195.255 scope global dynamic noprefixroute enp0s20f0u8
       valid_lft 3373sec preferred_lft 3373sec
    inet6 fe80::1526:240:cbf3:4a0/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

(enp2s0 is my main network interface and enp0s20f0u8 is my phone with usb tethering on, its the only way I can get connection at the moment)

Edit: systemctl status NetworkManager (without my phone connected)

Nov 06 21:51:40 starship NetworkManager[2482]: <info>  [1636235500.6376] device (enp2s0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'assume')
Nov 06 21:51:40 starship NetworkManager[2482]: <info>  [1636235500.6380] device (enp2s0): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'assume')
Nov 06 21:51:40 starship NetworkManager[2482]: <info>  [1636235500.6384] device (enp2s0): Activation: starting connection 'Wired connection 1' (94b9962c-02f9-3463-834f-ff6f63f9efbf)
Nov 06 21:51:40 starship NetworkManager[2482]: <info>  [1636235500.6390] ovsdb: Could not connect: No such file or directory
Nov 06 21:51:40 starship NetworkManager[2482]: <info>  [1636235500.6390] ovsdb: disconnected from ovsdb
Nov 06 21:51:40 starship NetworkManager[2482]: <info>  [1636235500.6394] device (enp2s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'assume')
Nov 06 21:51:40 starship NetworkManager[2482]: <info>  [1636235500.6396] device (enp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'assume')
Nov 06 21:51:40 starship NetworkManager[2482]: <info>  [1636235500.6397] device (enp2s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'assume')
Nov 06 21:51:40 starship NetworkManager[2482]: <info>  [1636235500.6398] dhcp4 (enp2s0): activation: beginning transaction (timeout in 45 seconds)
Nov 06 21:51:40 starship NetworkManager[2482]: <info>  [1636235500.7015] dhcp6 (enp2s0): activation: beginning transaction (timeout in 45 seconds)

Last edited by WhiteySpicy (2021-11-07 13:13:52)

seth · 2021-11-06 20:20:47

That ends w/ the dhcp request, please post the entire journal (sudo journalctl -b)

You can use dhcpcd as backend of networkmanager, https://wiki.archlinux.org/title/Networ … HCP_client
Do NOT activate the dhcpcd service for this! Just configure NM to use dhcpcd.

WhiteySpicy · 2021-11-06 21:40:22

Really sorry for the late reply, here is the result:

journalctl -b | grep enp2s0

Nov 07 00:37:30 starship NetworkManager[2482]: <info>  [1636245450.0595] dhcp4 (enp2s0): canceled DHCP transaction
Nov 07 00:37:30 starship NetworkManager[2482]: <info>  [1636245450.0595] dhcp4 (enp2s0): state changed timeout -> terminated
Nov 07 00:37:30 starship NetworkManager[82793]: <info>  [1636245450.1730] device (enp2s0): carrier: link connected
Nov 07 00:37:30 starship NetworkManager[82793]: <info>  [1636245450.1732] manager: (enp2s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/3)
Nov 07 00:37:30 starship NetworkManager[82793]: <info>  [1636245450.1737] manager: (enp2s0): assume: will attempt to assume matching connection 'Wired connection 1' (94b9962c-02f9-3463-834f-ff6f63f9efbf) (indicated)
Nov 07 00:37:30 starship NetworkManager[82793]: <info>  [1636245450.1737] device (enp2s0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'assume')
Nov 07 00:37:30 starship NetworkManager[82793]: <info>  [1636245450.1740] device (enp2s0): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'assume')
Nov 07 00:37:30 starship NetworkManager[82793]: <info>  [1636245450.1743] device (enp2s0): Activation: starting connection 'Wired connection 1' (94b9962c-02f9-3463-834f-ff6f63f9efbf)
Nov 07 00:37:30 starship NetworkManager[82793]: <info>  [1636245450.1767] device (enp2s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'assume')
Nov 07 00:37:30 starship NetworkManager[82793]: <info>  [1636245450.1769] device (enp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'assume')
Nov 07 00:37:30 starship NetworkManager[82793]: <info>  [1636245450.1775] device (enp2s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'assume')
Nov 07 00:37:30 starship NetworkManager[82793]: <info>  [1636245450.1777] dhcp4 (enp2s0): activation: beginning transaction (timeout in 45 seconds)
Nov 07 00:37:30 starship NetworkManager[82793]: <info>  [1636245450.1882] policy: set 'Wired connection 1' (enp2s0) as default for IPv6 routing and DNS
Nov 07 00:37:30 starship NetworkManager[82793]: <info>  [1636245450.2966] dhcp6 (enp2s0): activation: beginning transaction (timeout in 45 seconds)

journalctl -b

Nov 07 00:43:21 starship kernel: audit: type=1105 audit(1636245801.420:284): pid=83060 uid=1000 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Nov 07 00:43:21 starship audit[83060]: USER_ACCT pid=83060 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="matt" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Nov 07 00:43:21 starship audit[83060]: CRED_REFR pid=83060 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Nov 07 00:43:21 starship audit[83060]: USER_START pid=83060 uid=1000 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Nov 07 00:43:21 starship dbus-daemon[296]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Nov 07 00:43:21 starship sudo[83060]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Nov 07 00:43:21 starship sudo[83060]:     matt : TTY=pts/0 ; PWD=/home/matt ; USER=root ; COMMAND=/sbin/systemctl restart NetworkManager
Nov 07 00:43:21 starship systemd[1]: Stopping Network Manager...
Nov 07 00:43:21 starship sudo[83060]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Nov 07 00:43:21 starship NetworkManager[82793]: <info>  [1636245801.4295] caught SIGTERM, shutting down normally.
Nov 07 00:43:21 starship NetworkManager[82793]: <info>  [1636245801.4461] dhcp4 (enp2s0): canceled DHCP transaction
Nov 07 00:43:21 starship NetworkManager[82793]: <info>  [1636245801.4461] dhcp4 (enp2s0): state changed timeout -> terminated
Nov 07 00:43:21 starship NetworkManager[82793]: <info>  [1636245801.4629] dhcp4 (enp0s20f0u8): canceled DHCP transaction
Nov 07 00:43:21 starship NetworkManager[82793]: <info>  [1636245801.4629] dhcp4 (enp0s20f0u8): state changed bound -> terminated
Nov 07 00:43:21 starship NetworkManager[82793]: <info>  [1636245801.4631] manager: NetworkManager state is now CONNECTED_SITE
Nov 07 00:43:21 starship dbus-daemon[296]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.111' (uid=0 pid=82793 comm="/usr/bin/NetworkManager --no-daemon ")
Nov 07 00:43:21 starship systemd[1]: Starting Network Manager Script Dispatcher Service...
Nov 07 00:43:21 starship NetworkManager[82793]: <info>  [1636245801.4726] exiting (success)
Nov 07 00:43:21 starship dbus-daemon[296]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Nov 07 00:43:21 starship systemd[1]: Started Network Manager Script Dispatcher Service.
Nov 07 00:43:21 starship 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'
Nov 07 00:43:21 starship kernel: audit: type=1130 audit(1636245801.470:285): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 07 00:43:21 starship systemd[1]: NetworkManager.service: Deactivated successfully.
Nov 07 00:43:21 starship systemd[1]: Stopped Network Manager.
Nov 07 00:43:21 starship audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 07 00:43:21 starship systemd[1]: Starting Network Manager...
Nov 07 00:43:21 starship kernel: audit: type=1131 audit(1636245801.484:286): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5004] NetworkManager (version 1.32.12-1) is starting... (after a restart)
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5004] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf) (etc: dhcp-client.conf)
Nov 07 00:43:21 starship systemd[1]: Started Network Manager.
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5023] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Nov 07 00:43:21 starship audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 07 00:43:21 starship kernel: audit: type=1130 audit(1636245801.497:287): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 07 00:43:21 starship flameshot[78595]: propsReply "Object does not exist at path “/org/freedesktop/NetworkManager”"
Nov 07 00:43:21 starship sudo[83060]: pam_unix(sudo:session): session closed for user root
Nov 07 00:43:21 starship audit[83060]: USER_END pid=83060 uid=1000 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Nov 07 00:43:21 starship audit[83060]: CRED_DISP pid=83060 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Nov 07 00:43:21 starship flameshot[78595]: nmReply "Object does not exist at path “/org/freedesktop/NetworkManager”"
Nov 07 00:43:21 starship kernel: audit: type=1106 audit(1636245801.500:288): pid=83060 uid=1000 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Nov 07 00:43:21 starship kernel: audit: type=1104 audit(1636245801.500:289): pid=83060 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5072] manager[0x55a58bd160b0]: monitoring kernel firmware directory '/lib/firmware'.
Nov 07 00:43:21 starship dbus-daemon[296]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.126' (uid=0 pid=83066 comm="/usr/bin/NetworkManager --no-daemon ")
Nov 07 00:43:21 starship audit: BPF prog-id=34 op=LOAD
Nov 07 00:43:21 starship audit: BPF prog-id=35 op=LOAD
Nov 07 00:43:21 starship audit: BPF prog-id=36 op=LOAD
Nov 07 00:43:21 starship systemd[1]: Starting Hostname Service...
Nov 07 00:43:21 starship kernel: audit: type=1334 audit(1636245801.507:290): prog-id=34 op=LOAD
Nov 07 00:43:21 starship kernel: audit: type=1334 audit(1636245801.507:291): prog-id=35 op=LOAD
Nov 07 00:43:21 starship dbus-daemon[296]: [system] Successfully activated service 'org.freedesktop.hostname1'
Nov 07 00:43:21 starship systemd[1]: Started Hostname Service.
Nov 07 00:43:21 starship audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5802] hostname: hostname: using hostnamed
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5802] hostname: hostname changed from (none) to "starship"
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5804] dns-mgr[0x55a58bccd250]: init: dns=default,systemd-resolved rc-manager=symlink
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5806] manager[0x55a58bd160b0]: rfkill: Wi-Fi hardware radio set enabled
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5806] manager[0x55a58bd160b0]: rfkill: WWAN hardware radio set enabled
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5826] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.32.12-1/libnm-device-plugin-bluetooth.so)
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5856] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.32.12-1/libnm-device-plugin-team.so)
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5858] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.32.12-1/libnm-device-plugin-adsl.so)
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5860] Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.32.12-1/libnm-device-plugin-ovs.so)
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5861] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.32.12-1/libnm-device-plugin-wifi.so)
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5863] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.32.12-1/libnm-device-plugin-wwan.so)
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5864] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5865] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5865] manager: Networking is enabled by state file
Nov 07 00:43:21 starship NetworkManager[83066]: <warn>  [1636245801.5866] dhcp-init: DHCP client 'dhclient' not available
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5866] dhcp-init: Using DHCP client 'internal'
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5866] settings: Loaded settings plugin: keyfile (internal)
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5875] device (lo): carrier: link connected
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5877] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5880] device (enp0s20f0u8): carrier: link connected
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5883] manager: (enp0s20f0u8): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5888] manager: (enp0s20f0u8): assume: will attempt to assume matching connection 'Wired connection 2' (43fe9964-2337-39ea-a4af-b5e7d74505ac) (indicated)
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5888] device (enp0s20f0u8): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'assume')
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5892] device (enp0s20f0u8): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'assume')
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5896] device (enp0s20f0u8): Activation: starting connection 'Wired connection 2' (43fe9964-2337-39ea-a4af-b5e7d74505ac)
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5898] device (enp2s0): carrier: link connected
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5900] manager: (enp2s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/3)
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5904] manager: (enp2s0): assume: will attempt to assume matching connection 'Wired connection 1' (94b9962c-02f9-3463-834f-ff6f63f9efbf) (indicated)
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5904] device (enp2s0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'assume')
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5907] device (enp2s0): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'assume')
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5911] device (enp2s0): Activation: starting connection 'Wired connection 1' (94b9962c-02f9-3463-834f-ff6f63f9efbf)
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5924] ovsdb: Could not connect: No such file or directory
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5924] ovsdb: disconnected from ovsdb
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5927] device (enp0s20f0u8): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'assume')
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5930] device (enp0s20f0u8): state change: prepare -> config (reason 'none', sys-iface-state: 'assume')
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5932] device (enp2s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'assume')
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5933] device (enp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'assume')
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5936] device (enp0s20f0u8): state change: config -> ip-config (reason 'none', sys-iface-state: 'assume')
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5938] dhcp4 (enp0s20f0u8): activation: beginning transaction (timeout in 45 seconds)
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5941] device (enp2s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'assume')
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.5942] dhcp4 (enp2s0): activation: beginning transaction (timeout in 45 seconds)
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.6016] dhcp4 (enp0s20f0u8): state changed unknown -> bound, address=192.168.195.95
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.6022] device (enp0s20f0u8): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'assume')
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.6031] device (enp0s20f0u8): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'assume')
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.6032] device (enp0s20f0u8): state change: secondaries -> activated (reason 'none', sys-iface-state: 'assume')
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.6034] manager: NetworkManager state is now CONNECTED_LOCAL
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.6035] manager: NetworkManager state is now CONNECTED_SITE
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.6035] policy: set 'Wired connection 2' (enp0s20f0u8) as default for IPv4 routing and DNS
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.6036] policy: set 'Wired connection 1' (enp2s0) as default for IPv6 routing and DNS
Nov 07 00:43:21 starship dbus-daemon[296]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.126' (uid=0 pid=83066 comm="/usr/bin/NetworkManager --no-daemon ")
Nov 07 00:43:21 starship dbus-daemon[296]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.6077] device (enp0s20f0u8): Activation: successful, device activated.
Nov 07 00:43:21 starship NetworkManager[83066]: <info>  [1636245801.6257] dhcp6 (enp2s0): activation: beginning transaction (timeout in 45 seconds)
Nov 07 00:43:22 starship NetworkManager[83066]: <info>  [1636245802.2464] manager: NetworkManager state is now CONNECTED_GLOBAL
Nov 07 00:43:22 starship dbus-daemon[296]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.128' (uid=0 pid=83082 comm="sudo journalctl -b ")
Nov 07 00:43:22 starship dbus-daemon[296]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Nov 07 00:43:22 starship sudo[83082]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Nov 07 00:43:22 starship audit[83082]: USER_ACCT pid=83082 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="matt" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Nov 07 00:43:22 starship sudo[83082]:     matt : TTY=pts/0 ; PWD=/home/matt ; USER=root ; COMMAND=/sbin/journalctl -b
Nov 07 00:43:22 starship audit[83082]: CRED_REFR pid=83082 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Nov 07 00:43:22 starship sudo[83082]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Nov 07 00:43:22 starship audit[83082]: USER_START pid=83082 uid=1000 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'

Edit: enp0s20f0u8 is my phone with usb tethering on

(after timeout)

Nov 07 00:44:07 starship NetworkManager[83066]: <warn>  [1636245847.1836] dhcp4 (enp2s0): request timed out
Nov 07 00:44:07 starship NetworkManager[83066]: <info>  [1636245847.1837] dhcp4 (enp2s0): state changed unknown -> timeout
Nov 07 00:44:07 starship NetworkManager[83066]: <warn>  [1636245847.1842] dhcp6 (enp2s0): request timed out
Nov 07 00:44:07 starship NetworkManager[83066]: <info>  [1636245847.1843] dhcp6 (enp2s0): state changed unknown -> timeout
Nov 07 00:44:07 starship NetworkManager[83066]: <info>  [1636245847.1843] dhcp6 (enp2s0): canceled DHCP transaction
Nov 07 00:44:07 starship NetworkManager[83066]: <info>  [1636245847.1844] dhcp6 (enp2s0): state changed timeout -> terminated

Last edited by WhiteySpicy (2021-11-06 21:48:27)

seth · 2021-11-06 21:45:41

The *entire* journal, no greps or other filters.

The dhcp request gets canceled and retried.
I'd guess that you've competing network managing services, but that's unfounded and out of sheer experience of how users typically screw up stuff.

Edit: nope - the slightly longer segment shows that you were simply restarting NM.

sudo journalctl -b | curl -F 'f:1=<-' ix.io

Last edited by seth (2021-11-06 21:47:39)

WhiteySpicy · 2021-11-06 21:49:56

The entire journal: http://ix.io/3EeM

That is indeed true I have been getting awful performance and really high latency. And being the noob I am I screwed things up *yikes*

Last edited by WhiteySpicy (2021-11-06 21:53:09)

seth · 2021-11-06 21:54:40

Yeah, was the typical one

Nov 06 20:28:06 starship systemd-networkd[245]: enp2s0: Link UP
Nov 06 20:28:06 starship NetworkManager[297]: <info> [1636230486.9629] settings: (enp2s0): created default wired connection 'Wired connection 1'

Picker either systemd-networkd or networkmanager and disable the other one.
As a sanity check:

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

Also your crng is late

Nov 06 20:28:07 starship kernel: random: crng init done
Nov 06 20:28:07 starship kernel: random: 1 urandom warning(s) missed due to ratelimiting

https://wiki.debian.org/BoottimeEntropyStarvation - https://wiki.archlinux.org/title/Haveged

loqs · 2021-11-06 22:03:05

seth wrote:

Also your crng is late
Nov 06 20:28:07 starship kernel: random: crng init done
Nov 06 20:28:07 starship kernel: random: 1 urandom warning(s) missed due to ratelimiting
https://wiki.debian.org/BoottimeEntropyStarvation - https://wiki.archlinux.org/title/Haveged

haveged.service has a condition check preventing start on 5.6 or newer kernels https://github.com/jirka-h/haveged/blob … ed.service

WhiteySpicy · 2021-11-06 22:04:17

Now I actually got an ip address, I can ping ip addresses like "1.1.1.1, 8.8.8.8" really fast but pinging DNS addresses are extremely slow. I also am writing this on my phone cause even usb tethering doesn't help

By pinging I mean I can't even load websites

Last edited by WhiteySpicy (2021-11-06 22:04:45)

WhiteySpicy · 2021-11-06 23:08:20

Example of what I mean can be seen here:
https://streamable.com/ttkrrd

solskog · 2021-11-07 02:27:44

output from these commands ?

cat /etc/resolv.conf
...
time drill -D archlinux.org @8.8.8.8

WhiteySpicy · 2021-11-07 08:06:16

resolv.conf

# Generated by NetworkManager
nameserver 192.168.54.1

The output of "time drill -D archlinux.org @8.8.8.8" can be found here:
https://ibb.co/rvW2mjv

seth · 2021-11-07 08:10:43

Please post text, not images of it.
The drill fails and times out because of a pending network error, I don't think this is about your DNS.

seth wrote:

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

WhiteySpicy · 2021-11-07 08:21:45

Hi - yes the reason behind the image was I still dont have connection therefore I couldn't upload the text with my pc.

(again, sorry for uploading as a photo)

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

The result: https://ibb.co/hYHsvDj

Last edited by WhiteySpicy (2021-11-07 08:23:38)

seth · 2021-11-07 08:35:16

You've only systemd-networkd enabled, but not systemd-resolved, https://wiki.archlinux.org/title/System … _and_setup
https://wiki.archlinux.org/title/Systemd-resolved

If this is a fixed-location ethernet-only connection I'd personally not bother w/ any of that but disable systemd-networkd* and just use dhcpcd.

I still dont have connection

Now I actually got an ip address, I can ping ip addresses like "1.1.1.1, 8.8.8.8" really fast but pinging DNS addresses are extremely slow. I also am writing this on my phone cause even usb tethering doesn't help

WhiteySpicy · 2021-11-07 08:45:16

After enabling and starting systemd-resolved

When I try to ping any domain address:

ping: example.com: Name or service not known.

I can still ping ip addresses though, should I switch to dhcpcd?

Note: I also cannot access the router interface '192.168.1.1' it pends forever then Timeouts

Last edited by WhiteySpicy (2021-11-07 08:48:21)

seth · 2021-11-07 08:54:42

I can still ping ip addresses though
I also cannot access the router interface '192.168.1.1'

The phone tethers on 192.168.195.0/24 - if that's your network connection, you won't have a route to the 192.168.1.0/24 segment.

Stop and disable the systemd-network* and systemd-resolve* services and sockets, remove the phone and start and enable dhcpcd.
Post the output of "ip a; ip r"

WhiteySpicy · 2021-11-07 09:07:55

I haven't connected my phone since yesterday.

"ip a; ip r" piped into 'bat' for better readability:
https://ibb.co/HFvKvnZ

Dhcpcd gives me inet4 address starting with 169.254.xx.xx

Update: I can get an output on "time drill -D google.com @8.8.8.8":

https://ibb.co/6Zh52mn (piped into 'bat' for better readability)
Edit: Fixed Link

Last edited by WhiteySpicy (2021-11-07 09:19:54)

seth · 2021-11-07 09:19:13

Dhcpcd gives me inet4 address starting with 196.254.xx.xx

That's a link local address and you also get a lease on 192.168.1.102 - but it's not the default route.

Stop the dhcpcd.service, check "ip a; ip r" again - you should not have any IPv4 assigned and also no route.
Then run "dhcpcd -dB" and post the output.

Edit: you'll also be able to use the DNS globally by at least making 8.8.8.8 the entry in /etc/resolv.conf, but using 192.168.1.1 as DNS might still not work.

Last edited by seth (2021-11-07 09:21:01)

WhiteySpicy · 2021-11-07 09:23:37

seth wrote:

Stop the dhcpcd.service, check "ip a; ip r" again - you should not have any IPv4 assigned and also no route.

After stopping dhcpcd My ip route is empty but I still have a IPv4 address with the value "192.168.1.102"

WhiteySpicy · 2021-11-07 09:33:11

sudo dhcpcd -dB

(The output on the left is the first part and the output on the right is the second part [after line 44])
https://ibb.co/ScNVHHr

Edit: If I don't end it "requesting DHCPv6 information" errors and loops

Last edited by WhiteySpicy (2021-11-07 09:35:23)

WhiteySpicy · 2021-11-07 09:40:43

Added "domain station" to the resolv.conf and rebooting finally worked.

cat /etc/resolv.conf

domain station
nameserver 192.168.1.1

enp2s0: failed to request DHCPv6 information
enp2s0: requesting DHCPv6 information

Still loops in the output though.

seth · 2021-11-07 17:54:15

Since you now have a network connection (does it worg when rebooting w/ dhcpcd enabled?) please post a complete system journal (sudo journalctl -b | curl -F 'f:1=<-' ix.io) for inspection so we can ensure that there're no hidden remaining issues.

WhiteySpicy · 2021-11-11 12:13:39

Sorry for the late reply I was out of town for a few days everything seems okay here is the journal: http://ix.io/3EGi

seth · 2021-11-11 13:40:42

You're losing the carrier for about 15s after the boot.
Since this is

Nov 11 14:12:32 starship kernel: r8169 0000:02:00.0 eth0: RTL8168h/8111h, 2c:f0:5d:7e:90:7c, XID 541, IRQ 126

you may want to try https://archlinux.org/packages/community/x86_64/r8168/

WhiteySpicy · 2021-11-11 14:20:16

I have downloaded the package, can something go wrong if the carrier is lost? Cause whilst it's lost I'm probably not in the WM yet

Arch Linux

#1 2021-11-06 17:34:52

[SOLVED] Network Is not working

#2 2021-11-06 20:20:47

Re: [SOLVED] Network Is not working

#3 2021-11-06 21:40:22

Re: [SOLVED] Network Is not working

#4 2021-11-06 21:45:41

Re: [SOLVED] Network Is not working

#5 2021-11-06 21:49:56

Re: [SOLVED] Network Is not working

#6 2021-11-06 21:54:40

Re: [SOLVED] Network Is not working

#7 2021-11-06 22:03:05

Re: [SOLVED] Network Is not working

#8 2021-11-06 22:04:17

Re: [SOLVED] Network Is not working

#9 2021-11-06 23:08:20

Re: [SOLVED] Network Is not working

#10 2021-11-07 02:27:44

Re: [SOLVED] Network Is not working

#11 2021-11-07 08:06:16

Re: [SOLVED] Network Is not working

#12 2021-11-07 08:10:43

Re: [SOLVED] Network Is not working

#13 2021-11-07 08:21:45

Re: [SOLVED] Network Is not working

#14 2021-11-07 08:35:16

Re: [SOLVED] Network Is not working

#15 2021-11-07 08:45:16

Re: [SOLVED] Network Is not working

#16 2021-11-07 08:54:42

Re: [SOLVED] Network Is not working

#17 2021-11-07 09:07:55

Re: [SOLVED] Network Is not working

#18 2021-11-07 09:19:13

Re: [SOLVED] Network Is not working

#19 2021-11-07 09:23:37

Re: [SOLVED] Network Is not working

#20 2021-11-07 09:33:11

Re: [SOLVED] Network Is not working

#21 2021-11-07 09:40:43

Re: [SOLVED] Network Is not working

#22 2021-11-07 17:54:15

Re: [SOLVED] Network Is not working

#23 2021-11-11 12:13:39

Re: [SOLVED] Network Is not working

#24 2021-11-11 13:40:42

Re: [SOLVED] Network Is not working

#25 2021-11-11 14:20:16

Re: [SOLVED] Network Is not working

Board footer