[mythtv-users] OT slightly - MediaMVP won't boot

Paul Fine pfine at comcast.net
Sat May 13 09:08:48 EDT 2006


Brian Wood wrote:
> On May 12, 2006, at 9:02 AM, Paul Fine wrote:
>
>   
>> I also posted this question on the mvpmc forums, but I know that there
>> are a few MediaMVP users watching this list, so I thought I might also
>> try here for some advice.
>>
>> I am trying to setup a MediaMVP that I picked up on clearance from
>> RadioShack. It is a Model 86001 Rev D3A.
>>
>> I have a DHCP server running on my Fedora Core 4 Mythtv backend and  
>> the
>> TFTP-server is running. I confirmed that both the DHCP server and the
>> TFTP server are working by getting a lease from a PC, and using  
>> that PC
>> to extract the dongle.bin.mvpmc file from the server via TFTP.
>>
>> When I power up the MediaMVP, I see the DHCPDISCOVER and DHCPOFFER
>> messages (using tcpdump), and then I see an RRQ message from the
>> MediaMVP requesting the dongle.bin.mvpmc file.
>>
>> What I do not see is any acknowledgement of data received by the
>> MediaMVP after this point. My server keeps sending 516 byte packets
>> while getting no response. At some point, the DHCPDISCOVER and  
>> DHCPOFFER
>> messages come across again.  I am at work right now, so I can't  
>> post the
>> logs and tcpdump output.
>>
>> Any ideas/suggestions?
>>     
>
> Not right off-hand, sure sounds like you're doing everything right.
>
> Since it's short, here's my dhcpd.conf file, it's working fine for me:
>
> ddns-update-style interim;
>
> allow bootp;
> allow booting;
>
> subnet 192.168.0.0  netmask 255.255.255.0 {
>
> }
>
> group {
>    next-server 192.168.0.10; # IP of TFTP server
>
>    host mvp { # NOTE: Change the hardware ethernet to the MAC address  
> of your actual MVP
>             hardware ethernet 00:0d:fe:00:7e:9a;
>             fixed-address 192.168.0.50;
>             filename "dongle.bin.mvpmc";
>      }
>
> }
>
> As you say, posting more info may help.
>
>   
Well, I have done a few more experiments.

My mythbackend computer is 192.168.2.200 and the dhcpd.conf and 
/etc/xinetd.d/tftp files look like :

#
# DHCP Server Configuration file.
#   see /usr/share/doc/dhcp*/dhcpd.conf.sample 
#
ddns-update-style interim;

#option domain-name "local";
#option subnet-mask 255.255.255.0;
#option domain-name-servers 192.168.2.1;

allow bootp;
allow booting;

subnet 192.168.2.0 netmask 255.255.255.0 {
#  option routers      192.168.2.1;
#  range 192.168.2.100 192.168.2.199;
}

group {
  next-server 192.168.2.200;            # IP address of TFTP server

  host mvp {
           hardware ethernet 00:0d:fe:00:92:ef;
           fixed-address 192.168.2.57;
           filename "/dongle.bin.mvpmc";
 #          option root-path "/home/mvp,rsize=4096,wsize=4096,nolock";
  }

}


# default: off
# description: The tftp server serves files using the trivial file 
transfer \
#    protocol.  The tftp protocol is often used to boot diskless \
#    workstations, download configuration files to network-aware printers, \
#    and to start the installation process for some operating systems.
service tftp
{
    disable    = no
    socket_type        = dgram
    protocol        = udp
    wait            = yes
    user            = root
    server            = /usr/sbin/in.tftpd
    server_args        = -s /tftpboot
    per_source        = 11
    cps            = 100 2
    flags            = IPv4
}



 From the tcpdump, my friend noted that dhcpserver seems to be sending 
the dongle.bin.mvpmc file, but the mediamvp is not send ACKing it.

I also tried using tftpd32.exe as a tftp server running under WinXP.  
That TFTP server explicitly told me that the server was timing out 
because 192.168.2.57 was not ACKing Block #1.

