Aw: Re: Aw: Re: Aw: Re: Problem w/ Using tor(k) for Geostreaming Live-Videos

[f-ighting.erich@xxxxxxxx]

TOO bad! Now I bypass the ip geostreming shiled but end up with memory access error????

/tmp$ torkify mplayer rtsp://c36000-ls.w.core.cdn.streamfarm.net/2R38HDlo3/36000zdf/live/3546zdf/encoder.geozdf.geoevent_h.wmv

Playing rtsp://c36000-ls.w.core.cdn.streamfarm.net/2R38HDlo3/36000zdf/live/3546zdf/encoder.geozdf.geoevent_h.wmv.
Resolving c36000-ls.w.core.cdn.streamfarm.net for AF_INET...
Connecting to server c36000-ls.w.core.cdn.streamfarm.net[195.122.137.178]: 554...
STREAM_LIVE555, URL: rtsp://c36000-ls.w.core.cdn.streamfarm.net/2R38HDlo3/36000zdf/live/3546zdf/encoder.geozdf.geoevent_h.wmv
Stream not seekable!
 file format detected.
Speicherzugriffsfehler = momory access error!

if i use torify instead of torkify i get NO dns issue but the geostremer calls out bad ip again!

Can sombody beat this system :) :) -> http://wgeostreaming.zdf.de/encoder/livestream15_h.asx




----- Original Nachricht ----
Von:     Robert Hogan <robert@xxxxxxxxxxxxxxx>
An:      f-ighting.erich@xxxxxxxx
Datum:   11.06.2008 23:53
Betreff: Re: Aw: Re: Aw: Re: Problem w/ Using tor(k) for Geostreaming Live-Videos

> On Wednesday 11 June 2008 22:34:09 you wrote:
> > 
> >
> rtsp://c36000-ls.w.core.cdn.streamfarm.net/2R38HDlo3/36000zdf/live/3546zdf/
> >encoder.geozdf.geoevent_h.wmv
> 
> Hi Erich,
> 
> I'll answer off-list since it's probably not an or-talk issue.
> 
> 1. To confirm TorK is properly forcing all your Tor traffic through a german
> exit 
> node, you should browse through Konqueror or Firefox. If the flag appearing
> in 
> the yellow pop-up window is always german, then you are accessing the sites
> 
> through a german exit node and the 'pseudonymity' is working.
> 
> 2. You're right in your previous mail - only traffic that shows up in the
> yellow 
> pop-up is going through Tor. The flag there indicates what country the
> traffic 
> is leaving the Tor network from.
> 
> 3. torify mplayer [url]
> 
> is the format to use. torify can leak DNS addresses. TorK comes with a
> patched 
> version called torkify, which tries not to leak DNS requests. So you could
> also 
> try:
> 
> torkify mplayer [url]
> 
> Hopefully working through 1 and 2 above will help you confirm that TorK and
> Tor 
> are working as you expect them to. If those are working, then your issue is
> with 
> mplayer. 
> 
> Robert
> 
> 

Jetzt komfortabel bei Arcor-Digital TV einsteigen: Mehr Happy Ends, mehr Herzschmerz, mehr Fernsehen! Erleben Sie 50 digitale TV Programme und optional 60 Pay TV Sender, einen elektronischen Programmführer mit Movie Star Bewertungen von TV Movie. Außerdem, aktuelle Filmhits und spannende Dokus in der Arcor-Videothek. Infos unter www.arcor.de/tv