Evening all,
Trying to get my server, running atftpd, to respond to an incoming TFTP request from a device running in auto-config mode. The DHCP server responds as expected and, following the DHCPACK, the device sends in a request for its configuration file.
TCPDUMP give us this:
23:46:17.468168 IP 10.0.0.3.1024 > mesh.tftp: 20 RRQ “fdnplc.conf” octet
23:46:17.469610 IP 10.0.0.3.1024 > mesh.tftp: 6 ERROR EUNDEF "
mesh is the name of the machine at config level, not DNS or anything.
fdnplc.conf is the name of the file I want the device to download. It is in /tftpboot.
The sysconfig for atftpd is this:
ATFTPD_USE_INETD=“no”
ATFTPD_DIRECTORY="/tftpboot"
ATFTPD_BIND_ADDRESSES=“10.0.0.1”
So, what is that ‘octet’ doing at the end of the line. What is 1024 in this case? The assumed server port? I thought the standard port was 69.
And 6 error eundef? Opcode 6 is, I gather, the acknowledgement. I assume this is simply the device reporting that it got no ack to its request??
octet is the transfer mode = binary (hardly anyone uses the other mode: ascii)
1024 is the client side port.
Don’t know why your client is sending an error code of EUNDEF (that is the error string and the client makes it up). You might know better from context.
Looks like you are only seeing one side of the conversation with tcpdump.
Ok, thanks for this. I guess the essential question here is this: under what circumstances would a TFTP sever not reply at all to a RRQ, not even with so much as a ‘I don’t have the file, the request is badly formed, just go away…’
The TFTP server is running.
Also, where does atftpd write its log? I looked in var/log/messages, but there was nothing at all to do with the TFTP ‘exchange’. Possibly because as far as the server is concerned, nothing happened?
>
> Ok, thanks for this. I guess the essential question here is this:
> under what circumstances would a TFTP sever not reply at all to a RRQ,
> not even with so much as a ‘I don’t have the file, the request is badly
> formed, just go away…’
>
> The TFTP server is running.
>
> Also, where does atftpd write its log? I looked in var/log/messages,
> but there was nothing at all to do with the TFTP ‘exchange’. Possibly
> because as far as the server is concerned, nothing happened?
>
> sparkie
>
>
Have you checked your firewall settings? openSUSE installs default to being
fully firewalled. Either disable your firewall (as long as you are otherwise
protected), or add port 69 to the permitted open ports.
