mpvserver und suse 10.0

[dejuh]

Hi,
but

server:/ # lsof -P | grep UDP
portmap   5045     nobody    3u     IPv4              11530                 UDP *:111
nmbd      5320       root    6u     IPv4              12112                 UDP *:137
nmbd      5320       root    7u     IPv4              12113                 UDP *:138
nmbd      5320       root    8u     IPv4              12115                 UDP server.domain.de:137
nmbd      5320       root    9u     IPv4              12116                 UDP server.domain.de:138
dhcpd     5351      dhcpd    6u     IPv4              12211                 UDP *:67
rpc.mount 5530       root    6u     IPv4              12850                 UDP *:608
xdm       5917       root    5u     IPv6              14274                 UDP *:177
xinetd    5919       root    5u     IPv4              14468                 UDP *:69
miniserv. 5924       root    5u     IPv4              14264                 UDP *:10000
ypserv    5970       root    4u     IPv4              14452                 UDP *:634
rpc.ypxfr 5992       root    3u     IPv4              14498                 UDP *:656
rpc.yppas 5995       root    4u     IPv4              14513                 UDP *:659
in.tftpd  7579       root    0u     IPv4              14468                 UDP *:69
vdr       7688       root    4u     IPv4              28693                 UDP *:3024
vdr       7688       root   18u     IPv4              28699                 UDP *:16881

but Locating Server 

[Chris]

Oh.

So which client and server versions are you using now?

And you can definitely ping the client when it says "Locating server"?

[dejuh]

Hi,
vompserver-0.1.0 and  vomp-dongle-0.1.1
yes i can ping!!!!
Dejuh

[Chris]

In that case, I think I'm stuck.

[dejuh]

 

[Chris]

At the locating server stage the MVP sends 1 packet per second to the broadcast address of 255.255.255.255 on port 3024. The vompserver plugin responds and the two find each other. Pinging the MVP proves that it has the right IP address and is on the network - so it's not that. Your "ps" outputs prove that the vdr process has opened port 3024 on the server. You have said there is no firewall, so it can't be that. Maybe you could run an IP traffic monitoring program on the vdr server to see if the broadcast packets from the MVP are making it to the VDR box? I find "tcpdump ether host xx:xx:xx:xx:xx:xx" (inserting the MAC of the MVP) to be quite useful. Do that on the VDR box though to prove that the packets are making it to there.

[dejuh]

Hi Chris,
to compilieren the vompserver-plugin:

