Messages

I have to apologize. I just switched line 51 to debug output and saw that there was a request on port 3024 ......

thanks

klaus

I've got a theoretical question. Would it be possible to change the the default ports of the communication between vomp and mvp ?

Background: after the bootp session the mvp sends out an udp-broadcast on 16882 - the server answers and tells his guiserver and mediaport data. If vomp could communicate on other ports, it would be possible to run a second mvp-server on the same machine (for example mvpmc) and switch to this server by providing another dongle.bin. the vomp-plugin itself could provide such a mechanism, so we could use the best of both servers - and you don't need to implement all this features.....

greetz

klaus

hi chris

indeed - radio would be great .... it's really so difficult??

greets

klaus

hi chris,
dongle 14 works fine in an enviroment with two servers running the plugin (both vdr 1.2.6). thanks for fixing that!

Other topic - investigation of next-server entry.
I've set up the dhcp server on a third machine (running ipcop) providing the following entry to dhcpd.conf:

allow booting;
allow bootp;

........
........

group {
next-server 192.168.3.201;
    host mvp
    {
        filename "dongle.bin";
        hardware ethernet 00:0d:fe:00:23:c1;
        fixed-address 192.168.3.79;
    }
}

192.168.3.201 is the vdr where tftpd  is runnig
192.168.3.79 the mvp


works fine....


thanx a lot for your work. Your solution (already at this early state) is much more reliable and stable then other solutions for vdr, although there are only basic functions. but sometimes less is more!!

klaus