snow_freak wrote: > Unfortunately i have no chance to test with another machine.
It that due to the topology of your network or for lack of another machine? > As hopkin mentioned i tried to run mvprelay with IP address of the tftp > server. > # mvprelay 16881 5906 6337 192.168.1.2 > Now the MVP is trying to get the dongle.bin... ... > When i try the same with mvpboot there are not tftp messages in the syslog. Interesting. Were you running mvpboot when you captured the traffic you posted previously? It seemed like the IP address it handed out was correct (as evidenced by the MVP ARP request for your server's IP address). The corresponding syslog logs should also show whether the correct address was handed out by mvpboot. Do you have multiple Ethernet interfaces in use? mvpboot should have automatically determined your server's address using Net::Interface. After you get your MVP booting, perhaps we should come back to this and figure out why it didn't work. > ...but there are timeouts. > atftpd[7795]: Advanced Trivial FTP server started (0.7) > atftpd[7795]: Serving dongle.bin.ver to 192.168.1.3:2049 > atftpd[7795]: Serving dongle.bin to 192.168.1.3:2050 > atftpd[7795]: timeout: retrying... > atftpd[7795]: timeout: retrying... > atftpd[7795]: Serving dongle.bin to 192.168.1.3:2051 > atftpd[7795]: timeout: retrying... > last message repeated 2 times > atftpd[7795]: Serving dongle.bin to 192.168.1.3:2052 > atftpd[7795]: timeout: retrying... > > The MVP screen shows 'Loading Application'. I've seen the same timeouts and posted about them before, but in my case the boot succeeds. I don't know why they are occurring, and I've toyed around with the various timeout settings. Here's an example from my logs when I was using atftpd: atftpd[2587]: Serving dongle.bin to 192.168.0.242:2049 atftpd[2587]: timeout: retrying... last message repeated 6 times atftpd[2587]: recvmsg: Connection refused atftpd[2587]: tftpd_file.c: 926: recvfrom: Connection refused And after switching to BSD tftpd: tftpd[19396]: tftpd: read: Connection refused tftpd[19398]: tftpd: read: Connection refused So something is misbehaving. Probably the TFTP client in the Hauppauge firmware. I don't always see the errors, but they don't seem to interfere with the booting process. At this point it sounds like you have all the prerequisites for booting working correctly. I'm not sure what to suggest next, other than to try a different dongle, and as a longer shot, try the BSD TFTP server. hopkin wrote: > Odd that dongle.bin.ver now seems to work and dongle.bin fails. The larger file provides more opportunity for timeouts. > Check the file permissions for both files are the same in /tftpboot. Worth checking, but I don't think you'd get to the timeout error if the TFTP server couldn't access the requested file. -Tom ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Mvpmc-users mailing list Mvpmc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mvpmc-users mvpmc wiki: http://mvpmc.wikispaces.com/
