You have a fixed IP but still have dhcp enabled, "ipv4.method: auto". Try,I found some threads about similar problems but not about exactly this one. The Raspi has a fixed IPv4 address of 192.168.0.153/24, this was set via nmcli. After booting, all works fine, but after exactly three minutes the connection goes down, "ip a" showing onlyWhen I then perform (at the console) systemctl restart NetworkManager, all is fine for another three minutes, after which the issue repeats.Code:
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether b8:27:eb:eb:e9:4b brd ff:ff:ff:ff:ff:ff3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether b8:27:eb:be:bc:1e brd ff:ff:ff:ff:ff:ff
What could be wrong? What can I do to diagnose and localise the issue?
It is a newly installed RaspBerry 3B, with Raspbian version 12 (bookworm), kernel 6.6.51+rpt-rpi-v8 nmcli settings for ipv4:Code:
nmcli conn sho Wired\ connection\ 1 | grep ipv4 | grep -v '\-\-'ipv4.method: autoipv4.dns-priority: 0ipv4.addresses: 192.168.0.153/24ipv4.gateway: 192.168.0.254ipv4.route-metric: -1ipv4.route-table: 0 (unspec)ipv4.replace-local-rule: -1 (default)ipv4.ignore-auto-routes: noipv4.ignore-auto-dns: noipv4.dhcp-timeout: 0 (default)ipv4.dhcp-send-hostname: yesipv4.dhcp-hostname-flags: 0x0 (none)ipv4.never-default: noipv4.may-fail: yesipv4.required-timeout: -1 (default)ipv4.dad-timeout: -1 (default)ipv4.link-local: 0 (default)ipv4.auto-route-ext-gw: -1 (default)
Code:
sudo nmcli connection modify 'Wired connection 1' ipv4.method manual ipv4.addresses 192.168.0.153/24 ipv4.gateway 192.168.0.1254sudo nmcli connection reload 'Wired connection 1'sudo nmcli connection down 'Wired connection 1'sudo nmcli connection up 'Wired connection 1'Statistics: Posted by kmacdchap — Wed Oct 23, 2024 1:30 am