Messages

[#my server is 10.222.11.4, my mvp should get 10.222.10.40#the next is the important line!option routers 10.222.11.4;ddns-update-style none;allow bootp;allow booting;default-lease-time 14400;subnet 10.222.11.0 netmask 255.255.255.0 { range 10.222.11.20 10.222.11.40; default-lease-time 14400; max-lease-time 172800;}group { next-server 10.222.11.4; host mvp { # NOTE: Change the hardware ethernet to the MAC address of your actual MVP hardware ethernet 00:0d:fe:00:78:e6; fixed-address 10.222.11.40; filename "dongle.bin.mvp"; }}]

Hi Dejuh,
I had similar problems on a Suse9.3 - shortly after starting with vomp (looks very nice...)
Finally I explored that it was really important to have the server machine being setup as router in the DHCP setting, here is my /etc/hdcpd.conf:
#my server is 10.222.11.4, my mvp should get 10.222.10.40
#the next is the important line!
option routers 10.222.11.4;
ddns-update-style none;
allow bootp;
allow booting;
default-lease-time 14400;
subnet 10.222.11.0 netmask 255.255.255.0 {
  range 10.222.11.20 10.222.11.40;
  default-lease-time 14400;
  max-lease-time 172800;
}
group {
  next-server 10.222.11.4;
  host mvp { # NOTE: Change the hardware ethernet to the MAC address of your actual MVP
    hardware ethernet 00:0d:fe:00:78:e6;
    fixed-address 10.222.11.40;
    filename "dongle.bin.mvp";
  }
}


--
you can check this when you login to the mvp with telnet:
telnet 10.222.10.40
root

ping 255.255.255.255
- should give a reply from your server
if you get network unreachable - you missed the router entry.
you can also try
route
if there is a default - OK, otherwise it will fail.

Maybe this helps...

--> Chris - would it be possible to add an error message to the socket send in the vompclient, this will ease searching for such problems (you should really get a socket error there...)

Regards
Andreas

Hi avvdr thank you,
i can ping :
~ # ping 255.255.255.255
PING 255.255.255.255 (255.255.255.255): 56 data bytes
64 bytes from 192.168.6.79: icmp_seq=0 ttl=255 time=0.4 ms
64 bytes from 192.168.6.79: icmp_seq=1 ttl=255 time=0.4 ms
64 bytes from 192.168.6.79: icmp_seq=2 ttl=255 time=0.4 ms
64 bytes from 192.168.6.79: icmp_seq=3 ttl=255 time=0.3 ms
64 bytes from 192.168.6.79: icmp_seq=4 ttl=255 time=0.3 ms
64 bytes from 192.168.6.79: icmp_seq=5 ttl=255 time=0.3 ms

--- 255.255.255.255 ping statistics ---
6 packets transmitted, 6 packets received, 0% packet loss
round-trip min/avg/max = 0.3/0.3/0.4 ms

Dejuh

Hi Dejuh,

I had similar problems, but the hint from avvdr did the job. 

I am using vdr on Suse 8.2 (never touch a running system) and I have a dhcp server
activated in my dsl router.
I started to use mvploader to boot the mvp, I got it up to "locating server", but I could not ping
the box.
Then I used bootp/tftp as described in the howto from the vdr portal. I discovered the same problems as you did.
I was able to ping the box and it was possible to connect to the mvp via telnet.

Than I deactivated bootp and activated dhcp on my vdr and configured it as described in the howto and it is working.
Both dhcp servers seems not to interfear with each other.

I hope this may also work for you.

THX to everybody , THX Chris for your fine peace of software and great support

KalleAnka

Hi Chris,

thank you for your support.

I looked a bit into the network traffic (packetyzer).

What I can see that the box get's a response to the first DHCP request, and I can see the
a lot of traffic during the firmware upload. During that time also ping
is possible.

Then the box is unreachable. The last messages it sends out are 6 DHCP requests, when linux in the
box has booted - right ?

So I guess my WLAN router (Siemens SE515)  might be the course of the problem, since the box does
not get a correct answer on the second request.

I also uploaded a mediamvp dongle. After this firmware has booted I see UDP packets looking for a server.
Strange, since I read in various forums only success stories.

What do you think ?
BR
KalleAnka

Hi all,

today I tried to set up vomp on my medimvp.

Compiling and starting the vompserver (0.0.1) into vdr was no problem,
I see the message that it is started and I see the entry in the plugin
setup dialog (even if there is no option to set).

--plugin="vompserver"    ...
Jan 16 23:22:54 vdr vdr[5974]: loading plugin: /usr/local/lib/vdr/libvdr-vompserver.so.1.3.37
Jan 16 23:22:58 vdr vdr[5974]: initializing plugin: vompserver (0.0.1): VDR on MVP plugin by Chris Tallon
Jan 16 23:22:59 vdr vdr[5974]: starting plugin: vompserver
vdr:/var/log #



Then I load the vomp dongle (0.1.1) into mediamvp, I see the printout from the mvploader.

#
vdr:/usr/local/etc/vdr/plugins # [bootp] packet from 192.168.13.9 : 16868 [300 bytes]
[tftp] request from 192.168.13.9 : 3909
Firmware load complete for 192.168.13.9


during that time I can ping the mediamvp

PING 192.168.13.9 (192.168.13.9) 56(84) bytes of data.
64 bytes from 192.168.13.9: icmp_seq=1 ttl=64 time=0.520 ms
64 bytes from 192.168.13.9: icmp_seq=2 ttl=64 time=0.361 ms
64 bytes from 192.168.13.9: icmp_seq=3 ttl=64 time=0.433 ms


But after the dongle upload is finished the ping gets no reply.

Then "Locating server" appears on the screen, but nothing happens.

ping is still not answered.

The mediamvp gets its ip address from a WLAN router running dhcp.
During the time when the mediamvp is  booting I can see the MAC address
in the routers ARP table. After that the entry is gone even though it is still
listed in the DHCP table.

vdr 1.3.37  is running on Suse 8.2 without any firewall.

Any hint to get rid of this problem is welcome.

Kind Regards
KalleAnka