Date: Wed, 11 Jun 2014 17:28:10 -0400 (EDT) From: Rick Macklem <rmacklem@uoguelph.ca> To: Craig Rodrigues <rodrigc@FreeBSD.org> Cc: freebsd-current Current <freebsd-current@freebsd.org>, Beeblebrox <zaphod@berentweb.com> Subject: Re: Previously working PXE setup now fails Message-ID: <115336188.14750168.1402522090584.JavaMail.root@uoguelph.ca> In-Reply-To: <CAG=rPVciV=S8cJ67mF1qbG1yMJH_JnTCxyfSWEL-0YN2DGPTiQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Craig Rodrigues wrote: > On Tue, Jun 10, 2014 at 7:31 AM, Beeblebrox <zaphod@berentweb.com> > wrote: > > > > Then BTX starts to boot the kernel but fails with: > > pxe_open: server addr: 192.168.2.1 > > pxe_open: server path: / > > pxe_open: gateway ip: 192.168.2.1 > > NFS MOUNT RPC error: 72 > > In /usr/include/errno.h, error 72 is: > #define EBADRPC 72 /* RPC struct is bad */ > > > Take a look at > http://www.freebsd.org/doc/handbook/network-pxe-nfs.html > and see if you can run wireshark on your NFS server that is > being mounted. That should narrow down the RPC error. > Btw, if it more convenient, you can capture the packets with tcpdump (use -s 0 -w <file>.pcap ...) and then look at <file>.pcap via wireshark on any machine it's convenient to install it on. Although wireshark is pretty good at NFS messages, you can email me <file>.pcap and I'll take a look at it. I am not aware of any bugs in current that cause the RPC messages to be corrupted. Good luck with it, rick > -- > Craig > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?115336188.14750168.1402522090584.JavaMail.root>