I haven’t done anything with OpenWRT for a lomg time, but…

I have the IP of the server set to 0.0.0.0:69 when I try to set it to 10.10.10.3 (per the wiki) The server on my pc won’t start and gives an error.

I’m pretty sure that you can’t use all zeroes as an IP address.

kagis

https://en.wikipedia.org/wiki/0.0.0.0

RFC 1122 refers to 0.0.0.0 using the notation {0,0}. It prohibits this as a destination address in IPv4 and only allows it as a source address during the initialization process, when the host is attempting to obtain its own address.

As it is limited to use as a source address and prohibited as a destination address, setting the address to 0.0.0.0 explicitly specifies that the target is unavailable and non-routable.

You probably need to figure out why your TFTP server is unhappy with 10.10.10.3, and there’s not enough information here to provide guidance on that. I don’t know what OS or software package you’re using or the error or the network config.

It may be that you don’t have any network interface with 10.10.10.3 assigned to it, which I believe might cause the TFTP server to fail to bind a socket to that address and port when it attempts to do so.

If you are manually invoking the TFTP server as a non-root user and trying to bind to port 69, and this is a Linux system, it will probably fail, as ports below 1024 are privileged ports and processes running as ordinary users cannot bind to them. That might cause a TFTP server package to bail out.

But I’m really just taking wild stabs in the dark, without any information about the software involved and the errors you’re seeing. I would probably recommend trying to make 10.10.10.3 work, though, not 0.0.0.0.

If this is a Linux system, you might use a packet sniffer on the TFTP host, like Wireshark or tcpdump, to diagnose any additional issues that come up, since that will let you see how the two devices are talking to each other. But if you can’t get the TFTP server to even run on an IP address, then you’re not to that point yet.