Re: The OACK Project
On Wed, Jan 24, 2007 at 12:41:23PM +0100, Rogier Krieger wrote: > On 1/24/07, Jonathan Eifrig <[EMAIL PROTECTED]> wrote: > >tftpd[]: oack: Permission denied > > That may have something to do with *file* permissions. Quoting tftpd(8): > > "The use of tftp(1) does not require an account or password on the remote > system. Due to the lack of authentication information, tftpd will allow > only publicly readable files to be accessed." > > Are the files you're trying to serve world-readable? > Also, haa /etc/hosts.allow and /etc/host.deny been checked? -- Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
Re: The OACK Project
This rings a bell to me. I don't know if it still is true but "a while ago" tftpd was binding to the networkcard it found first. Try to run it on a machine that only has one networkcard and see if it works better. If you look at older postings you will probably find the exact problem. Howerver what you describe might be another problem, but I spent a log of time trying to get an old mac to boot via tftp and never succeded until I accidently hooked the client up on the other networkcard Jonathan Eifrig wrote: Rogier Krieger wrote: On 1/24/07, Jonathan Eifrig <[EMAIL PROTECTED]> wrote: tftpd[]: oack: Permission denied That may have something to do with *file* permissions. Quoting tftpd(8): "The use of tftp(1) does not require an account or password on the remote system. Due to the lack of authentication information, tftpd will allow only publicly readable files to be accessed." Are the files you're trying to serve world-readable? Yes. :-) As I said, the problem is client-specific: a tftp client running on the same machine as the server can retrieve files with no problem. Clients on remote machines timeout. It's as if the tftpd process is not allowed to use eth0 or some such.
Re: The OACK Project
Rogier Krieger wrote: On 1/24/07, Jonathan Eifrig <[EMAIL PROTECTED]> wrote: tftpd[]: oack: Permission denied That may have something to do with *file* permissions. Quoting tftpd(8): "The use of tftp(1) does not require an account or password on the remote system. Due to the lack of authentication information, tftpd will allow only publicly readable files to be accessed." Are the files you're trying to serve world-readable? Yes. :-) As I said, the problem is client-specific: a tftp client running on the same machine as the server can retrieve files with no problem. Clients on remote machines timeout. It's as if the tftpd process is not allowed to use eth0 or some such.
Re: The OACK Project
On Jan 24, 2007, at 6:18 AM, Jonathan Eifrig wrote: I'm trying to get a Soekris box to boot from an OpenBSD tftp server. I've gotten my DHCP server working, but I'm having trouble with my tftpd configuration. (I guess it's not so Trivial as I thought! :-)) When the client attempts to retrieve pxeboot from the tftp server, the client times out and on the server I get the following (unhelpful) message dumped to the syslog: tftpd[]: oack: Permission denied ... tftpd[]: nak: Permission denied This happens with any remote client. Interestingly, if I attempt to tftp from the server locally, it works fine: only remote clients have a problem. My tftp daemon is started from inetd (which I guess technically makes it not a daemon at all); I just uncommented the tftpd lines in the distributed inetd.conf file. Obviously, there's some sort of network permissions configuration layer I'm missing. Any ideas of where to look? What are the perms on /tftpboot/*? The tftpd daemon is privsep. The code snippets that generate those errors (src/libexec/tftpd/tftpd.c) would indeed suggest a network permissions problem as you mention, but it can't hurt to check. -- Jason Dixon DixonGroup Consulting http://www.dixongroup.net
Re: The OACK Project
On 1/24/07, Jonathan Eifrig <[EMAIL PROTECTED]> wrote: tftpd[]: oack: Permission denied That may have something to do with *file* permissions. Quoting tftpd(8): "The use of tftp(1) does not require an account or password on the remote system. Due to the lack of authentication information, tftpd will allow only publicly readable files to be accessed." Are the files you're trying to serve world-readable? Cheers, Rogier -- If you don't know where you're going, any road will get you there.
The OACK Project
I'm trying to get a Soekris box to boot from an OpenBSD tftp server. I've gotten my DHCP server working, but I'm having trouble with my tftpd configuration. (I guess it's not so Trivial as I thought! :-)) When the client attempts to retrieve pxeboot from the tftp server, the client times out and on the server I get the following (unhelpful) message dumped to the syslog: tftpd[]: oack: Permission denied ... tftpd[]: nak: Permission denied This happens with any remote client. Interestingly, if I attempt to tftp from the server locally, it works fine: only remote clients have a problem. My tftp daemon is started from inetd (which I guess technically makes it not a daemon at all); I just uncommented the tftpd lines in the distributed inetd.conf file. Obviously, there's some sort of network permissions configuration layer I'm missing. Any ideas of where to look?
