Comment

PriorityMotif@lemmy.world ⁨1⁩ ⁨week⁩ ago

I was correct that it is a networking error
cannot bind to local IPv4 socket: Cannot assign requested address current inet says: enp7s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 169.254.210.0 netmask 255.255.0.0 broadcast 169.254.255.255 inet6 fe80::9a40:bbff:fe28:459b prefixlen 64 scopeid 0x20<link> ether 98:40:bb:28:45:9b txqueuelen 1000 (Ethernet) RX packets 15 bytes 900 (900.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1466 bytes 492951 (492.9 KB) TX errors 0 dropped 78 overruns 0 carrier 0 collisions 0

source

Sort:hotnew top

tal@lemmy.today ⁨1⁩ ⁨week⁩ ago

cannot bind to local IPv4 socket: Cannot assign requested address

inet 169.254.210.0

Yeah. That’ll be that you needing an interface with that address assigned.

ifconfig

Going from memory, I believe that if you’ve got ifconfig available and this is a Linux system and you need to keep the address on the current interface to keep the system connected to the Internet or something, you can use something like ifconfig enp7s0:0 10.10.10.3 to use an interface alias, use both addresses (169.254.210.0 and 10.10.10.3) at the same time. Might also need ifconfig enp7s0:0 up after that. That being said, (a) I don’t think that I’ve set up an interface alias in probably a decade, and it’s possible that’s something has changed, (b) that’s a bit of additional complexity, and if you aren’t super familiar with Linux networking, you might not want to add more complexity if you don’t mind dropping just setting the address on the interface to something else.

Probably an iproute2-based approach to do this too (the ip command rather than the ifconfig command) but I haven’t bothered to pick up iproute2 equivalents for a bunch of stuff.

source
- non_burglar@lemmy.world ⁨1⁩ ⁨week⁩ ago
  An apipa address is a sign that networking is not working as intended. This should be resolved first before assigning a class C private addr manually.
  
  source