My ears are sore from all that yelling...

http://www.slingcommunity.com/forumpolicy

Slinging Tivo Series 2, Tivo HD, and TW cable from a Pro. Slinging Tivo HD from a Solo, Slinging Humax DRT800, and TW cable from a Classic to Sprint Mogul, AT&T SX66, N62, 8525, and Dell Inspiron 8600 with Sprint EVDO over Windstream DSL.

I'm also using a Dlink DGL-4300 since its release more than a year ago. I also use it for my Slingbox Pro for about a month now. I used my Samsung Blackjack via Cingular EDGE network to watch TV on away from home. I set the packet prioritization to 1. I got a decent picture about 160 to 200 kbps at 6 to 13 fps

Slinging over Cingular EDGE/3G network using Samsung Blackjack via Slingbox Pro on a static DSL connection with GameFuel Priority Technology.

What kind of internet connection you have at home? I got a static DSL connection with downlink speed of 6 mbps & uplink speed of about 700 kbps. With this network speed, I just wonder why I can't get more than 300kbps on my Slingbox mobile. Also if you compare Wifi with 3G, the later is always faster.

Slinging over Cingular EDGE/3G network using Samsung Blackjack via Slingbox Pro on a static DSL connection with GameFuel Priority Technology.

Briteport DSL modem by Broadxent provided to me by my DSL provider (Speakeasy.net).

Slinging over Cingular EDGE/3G network using Samsung Blackjack via Slingbox Pro on a static DSL connection with GameFuel Priority Technology.

I dont know about that OMAPCLOCK. What is that?

Slinging over Cingular EDGE/3G network using Samsung Blackjack via Slingbox Pro on a static DSL connection with GameFuel Priority Technology.

CISco,

You need to stop making SO many posts and stop just throwing crap around.

First of all, you don't need traffic prioritization on your LAN if the Slingbox is the only thing running.  Traffic prioritization is ONLY important if you are going to have multiple protocols going out over the WAN.  All that this box that you have does is use standard QoS protocols that can be found in many routers and third part firmware like DD-WRT.

Upping the clock speed on your router does NOTHING to help speed up your LAN or for that matter your WAN traffic.  It will help in areas where your router is doing a lot of processing such as VPN or heavy QoS.

If you are hardwired on your LAN between your computer, router and Slingbox, there is no reason you should see slow speeds.  If you do, perhaps you have high quality mode turned off.  The typical router these days has a 100 Mb/sec speed on LAN ports.  The Slingbox will stream at a maximum of 8 Mb/sec.  So there's no need for traffic prioritization on the LAN as there is plenty of bandwidth.

Where people on the LAN side of things may have trouble is that they are using wireless either for the link between the Slingbox and the router or wireless between the router and computer or both.  Wireless 54G is not always 54 Mb/s.  And it is not even 54 Mb/s in a single direction but half that or 27 Mb/s.  On top of that, if someone is using  WDS to bridge between access points, the speed drops by 50%.  On top of that, if signal strength is weak, speeds drop further.  Low speeds are likely a result of poor wireless connectivity.

Now, on the WAN it's a different story.  Your bandwidth is limited to a fraction of what the Slingbox can put out.  My DSL connection from Speakeasy is 768 Kbits/sec uplink.  And no, Cable is NOT faster because it is also 768 Kbits/sec.  Nor does cable provide me with a fixed IP.  Back to my point...If you are Slinging over the WAN, the Slingbox will take up all that upstream traffic very easily.  For most people this is not a problem.  But if you are also at the same time, trying to carry on a VoIP conversation, do a Replay IVS transfer or something like that, you'll have problems.  In comes traffic shaping or QoS.  You can configure your router to give different prioritizations to different types of traffic.  And you can configure your router in some cases to limit the speed of certain devices on your network.

In my case, I limit my Slingbox to about 530 Kbps.  This leaves me headroom to allow someone else at home to browse the internet without any problems.  The Slingbox is set to a high priority so it takes precedence.  Higher priority is VoIP.  It will take precedence over the Slingbox.  My Replay IVS configuration though is low priority.  If I am doing an IVS transfer to someone, it takes up all my bandwidth if nothing else is going on.  If I start Slinging, the Slingbox takes over and streams at the 530 Kbps rate.  The IVS traffic is then reduced to whatever else is left on the remaining bandwidth.  It all works quite well.

Your coments though reflect a case where a little bit of knowledge is dangerous.  You are spouting stuff that really makes no difference and acting like you have this super secret, exclusive solution when in reality, it's not a solution at all, but mostly hot air.  QoS or prioritization is really not needed like I say on the LAN side unless you are constantly transferring massive files that suck up all the bandwidth.  But I don't think this is the problem most people who report slow speeds are having.  Rather it's a more fundamental problem with how they have the network set up overall.

Jon 

Slinging with a Slingbox Pro, a Slingbox Solo and a Slingbox Classic. 3 Replay TV units, a Roku HD1000 Photobridge and a Roku M2000 Soundbridge, an AppleTV, a Vudu, and digital cable. www.na9d.net