Quantcast
Channel: Raspberry Pi Forums
Viewing all articles
Browse latest Browse all 4585

Advanced users • Trying to get Pi -> eth -> MacBook working, but NetworkManager keeps failing with `ip-config-unavailable`

$
0
0
Hello, I'm using the Dec. 2023 release of RPi OS, and am setting up an ethernet connection between my MacBook and my Raspberry Pi 3B. This does use the local-link connection, and I am able to see a connection on my MacBook for en7:

Code:

en7: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500options=6464<VLAN_MTU,TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>ether a0:ce:c8:0d:8f:4binet6 fe80::14c3:b7cf:39d6:c8e6%en7 prefixlen 64 secured scopeid 0x1ainet 169.254.17.250 netmask 0xffff0000 broadcast 169.254.255.255nd6 options=201<PERFORMNUD,DAD>media: autoselect (1000baseT <full-duplex>)status: active
I'm even able to SSH into the Raspberry Pi using its local mDNS. `nmcli c` shows:

Code:

NAME                UUID                                  TYPE      DEVICEWired connection 1  4ba9bd4a-74e2-32b7-9df8-6b7aa5e71248  ethernet  eth0lo                  f8b47560-2800-4fad-9c59-d48dc305ba5a  loopback  loethernet-enp1s0     aa8b20d1-64c4-44ad-9405-27dcd264d8b0  ethernet  --local               2d9c24be-1a26-4e6f-80a1-3cfe942990b7  ethernet  --local               5bf84816-0b03-44fd-ad2a-e1282641e57f  ethernet  --
However, the connection is unstable. After about 3min, the connection crashes, and the some time later (~10m), I can access the Pi again, and this repeats.

Looking into the `journalctl`, I see often repeated logs corresponding to the crashes:

Code:

Mar 25 12:52:12 leader24319 NetworkManager[525]: <info>  [1711385532.3309] device (eth0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')Mar 25 12:52:12 leader24319 NetworkManager[525]: <info>  [1711385532.3334] manager: NetworkManager state is now DISCONNECTEDMar 25 12:52:12 leader24319 NetworkManager[525]: <warn>  [1711385532.3352] device (eth0): Activation: failed for connection 'Wired connection 1'Mar 25 12:52:12 leader24319 NetworkManager[525]: <info>  [1711385532.3368] device (eth0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')Mar 25 12:52:12 leader24319 avahi-daemon[478]: Withdrawing address record for fe80::938a:f840:1222:c356 on eth0.Mar 25 12:52:12 leader24319 avahi-daemon[478]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::938a:f840:1222:c356.Mar 25 12:52:12 leader24319 avahi-daemon[478]: Interface eth0.IPv6 no longer relevant for mDNS.Mar 25 12:52:12 leader24319 NetworkManager[525]: <info>  [1711385532.4274] dhcp4 (eth0): canceled DHCP transactionMar 25 12:52:12 leader24319 NetworkManager[525]: <info>  [1711385532.4276] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)Mar 25 12:52:12 leader24319 NetworkManager[525]: <info>  [1711385532.4277] dhcp4 (eth0): state changed no lease
I've tried a few solutions:

`nmcli connection modify "Wired connection 1" ipv4.method auto`

and

` sudo nmcli c mod "Wired connection 1" ipv4.addresses 169.254.1.1/24`

neither of which provide a stable connection.

Does anyone have another test or solution I can try?

Statistics: Posted by CamDP — Mon Mar 25, 2024 6:58 pm — Replies 0 — Views 12



Viewing all articles
Browse latest Browse all 4585

Trending Articles