this post was submitted on 23 Apr 2025
35 points (100.0% liked)
Tech
1041 readers
120 users here now
A community for high quality news and discussion around technological advancements and changes
Things that fit:
- New tech releases
- Major tech changes
- Major milestones for tech
- Major tech news such as data breaches, discontinuation
Things that don't fit
- Minor app updates
- Government legislation
- Company news
- Opinion pieces
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Today, at $DAYJOB, we wanted to assign a temporary IP address to the Ethernet port of a Raspberry Pi, so we could connect an Ethernet cable to it and SSH in. We considered using an IPv6 address for that, because there's a lower chance of someone already using that IP address.
But as far as we could tell (didn't investigate terribly long), NetworkManager in Linux will kill a connection, if it does not get an IPv4 address in time, because it assumes there to be a DHCP server behind an Ethernet port. So, we decided to just use an IPv4 address instead.
I'm sure there's ways to make NetworkManager not do that, but those involve additional steps and complexity. And yeah, it's just kind of ridiculous to me, that we built these workarounds, like DHCP, to make IPv4 work and then the defaults assume those workarounds to be in place, which means the IPv6 experience is worse than the IPv4 experience with its workarounds...