QOS on the DIR 655

[trunolimit]

This is my first post in this forum so please excuse noobyness

I've got a DIR-655 A2 FW1.21. I've got one pc on my network that does nothing but run bittorent apps and serves up my movies to my laptop when I'm plugged in. My sisters pc runs limewire and she surfs on it. I need advice on how to properly set the QOS so that the p2p stuff doesn't interfere with the web and ftp stuff. The way I have it set now works pretty well but I can't stream videos from my desktop to my laptop without it lagging.

here is a screen cap of what I'm dealing with. I don't know what most of the options are and I get a max of 10 rules. If I chose other the protocol window ungrays and I can type in a number for the protocol but i don't know what protocols have what numbers, is there some list somewhere?

I'm assuming that these port numbers represent destination port numbers because the source port numbers are randomly generated so you can't predict what that will be. this brings me to another question, how do you qos inbound traffic if they are coming in with random port numbers? Also what does the local IP range represent and the remote IP range? is local outbound trafic and remote inbound traffic?

I have a dd-wrt 24 wrt54gs v3. I know that has some qosing features but its limited to setting priorities on the physical ports. no layer 4 qosing. As far as I know the dir-655 are the only routers offering qos via port numbers and or protocol.

any help would be greatly appreciated.

 

[thiggins]

The DIR-655 and most other routers do not allow you to control download bandwidth. The 655's automatic QoS applies only to upload / outbound traffic to the Internet.

But you said your problem is streaming from desktop to laptop, which is LAN traffic and not affected by the router QoS engine. If it's a wireless stream, then you need to enable the WISH controls. WISH is focused on prioritizing streaming traffic, so the default controls may work fine.

Your problem, however, just might be not enough bandwidth for the content you are trying to stream. You should check to see what the stream bandwidth requirement is by using Netmeter or other similar application while running a stream.

 

[trunolimit]

Really? the router only shapes outbound traffic. That really sucks. The QOSing is honestly the only reason I bought this router. I need to look more into this WISH thing but I don't use the wireless on my laptop because it's so horrible. It's suppose to wireless N but I only get like 23mb of bandwith half the time and the laptop is in the same room as the router. I've tried to set the rx and tx sizes on everything and nothing worked. It's been my experience that for wireless n to work you need to pair the devices (dlink router w/ dlink wlan card, linksys router w/ linksys card ...ect)

I can probably get a good price for this router, do you think it'll be wise to get rid of it and buy a real router like a cisco catalyst on ebay? I've seen a lot of those cisco routers for dirt cheap and I've been studying for my ccna so I know the basics of setting it up. do you think I'd get better performance? And can I set up the qosing on those cisco routers?

on another note I've been looking at my logs and I've got a lot of them. I'll clear it and in like 10 minutes it'll be back to 1000+ log entries. most are denying udp and tcp because no session was established. it seems like the router is working really hard and all this traffic being caught in my firewall is eating up my processor. I'm going to post some of my logs can anyone tell me anyway I can alleviate my routers cpu?

here are just a couple of the log enteries. can anyone tell me even what these ports do? the xxx is my public ip

