2009/12/6 Tom Metro
<[email protected]<tmetro%[email protected]>
>
> Dave wrote:
> > Tom Metro wrote:
> >> mvpmc includes a TFTP client, and will use the path supplied via
> >> DHCP when retrieving your optional startup script ("conf file").
> >
> > which path? This one?
> > option root-path "/home/me,rsize=4096,wsize=4096,nolock";
>
> Yes.
>
> I believe the boot firmware combines that path with the boot file name
> and makes a request for /home/me/mvp.bin, in your case.
>
> mvpmc in rcS gets this path as $DONGLE (from an upstream process, that
> gets it from mvpmc's DHCP client...or perhaps passed on by the boot
> firmware via a Flash location), and uses it as the basis of the file
> name for the "config file" request. So if the first includes a path, the
> second will also.
>
>
> > if so, then I need to change it back to
> > option root-path "/*tftpboot*,rsize=4096,wsize=4096,nolock";
>
> If your dongle is stored in /tftpboot on your server *and* your TFTP
> server isn't configured to ignore paths, then yes, correcting that path
> to match is necessary.
>
> Telling the server to ignore paths is the safest and simplest thing to do.
>
>
> > OK, here's the test I just ran from my laptop:
> >
> > > tftp
> > tftp> connect 192.168.2.107
> > tftp> get mvp.bin
> > tftp>
> >
> > The file was retrieved:
> > -rw-r--r-- 1 me users 3625504 2009-12-06 16:51 mvp.bin
> >
> > and the server logs show this:
> > Dec 6 16:51:33 myMythBE atftpd[2182]: Serving mvp.bin to
> > 192.168.2.114:44005 <http://192.168.2.114:44005>
> >
> > That would seem to indicate nothing unexpected with regard to the path.
>
> But your request didn't include a path. That's what you need to
> test...or alternatively, eliminate the path from your DHCP options so it
> matches your test.
>
> In any case, if it was just a file not found failure, you'd see that in
> the logs. (At least if you were running the BSD TFTP server; the logging
> from atftp is a bit sketchy, and I don't recommend it).
>
> -Tom
>
>
Thanks for your explanations. I just did some more testing. I have learned a
lot, but still no solution. With this MVP there is nothing in the tftp logs.
Originally, even before I got it to boot mvpmc, I could see, via the logs,
it was looking for mvp.bin. The rev H unit shows up in the tftp logs, as you
would expect.
After repeating all the test steps carefully, it looks like the problem is
dhcp related. Here's the logs:
Dec 6 21:47:00 myMythBE dhcpd: DHCPDISCOVER from 00:0d:fe:00:xx:xx via
eth0
Dec 6 21:47:00 myMythBE dhcpd: DHCPOFFER on 192.168.2.203 to
00:0d:fe:00:xx:xx via
eth0
Dec 6 21:47:18 myMythBE dhcpd: DHCPDISCOVER from 00:0d:fe:00:xx:xx via
eth0
Dec 6 21:47:18 myMythBE dhcpd: DHCPOFFER on 192.168.2.203 to
00:0d:fe:00:xx:xx via
eth0
Dec 6 21:47:37 myMythBE dhcpd: DHCPDISCOVER from 00:0d:fe:00:xx:xx via
eth0
Dec 6 21:47:37 myMythBE dhcpd: DHCPOFFER on 192.168.2.203 to
00:0d:fe:00:xx:xx via
eth0
Dec 6 21:48:06 myMythBE dhcpd: DHCPDISCOVER from 00:0d:fe:00:xx:xx via
eth0
Dec 6 21:48:06 myMythBE dhcpd: DHCPOFFER on 192.168.2.203 to
00:0d:fe:00:xx:xx via
eth0
Dec 6 21:48:37 myMythBE dhcpd: DHCPDISCOVER from 00:0d:fe:00:xx:xx via
eth0
Dec 6 21:48:37 myMythBE dhcpd: DHCPOFFER on 192.168.2.203 to
00:0d:fe:00:xx:xx via
eth0
Left device unplugged > dhcp max lease time and tried again
Dec 6 22:02:09 myMythBE dhcpd: DHCPDISCOVER from 00:0d:fe:00:xx:xx via
eth0
Dec 6 22:02:10 myMythBE dhcpd: DHCPOFFER on 192.168.2.203 to
00:0d:fe:00:xx:xx via
eth0
Dec 6 22:02:28 myMythBE dhcpd: DHCPDISCOVER from 00:0d:fe:00:xx:xx via
eth0
Dec 6 22:02:28 myMythBE dhcpd: DHCPOFFER on 192.168.2.203 to
00:0d:fe:00:xx:xx via
eth0
Dec 6 22:02:46 myMythBE dhcpd: DHCPDISCOVER from 00:0d:fe:00:xx:xx via
eth0
Dec 6 22:02:46 myMythBE dhcpd: DHCPOFFER on 192.168.2.203 to
00:0d:fe:00:xx:xx via
eth0
Dec 6 22:03:15 myMythBE dhcpd: DHCPDISCOVER from 00:0d:fe:00:xx:xx via
eth0
Dec 6 22:03:15 myMythBE dhcpd: DHCPOFFER on 192.168.2.203 to
00:0d:fe:00:xx:xx via
eth0
Dec 6 22:03:46 myMythBE dhcpd: DHCPDISCOVER from 00:0d:fe:00:xx:xx via
eth0
Dec 6 22:03:46 myMythBE dhcpd: DHCPOFFER on 192.168.2.203 to
00:0d:fe:00:xx:xx via
eth0
Dec 6 22:04:07 myMythBE dhcpd: DHCPDISCOVER from 00:0d:fe:00:xx:xx via
eth0
Dec 6 22:04:07 myMythBE dhcpd: DHCPOFFER on 192.168.2.203 to
00:0d:fe:00:xx:xx via eth0
------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Mvpmc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mvpmc-users
mvpmc wiki: http://mvpmc.wikispaces.com/
