On 02/12/2023 05:33, Greg Wooledge wrote:
In either case, the static-ness or dynamic-ness of the address is much
less important than the fact that the address*works*. You are able
to communicate with the printer, using your network.
This means the printer should be able to communicate*back*, and
specifically, it should be able to contact an NTP server on your network
to synchronize its system clock.
My guest is that a 169.254.x.y address allows to connect from other
hosts that belongs to the same network segment, but the router discards
outgoing packets instead of applying masquerading rules. Or the host
does not send non-local packets because it does not know a router and no
hosts respond to ARP requests.
Having IPv4LL addresses, it is possible to connect to other hosts
withing the same subnet using multicast mDNS (name.local) or LLMNR name
resolution.
Actually having a spare ethernet port or a WiFi card that supports hot
spot mode, it is possible to create a subnet for this 3d printer.
NetworkManager allows to create a "shared" connection with a few clicks.
It launches dnsmasq as DNS and DHCP server. The only downside is NAT, so
ssh to the printer will require to connect the host sharing network.
However it will solve the NTP issue.
