fldavem writes: > The issue is with a D3A model, which is not flash based.
Ah, OK. I'm not personally familiar with the setup of the older hardware, so I'll reiterate the recommendation of posting follow-up questions to the mailing list where hopefully others will be able to fill in the gaps. > I followed the guide...at: > http://www.mvpmc.org/mvpmc-HOWTO-singlehtml.html Many of the steps in that guide have since been simplified in newer guides on the wiki, though the procedures it specifies may indeed be required for the older hardware. > ...I was trying to say that my DLink router provides the > connected device...with address. And now I set up my linux > machine to be a dhtp server - is that a conflict? Yes, this is potentially a conflict. (Also, the term is DHCP.) DHCP works by having the client broadcast a request for an address (DHCPDISCOVER) over your LAN. Unless your DHCP servers are specially configured to ignore requests from certain MAC addresses (or other characteristics), they will *all* try and respond to that request, which leads to problems. > My log file...does show that the mvp is connecting by these log > entries: > dave-desktop dhcpd: DHCPDISCOVER from 00:0d:fe:00:2a:4f > via eth0 > dave-desktop dhcpd: DHCPOFFER on 192.168.0.200 > to 00:0d:fe:00:2a:4f via eth0 Yes, but you don't necessarily know whether the MVP successfully accepted the DHCPOFFER from dhcpd or if it accepted it from the D-Link. > Do I need 2 instances of the atftpd running (one > for 69 and one for 1689)? I believe the answer to that is hardware dependent. With the latest models, port 16869 (note the difference from what you wrote) is used to load the firmware, and 69 is used to load the config. I think with the older hardware only one of those is used - I believe just 69. If the HOWTO you cited is correct for your hardware, it seems to require only a TFTP server running on the standard port, so that's all you should need. Similarly, the mvpboot server I mentioned in my prior message isn't required for your hardware according to that document. > And should those be configured on my DLink router? No...I don't think there is a way that you could do that, even if you wanted to. > If so, should I pass those to the .100 linux machine with mvpmc > or to the Media MVP (.200)? I'm not following your question. Those ports are specified in the /etc/inetd.conf file of the machine where you are running your TFTP server. They tell the super server, inetd, which ports to listen on when providing the TFTP service. (inetd listens on specified ports and starts up other servers, like tftpd, to process the requests.) > Thanks for pointing me to this users mailing list! You're welcome. Please post follow-ups there, if you can. -Tom ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Mvpmc-users mailing list Mvpmc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mvpmc-users mvpmc wiki: http://mvpmc.wikispaces.com/
