Displaying 2 results from an estimated 2 matches for "tftpdmachin".
Did you mean:
tftpdmachine
2017 Feb 05
2
tftpd: don't use AI_ADDRCONFIG to resolve addresses to bind(2)
...at. The result is that eth0 doesn't
have an ipv4 address. You notice that because a tftp-client tries to
contact the tftpd server and doesn't get an answer. So what to do next?
I assume your next step is logging into the tftpd-machine and check if
tftpd is running. (If instead you try ping $tftpdmachine, or check the
network config of the tftpd-machine, it doesn't actually help you that
tftpd isn't running as it is already obvious then that the network
configuration is at fault and not tftpd.) You see it doesn't run, check
the log and see
cannot resolve local IPv4 bind address: 0.0....
2017 Feb 04
2
tftpd: don't use AI_ADDRCONFIG to resolve addresses to bind(2)
Hello Ron,
On Sat, Feb 04, 2017 at 03:46:46PM +1030, Ron wrote:
> > [...]
> That would seem to be a pretty good summation of how we're failing to
> converge here ...
I mixed too many things that IMHO improve the code but actually only
care about one of those. So I suggest we restart the discussion with
focusing on that one thing only. Let me try that:
Currently tftpd when