make[1]: Entering directory `/usr/local/src/vdr-1.3.36/PLUGINS/src/vompserver'
g++ -fPIC -O2 -Wall -Woverloaded-virtual -Werror -c -DPLUGIN_NAME_I18N='"vompserver"' -I../../../include -I../DVB/include -Iremux -Ilibdvbmpeg -o vompserver.o vompserver.c
g++ -fPIC -O2 -Wall -Woverloaded-virtual -Werror -c -DPLUGIN_NAME_I18N='"vompserver"' -I../../../include -I../DVB/include -Iremux -Ilibdvbmpeg -o dsock.o dsock.c
g++ -fPIC -O2 -Wall -Woverloaded-virtual -Werror -c -DPLUGIN_NAME_I18N='"vompserver"' -I../../../include -I../DVB/include -Iremux -Ilibdvbmpeg -o mvpserver.o mvpserver.c
g++ -fPIC -O2 -Wall -Woverloaded-virtual -Werror -c -DPLUGIN_NAME_I18N='"vompserver"' -I../../../include -I../DVB/include -Iremux -Ilibdvbmpeg -o udpreplier.o udpreplier.c
g++ -fPIC -O2 -Wall -Woverloaded-virtual -Werror -c -DPLUGIN_NAME_I18N='"vompserver"' -I../../../include -I../DVB/include -Iremux -Ilibdvbmpeg -o mvpclient.o mvpclient.c
g++ -fPIC -O2 -Wall -Woverloaded-virtual -Werror -c -DPLUGIN_NAME_I18N='"vompserver"' -I../../../include -I../DVB/include -Iremux -Ilibdvbmpeg -o tcp.o tcp.c
g++ -fPIC -O2 -Wall -Woverloaded-virtual -Werror -c -DPLUGIN_NAME_I18N='"vompserver"' -I../../../include -I../DVB/include -Iremux -Ilibdvbmpeg -o remux/ts2ps.o remux/ts2ps.c
g++ -fPIC -O2 -Wall -Woverloaded-virtual -Werror -c -DPLUGIN_NAME_I18N='"vompserver"' -I../../../include -I../DVB/include -Iremux -Ilibdvbmpeg -o remux/ts2es.o remux/ts2es.c
g++ -fPIC -O2 -Wall -Woverloaded-virtual -Werror -c -DPLUGIN_NAME_I18N='"vompserver"' -I../../../include -I../DVB/include -Iremux -Ilibdvbmpeg -o remux/tsremux.o remux/tsremux.c
g++ -fPIC -O2 -Wall -Woverloaded-virtual -Werror -c -DPLUGIN_NAME_I18N='"vompserver"' -I../../../include -I../DVB/include -Iremux -Ilibdvbmpeg -o ringbuffer.o ringbuffer.c
g++ -fPIC -O2 -Wall -Woverloaded-virtual -Werror -c -DPLUGIN_NAME_I18N='"vompserver"' -I../../../include -I../DVB/include -Iremux -Ilibdvbmpeg -o recplayer.o recplayer.c
g++ -fPIC -O2 -Wall -Woverloaded-virtual -Werror -c -DPLUGIN_NAME_I18N='"vompserver"' -I../../../include -I../DVB/include -Iremux -Ilibdvbmpeg -o config.o config.c
g++ -fPIC -O2 -Wall -Woverloaded-virtual -Werror -c -DPLUGIN_NAME_I18N='"vompserver"' -I../../../include -I../DVB/include -Iremux -Ilibdvbmpeg -o log.o log.c
g++ -fPIC -O2 -Wall -Woverloaded-virtual -Werror -c -DPLUGIN_NAME_I18N='"vompserver"' -I../../../include -I../DVB/include -Iremux -Ilibdvbmpeg -o thread.o thread.c
g++ -fPIC -O2 -Wall -Woverloaded-virtual -Werror -c -DPLUGIN_NAME_I18N='"vompserver"' -I../../../include -I../DVB/include -Iremux -Ilibdvbmpeg -o mvpreceiver.o mvpreceiver.c
make -C ./libdvbmpeg libdvbmpegtools.a
make[2]: Entering directory `/usr/local/src/vdr-1.3.36/PLUGINS/src/vompserver/libdvbmpeg'
g++  -M ctools.c remux.c ringbuffy.c transform.c cpptools.cc   -I.> .depend
make[2]: Leaving directory `/usr/local/src/vdr-1.3.36/PLUGINS/src/vompserver/libdvbmpeg'
make[2]: Entering directory `/usr/local/src/vdr-1.3.36/PLUGINS/src/vompserver/libdvbmpeg'
cc -c -fPIC -g -Wall -O2 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -I.  ctools.c
ctools.c: In function âwrite_mpgâ:
ctools.c:2028: warning: pointer targets in assignment differ in signedness
ctools.c: In function âurl2hostâ:
ctools.c:2253: warning: pointer targets in passing argument 1 of âstrlenâ differ in signedness
ctools.c:2253: warning: pointer targets in passing argument 1 of âstrlenâ differ in signedness
ctools.c:2253: warning: pointer targets in passing argument 1 of â__builtin_strcmpâ differ in signedness
ctools.c:2253: warning: pointer targets in passing argument 1 of âstrlenâ differ in signedness
ctools.c:2253: warning: pointer targets in passing argument 1 of â__builtin_strcmpâ differ in signedness
ctools.c:2253: warning: pointer targets in passing argument 1 of â__builtin_strcmpâ differ in signedness
ctools.c:2253: warning: pointer targets in passing argument 1 of â__builtin_strcmpâ differ in signedness
ctools.c:2253: warning: pointer targets in passing argument 1 of âstrncmpâ differ in signedness
ctools.c:2256: warning: pointer targets in passing argument 1 of âstrlenâ differ in signedness
ctools.c:2256: warning: pointer targets in passing argument 1 of â__strdupâ differ in signedness
ctools.c:2282: warning: pointer targets in return differ in signedness
ctools.c:2284: warning: pointer targets in passing argument 1 of âatoiâ differ in signedness
ctools.c:2288: warning: pointer targets in return differ in signedness
ctools.c: In function âhttp_openâ:
ctools.c:2309: warning: pointer targets in passing argument 1 of âurl2hostâ differ in signedness
ctools.c:2341: warning: pointer targets in passing argument 2 of âwrite_allâ differ in signedness
ctools.c:2348: warning: pointer targets in passing argument 2 of âread_allâ differ in signedness
ctools.c:2362: warning: pointer targets in passing argument 2 of âread_allâ differ in signedness
cc -c -fPIC -g -Wall -O2 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -I.  ringbuffy.c
ringbuffy.c: In function âring_writeâ:
ringbuffy.c:62: warning: implicit declaration of function âmemcpyâ
ringbuffy.c:62: warning: incompatible implicit declaration of built-in function âmemcpyâ
ringbuffy.c:67: warning: incompatible implicit declaration of built-in function âmemcpyâ
ringbuffy.c: In function âring_peekâ:
ringbuffy.c:92: warning: incompatible implicit declaration of built-in function âmemcpyâ
ringbuffy.c:94: warning: incompatible implicit declaration of built-in function âmemcpyâ
ringbuffy.c: In function âring_readâ:
ringbuffy.c:117: warning: incompatible implicit declaration of built-in function âmemcpyâ
ringbuffy.c:120: warning: incompatible implicit declaration of built-in function âmemcpyâ
cc -c -fPIC -g -Wall -O2 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -I.  remux.c
cc -c -fPIC -g -Wall -O2 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -I.  transform.c
g++ -c -fPIC -g -Wall -O2 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -I.  cpptools.cc
ar -rcs libdvbmpegtools.a ctools.o ringbuffy.o remux.o transform.o cpptools.o
make[2]: Leaving directory `/usr/local/src/vdr-1.3.36/PLUGINS/src/vompserver/libdvbmpeg'
g++ -fPIC -O2 -Wall -Woverloaded-virtual -Werror -shared vompserver.o dsock.o mvpserver.o udpreplier.o mvpclient.o tcp.o remux/ts2ps.o remux/ts2es.o remux/tsremux.o ringbuffer.o recplayer.o config.o log.o thread.o mvpreceiver.o libdvbmpeg/libdvbmpegtools.a -o libvdr-vompserver.so
make[1]: Leaving directory `/usr/local/src/vdr-1.3.36/PLUGINS/src/vompserver'