1990 Log Entries: PriorityTimeMessage
[INFO]Sat Jan 31 21:43:33 2004Blocked incoming TCP connection request from 142.166.205.78:61102 to xxx.xxx.xxx.xxx:41718
[INFO]Sat Jan 31 21:43:33 2004Blocked incoming UDP packet from 98.208.224.29:44336 to xxx.xxx.xxx.xxx:41718
[INFO]Sat Jan 31 21:43:32 2004Blocked incoming TCP connection request from 12.192.113.249:3162 to xxx.xxx.xxx.xxx:41718
[INFO]Sat Jan 31 21:43:32 2004Blocked incoming UDP packet from 86.137.31.90:53227 to xxx.xxx.xxx.xxx:40467
[INFO]Sat Jan 31 21:43:32 2004Blocked incoming TCP connection request from 88.100.183.154:54918 to xxx.xxx.xxx.xxx:41718
[INFO]Sat Jan 31 21:43:31 2004Blocked incoming UDP packet from 70.116.14.48:58777 to xxx.xxx.xxx.xxx:41718
[INFO]Sat Jan 31 21:43:31 2004Blocked incoming UDP packet from 70.107.132.184:50515 to xxx.xxx.xxx.xxx:41718
[INFO]Sat Jan 31 21:43:31 2004Allowed configuration authentication by IP address 192.168.0.197
[INFO]Sat Jan 31 21:43:31 2004Blocked incoming UDP packet from 24.130.100.244:30625 to xxx.xxx.xxx.xxx:41718
[INFO]Sat Jan 31 21:43:30 2004Blocked incoming TCP connection request from 88.100.183.154:54918 to xxx.xxx.xxx.xxx:41718
[INFO]Sat Jan 31 21:43:30 2004Blocked incoming UDP packet from 118.94.84.227:60924 to xxx.xxx.xxx.xxx:41718
[INFO]Sat Jan 31 21:43:30 2004Blocked incoming UDP packet from 88.105.42.140:27915 to xxx.xxx.xxx.xxx:41718
[INFO]Sat Jan 31 21:43:30 2004Blocked incoming UDP packet from 64.252.7.77:6535 to xxx.xxx.xxx.xxx:41718
[INFO]Sat Jan 31 21:43:29 2004Blocked incoming TCP connection request from 88.100.183.154:54918 to xxx.xxx.xxx.xxx:41718‏
[INFO]Sat Jan 31 21:43:28 2004Above message repeated 1 times
‏[INFO]Sat Jan 31 21:43:28 2004Blocked incoming TCP packet from 72.197.103.141:4244 to xxx.xxx.xxx.xxx:41718 as RST received but there is no active connection
[INFO]Sat Jan 31 21:43:28 2004Blocked incoming UDP packet from 84.122.147.11:6882 to xxx.xxx.xxx.xxx:41718
[INFO]Sat Jan 31 21:43:27 2004Blocked incoming TCP connection request from 88.100.183.154:54918 to xxx.xxx.xxx.xxx:41718
[INFO]Sat Jan 31 21:43:27 2004Blocked incoming TCP connection request from 142.166.205.78:61102 to xxx.xxx.xxx.xxx:41718

is there some port forwarding i have to do?

 

[scotty]

Really? the router only shapes outbound traffic. That really sucks. The QOSing is honestly the only reason I bought this router. I need to look more into this WISH thing but I don't use the wireless on my laptop because it's so horrible. It's suppose to wireless N but I only get like 23mb of bandwith half the time and the laptop is in the same room as the router. I've tried to set the rx and tx sizes on everything and nothing worked. It's been my experience that for wireless n to work you need to pair the devices (dlink router w/ dlink wlan card, linksys router w/ linksys card ...ect)

I can probably get a good price for this router, do you think it'll be wise to get rid of it and buy a real router like a cisco catalyst on ebay? I've seen a lot of those cisco routers for dirt cheap and I've been studying for my ccna so I know the basics of setting it up. do you think I'd get better performance? And can I set up the qosing on those cisco routers?

on another note I've been looking at my logs and I've got a lot of them. I'll clear it and in like 10 minutes it'll be back to 1000+ log entries. most are denying udp and tcp because no session was established. it seems like the router is working really hard and all this traffic being caught in my firewall is eating up my processor. I'm going to post some of my logs can anyone tell me anyway I can alleviate my routers cpu?

here are just a couple of the log enteries. can anyone tell me even what these ports do? the xxx is my public ip

