Hi everyone,
Rather. odd bug or behavior, here is my problem :
New Pi5 + Raspberry Pi OS Lite 64 bit ( 2023-12-11-raspios-bookworm-arm64-lite.img) + wired network connection.
( I noticed that a newer image has been just released but the behavior happens anyway as I have upgraded all Debian packages to their latest version)
Everything installs and run just fine as long I don't change my IP address which I receive through DHCP.
As soon as I change from DHCP to static IP address (either with Network Manager or by disabling Network Manager and using /etc/network/interfaces(.d/ethO), then *SOME* TCP connections won't be usable. Looking deeper, I notice that I can't establish TLS connections with my Postfix or Dovecot server.
As soon as I delete my static IP address and switch back to DHCP (eth0 handled by Network Manager), then i can use TLS again.
Easiest way to reproduce :
1/ Install Raspberry Pi 64bit OS Lite image
2/ nmcli con mod "Wired connection 1" ipv4.addresses 192.168.0.1/24
3/ nmcli con mod "Wired connection 1" ipv4.meethod manual
4/ Reboot. TLS connections can't be established
To "solve" the issue, I only need to go back to DHCP :
1/ lookup NM connection UUID
2/ nmcli con delete UUID
3/ reboot . TLS connections can be established again.
Thanks for your help.
Phil0u
Rather. odd bug or behavior, here is my problem :
New Pi5 + Raspberry Pi OS Lite 64 bit ( 2023-12-11-raspios-bookworm-arm64-lite.img) + wired network connection.
( I noticed that a newer image has been just released but the behavior happens anyway as I have upgraded all Debian packages to their latest version)
Everything installs and run just fine as long I don't change my IP address which I receive through DHCP.
As soon as I change from DHCP to static IP address (either with Network Manager or by disabling Network Manager and using /etc/network/interfaces(.d/ethO), then *SOME* TCP connections won't be usable. Looking deeper, I notice that I can't establish TLS connections with my Postfix or Dovecot server.
As soon as I delete my static IP address and switch back to DHCP (eth0 handled by Network Manager), then i can use TLS again.
Easiest way to reproduce :
1/ Install Raspberry Pi 64bit OS Lite image
2/ nmcli con mod "Wired connection 1" ipv4.addresses 192.168.0.1/24
3/ nmcli con mod "Wired connection 1" ipv4.meethod manual
4/ Reboot. TLS connections can't be established
To "solve" the issue, I only need to go back to DHCP :
1/ lookup NM connection UUID
2/ nmcli con delete UUID
3/ reboot . TLS connections can be established again.
Thanks for your help.
Phil0u
Statistics: Posted by phil0u — Sat Mar 16, 2024 5:37 pm