[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
port-i386/54562: pxeboot NFS V2 READ Call into the void
>Synopsis: pxeboot NFS V2 READ Call into the void
>Arrival-Date: Sun Sep 22 17:45:00 +0000 2019
>Originator: pierre-philipp braun
This bug report is either about the NFS client built-into netbsd's pxeboot, or probably rather about its built-in DHCP client.
While trying to PXE boot netbsd-INSTALL.gz from a Lignux NFS server, and after facing, sniffing and solving unknown error codes 72 and 45, I finally end-up with a similar problem as in the pxeboot/TFTP client bug I just reported (54561). So after numerous tweaks on the server side, namely enabling NFS version 2 and adding no_subtree_check to exports, it looks like it could work.
The pxeboot built-in NFS client sends its `V2 LOOKUP Call` alright and the server answers with `V2 LOOKUP Reply`. Then comes two `V2 READ Call` requests and server answers back two `V2 READ Reply` in turns. However the third `V2 READ Call` sent by the client ends-up nowhere as the destination IP is 0.0.0.0.
It seems pxeboot lost track of its DHCP lease.
Setup a PXE service (DHCP+TFTP+pxeboot), here done on Slackware Linux 14.2. I did not try to reproduce it with NetBSD's NFS server.
option root-path "/tftpboot";
Then PXE boot from a client node, get to the netbsd boot loader prompt provided by pxeboot and enter one of those (NFS is the default)
Main Index |
Thread Index |