1990 Log Entries: PriorityTimeMessage
[INFO]Sat Jan 31 21:43:33 2004Blocked incoming TCP connection request from 142.166.205.78:61102 to xxx.xxx.xxx.xxx:41718
[INFO]Sat Jan 31 21:43:33 2004Blocked incoming UDP packet from 98.208.224.29:44336 to xxx.xxx.xxx.xxx:41718
[INFO]Sat Jan 31 21:43:32 2004Blocked incoming TCP connection request from 12.192.113.249:3162 to xxx.xxx.xxx.xxx:41718
[INFO]Sat Jan 31 21:43:32 2004Blocked incoming UDP packet from 86.137.31.90:53227 to xxx.xxx.xxx.xxx:40467
[INFO]Sat Jan 31 21:43:32 2004Blocked incoming TCP connection request from 88.100.183.154:54918 to xxx.xxx.xxx.xxx:41718
[INFO]Sat Jan 31 21:43:31 2004Blocked incoming UDP packet from 70.116.14.48:58777 to xxx.xxx.xxx.xxx:41718
[INFO]Sat Jan 31 21:43:31 2004Blocked incoming UDP packet from 70.107.132.184:50515 to xxx.xxx.xxx.xxx:41718
[INFO]Sat Jan 31 21:43:31 2004Allowed configuration authentication by IP address 192.168.0.197
[INFO]Sat Jan 31 21:43:31 2004Blocked incoming UDP packet from 24.130.100.244:30625 to xxx.xxx.xxx.xxx:41718
[INFO]Sat Jan 31 21:43:30 2004Blocked incoming TCP connection request from 88.100.183.154:54918 to xxx.xxx.xxx.xxx:41718
[INFO]Sat Jan 31 21:43:30 2004Blocked incoming UDP packet from 118.94.84.227:60924 to xxx.xxx.xxx.xxx:41718
[INFO]Sat Jan 31 21:43:30 2004Blocked incoming UDP packet from 88.105.42.140:27915 to xxx.xxx.xxx.xxx:41718
[INFO]Sat Jan 31 21:43:30 2004Blocked incoming UDP packet from 64.252.7.77:6535 to xxx.xxx.xxx.xxx:41718
[INFO]Sat Jan 31 21:43:29 2004Blocked incoming TCP connection request from 88.100.183.154:54918 to xxx.xxx.xxx.xxx:41718‏
[INFO]Sat Jan 31 21:43:28 2004Above message repeated 1 times
‏[INFO]Sat Jan 31 21:43:28 2004Blocked incoming TCP packet from 72.197.103.141:4244 to xxx.xxx.xxx.xxx:41718 as RST received but there is no active connection
[INFO]Sat Jan 31 21:43:28 2004Blocked incoming UDP packet from 84.122.147.11:6882 to xxx.xxx.xxx.xxx:41718
[INFO]Sat Jan 31 21:43:27 2004Blocked incoming TCP connection request from 88.100.183.154:54918 to xxx.xxx.xxx.xxx:41718
[INFO]Sat Jan 31 21:43:27 2004Blocked incoming TCP connection request from 142.166.205.78:61102 to xxx.xxx.xxx.xxx:41718

is there some port forwarding i have to do?

You might want to have a look at pfSense. It's an open source BSD based router that's really easy to set up and use, but very powerful with a huge feature set. It'll run on pretty much any old computer (even old P3's will do fine). All you typically need is an extra NIC or two.

It does better QoS.

 

[trunolimit]

You might want to have a look at pfSense. It's an open source BSD based router that's really easy to set up and use, but very powerful with a huge feature set. It'll run on pretty much any old computer (even old P3's will do fine). All you typically need is an extra NIC or two.

It does better QoS.

So basicaly it's software that turns a pc into a router? Thats actually really cool and it makes sence because a router is just a mini computer. I've got a ton of nics lying around.

 

[scotty]

So basicaly it's software that turns a pc into a router? Thats actually really cool and it makes sence because a router is just a mini computer. I've got a ton of nics lying around.

Yep. It's an operating system (BSD) that basically does routing. It's installed off a cd and after a few questions and wizards you're set. It has simple web based configuration like any other router. Tons of features including pretty slick QoS.