I ran tcpdump like :

   # tcpdump not host 192.168.2.202 -v -c 200 >& tcpdump.txt

I excluded 192.168.2.202 because that is my laptop which I am using to 
ssh into my mythbackend computer. 

The first few lines of the resulting tcpdump.txt file are :

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
08:59:52.327331 arp who-has 192.168.2.100 tell .
08:59:52.328001 IP 192.168.2.200.51816 > ..domain:  25945+ PTR? 
100.2.168.192.in-addr.arpa. (44)
08:59:52.553265 IP ..domain > 192.168.2.200.51816:  25945 NXDomain 0/0/0 
(44)
08:59:52.553510 IP 192.168.2.200.51816 > ..domain:  25161+ PTR? 
1.2.168.192.in-addr.arpa. (42)
08:59:52.564902 IP ..domain > 192.168.2.200.51816:  25161*- 1/0/0 
PTR[|domain]
08:59:52.565062 IP 192.168.2.200.51816 > ..domain:  6928+ PTR? 
200.2.168.192.in-addr.arpa. (44)
08:59:52.603355 IP ..domain > 192.168.2.200.51816:  6928 NXDomain 0/0/0 (44)
08:59:53.508142 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, 
Request from 00:0d:fe:00:92:ef, length: 548
08:59:53.508348 IP 192.168.2.200.51816 > ..domain:  38537+ PTR? 
255.255.255.255.in-addr.arpa. (46)
08:59:53.508562 IP 192.168.2.200.bootps > 192.168.2.57.bootpc: 
BOOTP/DHCP, Reply, length: 300
08:59:53.638352 arp who-has 192.168.2.200 tell 192.168.2.57
08:59:53.638381 arp reply 192.168.2.200 is-at 00:15:f2:c1:6e:15
08:59:53.639095 IP 192.168.2.57.3909 > 192.168.2.200.tftp:  26 RRQ 
"/dongle.bin.mvpmc" octet
08:59:53.639830 IP 192.168.2.200.51818 > 192.168.2.57.3909: UDP, length 516
08:59:53.662157 IP ..domain > 192.168.2.200.51816:  38537 NXDomain 0/1/0 
(110)
08:59:53.662306 IP 192.168.2.200.51819 > ..domain:  45118+ PTR? 
0.0.0.0.in-addr.arpa. (38)
08:59:53.666928 IP 192.168.2.57.bootpc > 192.168.2.200.bootps: 
BOOTP/DHCP, Request from 00:0d:fe:00:92:ef, length: 548
08:59:53.667132 IP 192.168.2.200.bootps > 192.168.2.57.bootpc: 
BOOTP/DHCP, Reply, length: 300
08:59:53.690570 IP ..domain > 192.168.2.200.51819:  45118 NXDomain 0/1/0 
(102)
08:59:53.690837 IP 192.168.2.200.51819 > ..domain:  40823+ PTR? 
57.2.168.192.in-addr.arpa. (43)
08:59:53.709000 IP ..domain > 192.168.2.200.51819:  40823 NXDomain 0/0/0 
(43)
08:59:53.795396 IP 192.168.2.57.3909 > 192.168.2.200.tftp:  26 RRQ 
"/dongle.bin.mvpmc" octet
08:59:53.796134 IP 192.168.2.200.51819 > 192.168.2.57.3909: UDP, length 516
08:59:53.822620 IP 192.168.2.57.bootpc > 192.168.2.200.bootps: 
BOOTP/DHCP, Request from 00:0d:fe:00:92:ef, length: 548
08:59:53.822870 IP 192.168.2.200.bootps > 192.168.2.57.bootpc: 
BOOTP/DHCP, Reply, length: 300
08:59:53.951059 IP 192.168.2.57.3909 > 192.168.2.200.tftp:  26 RRQ 
"/dongle.bin.mvpmc" octet
08:59:53.951800 IP 192.168.2.200.51820 > 192.168.2.57.3909: UDP, length 516
08:59:53.978091 IP 192.168.2.57.bootpc > 192.168.2.200.bootps: 
BOOTP/DHCP, Request from 00:0d:fe:00:92:ef, length: 548
08:59:53.978341 IP 192.168.2.200.bootps > 192.168.2.57.bootpc: 
BOOTP/DHCP, Reply, length: 300
08:59:54.106868 IP 192.168.2.57.3909 > 192.168.2.200.tftp:  26 RRQ 
"/dongle.bin.mvpmc" octet
08:59:54.107655 IP 192.168.2.200.51821 > 192.168.2.57.3909: UDP, length 516
08:59:54.134093 IP 192.168.2.57.bootpc > 192.168.2.200.bootps: 
BOOTP/DHCP, Request from 00:0d:fe:00:92:ef, length: 548
08:59:54.134310 IP 192.168.2.200.bootps > 192.168.2.57.bootpc: 
BOOTP/DHCP, Reply, length: 300
08:59:54.262500 IP 192.168.2.57.3909 > 192.168.2.200.tftp:  26 RRQ 
"/dongle.bin.mvpmc" octet
08:59:54.263236 IP 192.168.2.200.51822 > 192.168.2.57.3909: UDP, length 516
08:59:54.289707 IP 192.168.2.57.bootpc > 192.168.2.200.bootps: 
BOOTP/DHCP, Request from 00:0d:fe:00:92:ef, length: 548
08:59:54.289925 IP 192.168.2.200.bootps > 192.168.2.57.bootpc: 
BOOTP/DHCP, Reply, length: 300
08:59:54.418144 IP 192.168.2.57.3909 > 192.168.2.200.tftp:  26 RRQ 
"/dongle.bin.mvpmc" octet
08:59:54.418884 IP 192.168.2.200.51824 > 192.168.2.57.3909: UDP, length 516
08:59:54.445172 IP 192.168.2.57.bootpc > 192.168.2.200.bootps: 
BOOTP/DHCP, Request from 00:0d:fe:00:92:ef, length: 548
08:59:54.445427 IP 192.168.2.200.bootps > 192.168.2.57.bootpc: 
BOOTP/DHCP, Reply, length: 300
08:59:54.573946 IP 192.168.2.57.3909 > 192.168.2.200.tftp:  26 RRQ 
"/dongle.bin.mvpmc" octet
08:59:54.574683 IP 192.168.2.200.51825 > 192.168.2.57.3909: UDP, length 516
08:59:54.601149 IP 192.168.2.57.bootpc > 192.168.2.200.bootps: 
BOOTP/DHCP, Request from 00:0d:fe:00:92:ef, length: 548
08:59:54.601406 IP 192.168.2.200.bootps > 192.168.2.57.bootpc: 
BOOTP/DHCP, Reply, length: 300
08:59:54.637550 IP 192.168.2.200.51818 > 192.168.2.57.3909: UDP, length 516
08:59:54.729906 IP 192.168.2.57.3909 > 192.168.2.200.tftp:  26 RRQ 
"/dongle.bin.mvpmc" octet
08:59:54.730788 IP 192.168.2.200.51826 > 192.168.2.57.3909: UDP, length 516
08:59:54.756816 IP 192.168.2.57.bootpc > 192.168.2.200.bootps: 
BOOTP/DHCP, Request from 00:0d:fe:00:92:ef, length: 548
08:59:54.757046 IP 192.168.2.200.bootps > 192.168.2.57.bootpc: 
BOOTP/DHCP, Reply, length: 300
08:59:54.793566 IP 192.168.2.200.51819 > 192.168.2.57.3909: UDP, length 516
08:59:54.886072 IP 192.168.2.57.3909 > 192.168.2.200.tftp:  26 RRQ 
"/dongle.bin.mvpmc" octet
08:59:54.886815 IP 192.168.2.200.51827 > 192.168.2.57.3909: UDP, length 516
08:59:54.912812 IP 192.168.2.57.bootpc > 192.168.2.200.bootps: 
BOOTP/DHCP, Request from 00:0d:fe:00:92:ef, length: 548






More information about the mythtv-users mailing list