Re: Why is one port better than another for streaming video?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



On Wed, 06 Jul 2005 10:17:04 GMT, "Neil Smith [MVP Digital Media]"
<neil@xxxxxxxxxx> wrote:

>On Wed, 06 Jul 2005 06:33:54 GMT, Videofreak <Thisguy@xxxxxxxxxxxxxx>
>wrote:
>
>>When I setup my web site to "PULL" video from my webcam I used a
>>randomly chosen, free port. ON my DSL connection it literally took 2.5
>>minutes for a 300kb live broadcast to travel a 768kb up connection.
>
>You mean a 2.5 minute *delay* before you saw the first frame ? Or was
>that end to end - did it keep saying 'buffering' on the player ?


Yeah I meant delay before I saw first video and delay before I saw 1
client acknowledged in WMEncoder. I'm thinking that at least one
reason for the long delay Was Zone Alarm Pro. I started using port
1755 and its very quick now.

>
>>Microsoft claims that port 8080 is best for video streams. I tried it.
>
>I don't remember seeing that claim. Can you post a web address where I
>can check your data for that ?

I'll look for it.Its on one of MS's WMEncoder pages. Also Zone Alarm
Pro has port 1755 set as default for the windows media expert rules
protocol section. Any Idea why?

"To broadcast a stream from the host computer, use IWMEncBroadcast to
specify the protocol and the port number from which to broadcast. HTTP
and port 8080 work best for broadcasting through firewalls."

Okay, So I sort of distorted what they said but pretty much says the
same thing. "Broadcasting"

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wmencode/htm/broadcastingastreamfromwindowsmediaencoder.asp

>
>It's actually "nonsense" if it is - the only "better" is if you set up
>your firewall to automagically use 8080 as the 'universal firewall
>avoidance port' when it's actually supposed to be used for discrete
>http services such as web servers, proxies or maybe SOAP services.
>
>>It took less than 7 seconds for the live feed to travel from
>>WMEncoder to my web site.
>
>The media path doesn't go to the web site but direct from the encoder
>to the media player (well, direct *through* a series of routers - but
>the website isn't involved in the data path). The website just hosts a
>location (IP address) where the encoder can be contacted.

So when Imbroadcasting and viewing the broadcast through an embedded
player on my website. Well I know the player actually resides on the
viewers machine. So in my own case isn't my broadcast traveling to my
ISP and then back down to my media player when I'm on the website? Or
is it just jumping straight to my media player?

>
>> In both scenarios I'm broadcasting and
>>checking the broadcast on my web site using the same PC. So why is
>>8080 so much better than other ports? And isn't it foolish to use the
>>default 8080 port since so many app's also use the default 8080
>
>Yes, it is. That's why you have a choice of which port to use - to
>avoid port service conflicts.
>
>>thereby making it one of the first choices a hacker would look for?
>
>I can trivially scan your system's 65535 available ports using nmap in
>about 2.5 seconds using my DSL line. So no, it's irrelevant. Applying
>a denial of service to the encoder is also trivial, you just open (and
>don't close) connection requests repeatedly until it's choked solid.
>
>It's not meant to be a high security system - the intention is to
>broadcast over http 'for ease of configuration' to a media server. It
>happens you can connect using a player (or something which simulates
>a player) but thankfully, this allows us to run these live streams to
>micro-audiences.
>
>I'm writing a website to handle most or all of this connect / locate /
>stream / broadcast for you - would u be inerested in having a play in
>a couple of weeks ?

Obviously you don't mean me specifically. You mean "a person". Keep
me informed
>
>Cheers - Neil

.



Relevant Pages

  • Re: prevent dhclient from exting
    ... > iface eth0 inet static ... port 67 interval 5 ... Oct 17 13:18:07 localhost dhclient: DHCPDISCOVER on eth0 to ... > file regarding broadcast address. ...
    (Debian-User)
  • Re: Should I configure a firewall to allow multicast?
    ... firewall is blocking various hosts to 192.168.1.255 port 138. ... but I know for certain there are no hosts with an address of 192.168.1.255. ... inet 192.168.1.9 netmask ffffff00 broadcast 192.168.1.255 ...
    (comp.security.firewalls)
  • Broadcasting for TV station
    ... I have to broadcast the video from any DV camera for local TV station ... from DV camera and broadcast it on particular port of the system successfully. ... Now I have to forward this transmission audio and video both from system ...
    (microsoft.public.windowsmedia.encoder)
  • Re: checking for bandwidth utilization
    ... command line on a cisco switch. ... you can easily see the real time traffic on any port, ... "storm-control broadcast level 3.00" which will allow up to 3% of the ... err-disabled mode fromt he storm control or the udld protection. ...
    (comp.dcom.sys.cisco)
  • Re: Wanting to place my hosted web on my server
    ... Port 80 is the default port for web services, ... Another method for unique website identification is the hostheader. ... IIS TIPS - Host Header - What is it: ... You mentioned earlier you installed DNS but wasn't ...
    (microsoft.public.windows.server.dns)