Dejuh

[Chris]

Hi, that's ok and nothing to do with it. I also get those warnings on newer compilers. They are all in libdvbmpeg which is not my stuff. I will investigate it one day.

[Nobiman]

Hi Dejuh,

in my opinion this problem is a firewall problem. You are really sure that the
SuSE-Firewall is NOT running? As I know the Suse-firewall blocks incoming
Broadcasts for default, so the vomp-plugin would never receive the initial paket from
the media-mvp. (I'm not really sure, cause I don't use the SuSEFW on my vdr)
Try a "/sbin/SuSEfirewall2 stop" before starting the media-mvp!

it might be usefull for you to read the same text in german, but please don't switch
this thread to german, because Chris won't understand us, send me a pn instead.
----------------------------------
nach meiner Ansicht liegt das Problem an der SuSE-Firewall. Bist Du ganz sicher, dass
die SuseFirewall abgeschaltet ist? Soweit ich weiss werden in der SusEFW per default
eingehende Broadcasts geblockt, dann wird das vomp-plugin niemals was vom media.-mvp
mitbekommen! (Bin mir aber nicht sicher, da ich die SuSEFW auf meinem vdr nicht nutze)
Versuch mal als "root"  "/sbin/SuSEfirewall2 stop" einzugeben bevor Du das MVP startest !

Weitere "Deutsche" Fragen bitte per pn
----------------------------------
cu
Nobi

[avvdr]

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

[frithjof]

Hi,
vompserver-0.1.0 and  vomp-dongle-0.1.1  ?
yes i can ping!!!!
Dejuh

please use vompserver-0.1.0 and  vomp-dongle-0.1.0

that works on my suse 10.0

also the current cvs versions of server and dongle work fine, watched saturday and sunday
the whole evening without any crashes (live and recordings)

used mvploader in the tftpboot dir to load the dongle, DHCP is on the DSL router

Frithjof

[dejuh]

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

[KalleAnka]

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

[Chris]

Dejuh: do you have this working now? If not there are now in-built bootp/tftp servers in the vompserver plugin which might change the situation.

[dejuh]

Hi Chris,
with the new plugin wors my Mediamvp perfect..........
It is wunderfull Thank You
Dejuh