hmm das ist ja schön und gut aber bei mir tut sich da mal garnix
habe das damals schon im vdsinfo gelesen und hatte keinen erfolg
weder vlc noch mplayer verursachen traffic
google sagt was von problemen mit multicast und winxp sp2 aber so richtig schlau werd ich daraus nicht
hier der log vom vcl, firewall und kram alles aus:
main debug: prebuffering done 0 bytes in 352s - 0 kbytes/s
main error: cannot pre fill buffer
main warning: cannot create a stream_t from access
main debug: removing module "access_udp"
main debug: thread times: real 5m57.046875s, kernel 0m0.015625s, user 0m0.000000s
main debug: thread 4124 joined (input/input.c:412)
main debug: creating new input thread
main debug: waiting for thread completion
main debug: thread 4124 (input) created at priority 1 (input/input.c:265)
main debug: `udp://@239.35.129.11:10000' gives access `udp' demux `' path `@239.35.129.11:10000'
main debug: creating demux: access='udp' demux='' path='@239.35.129.11:10000'
main debug: looking for access_demux module: 0 candidates
main warning: no access_demux module matched "udp"
main debug: creating access 'udp' path='@239.35.129.11:10000'
main debug: looking for access2 module: 6 candidates
access_udp debug: opening server=:0 local=239.35.129.11:10000
main debug: net: connecting to '[]:0@[239.35.129.11]:10000'
main debug: looking for network module: 1 candidate
ipv6 debug: 239.35.129.11: Host or service not found
main debug: using network module "ipv6"
main debug: removing module "ipv6"
main debug: looking for network module: 1 candidate
ipv4 debug: resolving 239.35.129.11:10000...
ipv4 debug: resolving :0...
ipv4 debug: Winsock best interface is 2
ipv4 debug: using interface 0xeeeea8c0
ipv4 debug: IP_ADD_MEMBERSHIP multicast request
main debug: using network module "ipv4"
main debug: removing module "ipv4"
main debug: using access2 module "access_udp"
main debug: pre buffering