Arch not connecting with Raspberry Pi

khatrimann · 2021-02-11 07:48:52

I am having problems connecting my Arch to Raspberry Pi 3 via ethernet. I am having Realtek r8169. Though internet is working but when I connect it to my Raspberry Pi, it shows

wire connecting

The Ethernet and Raspberry Pi perfectly connects in windows.
dhcpcd is turned on
Ethernet light blinks on both the ports

Edit: For better understanding (re-used from #6)

the command

ip a

gives the following results

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: enp8s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether f0:76:1c:b5:90:5a brd ff:ff:ff:ff:ff:ff
inet6 fe80::2e3b:cf60:a682:b685/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: wlp9s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether ac:e0:10:22:88:e3 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.7/24 brd 192.168.1.255 scope global dynamic noprefixroute wlp9s0
valid_lft 86215sec preferred_lft 86215sec
inet6 fe80::31e8:7f66:951a:9c53/64 scope link noprefixroute
valid_lft forever preferred_lft forever

Command

ip r

gives

default via 192.168.1.1 dev wlp9s0 proto dhcp metric 600
192.168.1.0/24 dev wlp9s0 proto kernel scope link src 192.168.1.7 metric 600

Wired Connecting: Like I said it keeps showing Wired connecting
Auth Failure

The cables are perfectly fine and works in my Windows 10.
In my Linux when I attach cable to router (for internet) then plug it into Arch, it shows Wire Connected but when I plug one ned to Pi and other to my Arch it shows Wired connecting and then Auth Failure. In short, ethernet is working as it is tested on windows (router and Pi) and Linux (router) but unable to get connected to Raspberry Pi (on Arch)

Last edited by khatrimann (2021-02-15 20:26:26)

seth · 2021-02-11 08:24:29

when I connect it to my Raspberry Pi, it shows ```wire connecting```

How do you "connect" it and what shows "wire connecting"?

Though internet is working

So is this about some status indicator only? Which one?

khatrimann · 2021-02-13 18:46:44

In my windows, I simply connect ethernet on both ends and then can use remote desktop feature in windows to access my raspberry (raspbian)
but on arch in to right menu (GNOME) it shows ```wire connecting```

seth · 2021-02-13 21:42:29

That doesn't really add anything.
Post the output of

ip a
ip r
ping -c3 8.8.8.8

and a screenshot (with reasonable context!) of whatever "right menu (GNOME)" is.
Can you ping the raspi?

khatrimann · 2021-02-15 20:23:41

Just a min

Last edited by khatrimann (2021-02-15 20:24:52)

khatrimann · 2021-02-15 20:24:19

seth wrote:

That doesn't really add anything.
Post the output of
ip a
ip r
ping -c3 8.8.8.8
and a screenshot (with reasonable context!) of whatever "right menu (GNOME)" is.
Can you ping the raspi?

the command

ip a

gives the following results

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: enp8s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether f0:76:1c:b5:90:5a brd ff:ff:ff:ff:ff:ff
inet6 fe80::2e3b:cf60:a682:b685/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: wlp9s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether ac:e0:10:22:88:e3 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.7/24 brd 192.168.1.255 scope global dynamic noprefixroute wlp9s0
valid_lft 86215sec preferred_lft 86215sec
inet6 fe80::31e8:7f66:951a:9c53/64 scope link noprefixroute
valid_lft forever preferred_lft forever

Command

ip r

gives

default via 192.168.1.1 dev wlp9s0 proto dhcp metric 600
192.168.1.0/24 dev wlp9s0 proto kernel scope link src 192.168.1.7 metric 600

Wired Connecting: Like I said it keeps showing Wired connecting
Auth Failure

The cables are perfectly fine and works in my Windows 10.
In my Linux when I attach cable to router (for internet) then plug it into Arch, it shows Wire Connected but when I plug one ned to Pi and other to my Arch it shows Wired connecting and then Auth Failure. In short, ethernet is working as it is tested on windows (router and Pi) and Linux (router) but unable to get connected to Raspberry Pi (on Arch)

Edit: I suppose DHCP server is not the problem as when connecting to router for internet via ethernet, IP is assigned

Last edited by khatrimann (2021-02-15 20:32:55)

seth · 2021-02-15 21:04:28

I suppose DHCP server is not the problem as when connecting to router for internet via ethernet, IP is assigned

Actually, that suggest that the dhcp server *is* the problem. Also that you've a carrier and the network is up - you just don't get a lease on enp8s0.

I assume 192.168.1.7/24 on wlp9s0 is from your router dhcp?
Try to rfkill that, so whatever is configuring your network (i assume NM?) doesn't have to deal w/ two dhcp servers.
Do you then get a lease on enp8s0?

Please post the complete system journal after plugging the cable (sudo journalctl -b)

khatrimann · 2021-02-15 21:41:03

seth wrote:

I suppose DHCP server is not the problem as when connecting to router for internet via ethernet, IP is assigned
Actually, that suggest that the dhcp server *is* the problem. Also that you've a carrier and the network is up - you just don't get a lease on enp8s0.
I assume 192.168.1.7/24 on wlp9s0 is from your router dhcp?
Try to rfkill that, so whatever is configuring your network (i assume NM?) doesn't have to deal w/ two dhcp servers.
Do you then get a lease on enp8s0?
Please post the complete system journal after plugging the cable (sudo journalctl -b)

Yes NM is being used
Please can you help me with the commands because I am not able to do it

[mann@mann ~]$ rfkill list
0: ideapad_wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
1: ideapad_bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
3: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

and

rfkill block wifi

just turn off the wifi but ethernet continuously shows connecting

seth · 2021-02-15 22:00:06

Turning off the wifi is the point, but plug the ethernet *after* you did that.

khatrimann · 2021-02-15 22:08:29

seth wrote:

Turning off the wifi is the point, but plug the ethernet *after* you did that.

No luck

Feb 16 03:36:24 mann kernel: audit: type=1105 audit(1613426784.492:200): pid=9279 uid=1000 auid=1000 ses=4 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Feb 16 03:36:24 mann dhclient[9077]: DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 12
Feb 16 03:36:25 mann sudo[9279]: pam_unix(sudo:session): session closed for user root
Feb 16 03:36:25 mann audit[9279]: USER_END pid=9279 uid=1000 auid=1000 ses=4 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Feb 16 03:36:25 mann audit[9279]: CRED_DISP pid=9279 uid=1000 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Feb 16 03:36:25 mann kernel: audit: type=1106 audit(1613426785.932:201): pid=9279 uid=1000 auid=1000 ses=4 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Feb 16 03:36:25 mann kernel: audit: type=1104 audit(1613426785.932:202): pid=9279 uid=1000 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Feb 16 03:36:34 mann dbus-daemon[402]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.205' (uid=0 pid=9283 comm="sudo journalctl -b ")
Feb 16 03:36:34 mann dbus-daemon[402]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Feb 16 03:36:34 mann sudo[9283]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Feb 16 03:36:34 mann audit[9283]: USER_ACCT pid=9283 uid=1000 auid=1000 ses=4 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="mann" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Feb 16 03:36:34 mann sudo[9283]: mann : TTY=pts/2 ; PWD=/home/mann ; USER=root ; COMMAND=/usr/bin/journalctl -b
Feb 16 03:36:34 mann audit[9283]: CRED_REFR pid=9283 uid=1000 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Feb 16 03:36:34 mann kernel: audit: type=1101 audit(1613426794.892:203): pid=9283 uid=1000 auid=1000 ses=4 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="mann" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Feb 16 03:36:34 mann kernel: audit: type=1110 audit(1613426794.892:204): pid=9283 uid=1000 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Feb 16 03:36:34 mann sudo[9283]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Feb 16 03:36:34 mann audit[9283]: USER_START pid=9283 uid=1000 auid=1000 ses=4 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Feb 16 03:36:34 mann kernel: audit: type=1105 audit(1613426794.902:205): pid=9283 uid=1000 auid=1000 ses=4 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Feb 16 03:36:34 mann sudo[9283]: pam_unix(sudo:session): session closed for user root
Feb 16 03:36:34 mann audit[9283]: USER_END pid=9283 uid=1000 auid=1000 ses=4 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Feb 16 03:36:34 mann audit[9283]: CRED_DISP pid=9283 uid=1000 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Feb 16 03:36:34 mann kernel: audit: type=1106 audit(1613426794.912:206): pid=9283 uid=1000 auid=1000 ses=4 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Feb 16 03:36:34 mann kernel: audit: type=1104 audit(1613426794.912:207): pid=9283 uid=1000 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Feb 16 03:36:36 mann dhclient[9077]: DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 11
Feb 16 03:36:37 mann NetworkManager[6927]: <warn> [1613426797.8184] dhcp4 (enp8s0): request timed out
Feb 16 03:36:37 mann NetworkManager[6927]: <info> [1613426797.8186] dhcp4 (enp8s0): state changed unknown -> timeout
Feb 16 03:36:37 mann NetworkManager[6927]: <info> [1613426797.8188] device (enp8s0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Feb 16 03:36:37 mann NetworkManager[6927]: <info> [1613426797.8205] manager: NetworkManager state is now DISCONNECTED
Feb 16 03:36:37 mann NetworkManager[6927]: <warn> [1613426797.8247] device (enp8s0): Activation: failed for connection 'Wired connection 1'
Feb 16 03:36:37 mann NetworkManager[6927]: <info> [1613426797.8257] device (enp8s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Feb 16 03:36:37 mann NetworkManager[6927]: <info> [1613426797.8921] dhcp4 (enp8s0): canceled DHCP transaction, DHCP client pid 9077
Feb 16 03:36:37 mann NetworkManager[6927]: <info> [1613426797.8921] dhcp4 (enp8s0): state changed timeout -> done
Feb 16 03:36:37 mann NetworkManager[6927]: <info> [1613426797.9048] policy: auto-activating connection 'Wired connection 1' (4c2fb2e1-8456-3dcc-ad24-240585626d6b)
Feb 16 03:36:37 mann NetworkManager[6927]: <info> [1613426797.9064] device (enp8s0): Activation: starting connection 'Wired connection 1' (4c2fb2e1-8456-3dcc-ad24-240585626d6b)
Feb 16 03:36:37 mann NetworkManager[6927]: <info> [1613426797.9066] device (enp8s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Feb 16 03:36:37 mann NetworkManager[6927]: <info> [1613426797.9073] manager: NetworkManager state is now CONNECTING
Feb 16 03:36:37 mann NetworkManager[6927]: <info> [1613426797.9077] device (enp8s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Feb 16 03:36:37 mann NetworkManager[6927]: <info> [1613426797.9086] device (enp8s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Feb 16 03:36:37 mann NetworkManager[6927]: <info> [1613426797.9094] dhcp4 (enp8s0): activation: beginning transaction (timeout in 45 seconds)
Feb 16 03:36:37 mann dbus-daemon[402]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.168' (uid=0 pid=6927 comm="/usr/bin/NetworkManager --no-daemon ")
Feb 16 03:36:37 mann systemd[1]: Starting Network Manager Script Dispatcher Service...
Feb 16 03:36:37 mann NetworkManager[6927]: <info> [1613426797.9182] dhcp4 (enp8s0): dhclient started with pid 9290
Feb 16 03:36:37 mann dbus-daemon[402]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Feb 16 03:36:37 mann systemd[1]: Started Network Manager Script Dispatcher Service.
Feb 16 03:36:37 mann 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'
Feb 16 03:36:37 mann kernel: audit: type=1130 audit(1613426797.932:208): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 16 03:36:37 mann dhclient[9290]: DHCPREQUEST for 192.168.1.18 on enp8s0 to 255.255.255.255 port 67
Feb 16 03:36:39 mann dbus-daemon[402]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.207' (uid=0 pid=9304 comm="sudo journalctl -b ")
Feb 16 03:36:39 mann dbus-daemon[402]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Feb 16 03:36:39 mann sudo[9304]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Feb 16 03:36:39 mann audit[9304]: USER_ACCT pid=9304 uid=1000 auid=1000 ses=4 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="mann" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Feb 16 03:36:39 mann sudo[9304]: mann : TTY=pts/2 ; PWD=/home/mann ; USER=root ; COMMAND=/usr/bin/journalctl -b
Feb 16 03:36:39 mann audit[9304]: CRED_REFR pid=9304 uid=1000 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Feb 16 03:36:39 mann sudo[9304]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Feb 16 03:36:39 mann audit[9304]: USER_START pid=9304 uid=1000 auid=1000 ses=4 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Feb 16 03:36:39 mann kernel: audit: type=1101 audit(1613426799.782:209): pid=9304 uid=1000 auid=1000 ses=4 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="mann" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Feb 16 03:36:39 mann kernel: audit: type=1110 audit(1613426799.782:210): pid=9304 uid=1000 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Feb 16 03:36:39 mann kernel: audit: type=1105 audit(1613426799.782:211): pid=9304 uid=1000 auid=1000 ses=4 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Feb 16 03:36:39 mann sudo[9304]: pam_unix(sudo:session): session closed for user root
Feb 16 03:36:39 mann audit[9304]: USER_END pid=9304 uid=1000 auid=1000 ses=4 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Feb 16 03:36:39 mann audit[9304]: CRED_DISP pid=9304 uid=1000 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Feb 16 03:36:39 mann kernel: audit: type=1106 audit(1613426799.972:212): pid=9304 uid=1000 auid=1000 ses=4 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Feb 16 03:36:39 mann kernel: audit: type=1104 audit(1613426799.972:213): pid=9304 uid=1000 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Feb 16 03:36:43 mann dhclient[9290]: DHCPREQUEST for 192.168.1.18 on enp8s0 to 255.255.255.255 port 67
Feb 16 03:36:47 mann systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Feb 16 03:36:47 mann 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'
Feb 16 03:36:47 mann kernel: audit: type=1131 audit(1613426807.802:214): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 16 03:36:58 mann dbus-daemon[402]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.208' (uid=0 pid=9312 comm="sudo journalctl -b ")
Feb 16 03:36:58 mann audit[9312]: USER_ACCT pid=9312 uid=1000 auid=1000 ses=4 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="mann" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Feb 16 03:36:58 mann kernel: audit: type=1101 audit(1613426818.272:215): pid=9312 uid=1000 auid=1000 ses=4 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="mann" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Feb 16 03:36:58 mann dbus-daemon[402]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Feb 16 03:36:58 mann sudo[9312]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Feb 16 03:36:58 mann audit[9312]: CRED_REFR pid=9312 uid=1000 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Feb 16 03:36:58 mann sudo[9312]: mann : TTY=pts/2 ; PWD=/home/mann ; USER=root ; COMMAND=/usr/bin/journalctl -b
Feb 16 03:36:58 mann sudo[9312]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Feb 16 03:36:58 mann audit[9312]: USER_START pid=9312 uid=1000 auid=1000 ses=4 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Feb 16 03:36:58 mann kernel: audit: type=1110 audit(1613426818.282:216): pid=9312 uid=1000 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Feb 16 03:36:58 mann kernel: audit: type=1105 audit(1613426818.282:217): pid=9312 uid=1000 auid=1000 ses=4 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'

seth · 2021-02-15 22:26:16

Please use "code" tags, not "quote" tags.

Feb 16 03:36:37 mann dhclient[9290]: DHCPREQUEST for 192.168.1.18 on enp8s0 to 255.255.255.255 port 67

I assume the dhcp server on the raspi doesn't operate on the same subnet as your router, 192.168.1.18 is the IP you got from the router (same subnet as wifi) and NM tries to preserve that.
=> What if you restart the NM service after unplugging the ethernet and before connecting it to the raspi?

khatrimann · 2021-02-15 22:47:02

seth wrote:

Please use "code" tags, not "quote" tags.
Feb 16 03:36:37 mann dhclient[9290]: DHCPREQUEST for 192.168.1.18 on enp8s0 to 255.255.255.255 port 67
I assume the dhcp server on the raspi doesn't operate on the same subnet as your router, 192.168.1.18 is the IP you got from the router (same subnet as wifi) and NM tries to preserve that.
=> What if you restart the NM service after unplugging the ethernet and before connecting it to the raspi?

Tried restarting services using all combinations. None worked

seth · 2021-02-15 22:53:26

Updated journal?
Can you please clarify the IP ranges for router and raspi and whether 192.168.1.18 is the IP that you got from the router?

Also: What if you stop NM, bring enp8s0 up and query "sudo dhclient -dv enp8s0"?

Arch Linux

#1 2021-02-11 07:48:52

Arch not connecting with Raspberry Pi

#2 2021-02-11 08:24:29

Re: Arch not connecting with Raspberry Pi

#3 2021-02-13 18:46:44

Re: Arch not connecting with Raspberry Pi

#4 2021-02-13 21:42:29

Re: Arch not connecting with Raspberry Pi

#5 2021-02-15 20:23:41

Re: Arch not connecting with Raspberry Pi

#6 2021-02-15 20:24:19

Re: Arch not connecting with Raspberry Pi

#7 2021-02-15 21:04:28

Re: Arch not connecting with Raspberry Pi

#8 2021-02-15 21:41:03

Re: Arch not connecting with Raspberry Pi

#9 2021-02-15 22:00:06

Re: Arch not connecting with Raspberry Pi

#10 2021-02-15 22:08:29

Re: Arch not connecting with Raspberry Pi

#11 2021-02-15 22:26:16

Re: Arch not connecting with Raspberry Pi

#12 2021-02-15 22:47:02

Re: Arch not connecting with Raspberry Pi

#13 2021-02-15 22:53:26

Re: Arch not connecting with Raspberry Pi

Board footer