Thanks for the hint, but I already searched this locations but I didn't find anything useful.
I found something in log files that looks pretty good to find the right thing to change.
/var/log/pluto/33_VDR.log:
== ATTEMPT FRESH START ==
1 01/29/10 18:14:32 Spawn_Device.sh 33 (spawning-device) 19907 Dev: 33; Already Running list: 15,16,18,19,29,30,21,
== FRESH START ==
1 01/29/10 18:14:32 Spawn_Device.sh 33 (spawning-device) device: 33 ip: 127.0.0.1 cmd_line: VDR
3 01/29/10 18:14:32 Spawn_Device.sh 33 (spawning-device) Can't execute VDR
and for the md /usr/pluto/diskless/34/var/log/pluto/42_VDR.log:
== ATTEMPT FRESH START ==
1 01/29/10 18:51:38 Spawn_Device.sh 42 (spawning-device) 9986 Dev: 42; Already Running list: 35,36,38,43,39,
== FRESH START ==
1 01/29/10 18:51:39 Spawn_Device.sh 42 (spawning-device) device: 42 ip: 192.168.1.2 cmd_line: VDR
3 01/29/10 18:51:39 Spawn_Device.sh 42 (spawning-device) Can't execute VDR
Of course, the "Can't execute VDR" doesn't look that nice but you can see that the ip for the core is localhost and the ip for the md ist the ip of the core (192.168.1.2). My guess is that I have to change the ip for all cases to 192.168.1.1 (my VDR server). But i have no idea where this comes from...
On my server runs version 1.7.7 of vdr. The change to the ts format was before this version, so I don't think this would be a problem.