|
|
Post by unisol on Jul 22, 2006 16:37:10 GMT -8
Hey Johnny...how do you have your GameFuel setup?
When I do automatic speed test, it comes up with 512 for the uplink, but when I goto Speakeasy and do a speed test, I get 320.
Also, when I am using passive with my FTP client, GameFuel seems not to work. My games are supper laggy and my pings are way up there, but when I set my FTP client to Active, it seems to work.
|
|
|
|
Post by Johnny Grenade on Jul 22, 2006 18:56:02 GMT -8
I manually set my upstream bandwidth.
automatic classification on, dynamic fragmentation on, automatic uplink speed off. Connection set to cable/broadband. No gamefuel special rules.
I dont have any issues on the uplink side. But Im not using passive FTP. I think you may need to specify a rule for that since it uses dynamicly allocated ports in the range of 1024-5000 I think. Maybe the router doesnt know what service its classifying.
I would just switch to active mode if you are running a FTP server on the LAN side. Just set up a Virtual server on the virtual server page and forward port 21 over to the server you are running the FTP server from.
|
|
|
|
Post by unisol on Jul 23, 2006 17:00:43 GMT -8
Yea it seems to be working better running Active mode.
I checked the active sessions list and I saw some ports that could be associated with games being used for transfers so I suppose that GameFuel would give them higher priority.
|
|
|
|
Post by Johnny Grenade on Aug 27, 2006 10:02:31 GMT -8
Hey Unisol, I was messing with those game rules to balance out the bit torrent and I dont think it works properly . In auto classification mode it was assigning priority 130 to UDP on 6881. I created a rule for that port and gave it the lowest priority 255 and it didnt seem to make any difference. Im thinking that those rules only apply when autoclassification is OFF.
I didnt try it because the network was busy at the time.
|
|
|
|
Post by unisol on Aug 27, 2006 14:39:27 GMT -8
Yep, I am thinking the same thing.
I am having trouble with FTP transfers while gaming also. I am good for most of the part, but about every minute or so, I lose my connection to the server for a few seconds, then my ping drops back down to where it should be for another minute. This is real annoying when uploading a 1+ GB file and it takes 10hrs and I can't game while doing it.
I am thinking GameFuel is not what it is all cracked up to be. I had much better performance from my m0n0wall in this respect.
|
|
|
|
Post by unisol on Aug 27, 2006 14:47:05 GMT -8
Here is one for ya.....
Ok, let's say you manually set your uplink speed in GameFuel and you set it lower than what it actually is. That is what your uplink will be limited to. The speedtest thing was getting old everytime I rebooted so I set it to 312k. Then I noticed when doing my FTP transfer of POE2 up to our site, my upload rate was like 28 KB/s. So, just now, I set it to auto detect my upload speed and it came back with 493kbps and now I resumed that FTP transfer and it is going at 45.6 KB/s.
I have seen this before with m0n0wall's system similar to GameFuel. If you set it too high, the prioritizing of packets didn't work since it never realized you were saturating your upload, and set it to low, it capped your upload at whatever you set it to.
|
|
|
|
Post by Johnny Grenade on Aug 27, 2006 17:14:12 GMT -8
I used manual mode since day one. All it took was one reboot and I had enough of the auto detect feature. I really havent had any problems with the classification that I can detect though. My FTP uploads never caused a problem, but I suspect it has to do with active mode versus passive mode or something. That bit torrent was the first time I had seen that it wasnt giving TS2 a high enough prioroity. Now that I think about it. You should probably set up that rule setting port 6881 on any UDP or TCP and assign it a 250 priority then save and reboot the router. We havent tried rebooting it. Maybe that chip needs the hard boot?
|
|
|
|
Post by unisol on Aug 27, 2006 18:16:12 GMT -8
But, TS2 gives the clients dynamic ports.
|
|
|
|
Post by Johnny Grenade on Aug 27, 2006 20:05:53 GMT -8
6881 is bit-torrent. Just lower that priority and leave ts2 where it is.
|
|
|
|
Post by unisol on Aug 28, 2006 5:10:37 GMT -8
That is a good idea, I will have to limit my Torrent client to a small set of ports and lower the priority on each of them.
|
|
|
|
Post by Johnny Grenade on Aug 28, 2006 5:46:32 GMT -8
That is a good idea, I will have to limit my Torrent client to a small set of ports and lower the priority on each of them. I use Azareus for bit torrent and it always uses 6881. |
|
|
|
Post by unisol on Sept 23, 2006 18:26:49 GMT -8
Hey JG, I can't connect to servers with Source on two different computers at the same time. Me an my son were gonna play some CS:S and if one of us was on a server, the other couldn't connect to it. This shouldn't be that way since Slammer and his kid can play and I know there were 3 clowns connecting from the same connection over at Ten, Dans, and TrashedRC's house last spring.
I think it may DLG-4300 related.
|
|
|
|
Post by unisol on Sept 23, 2006 22:38:06 GMT -8
Ok, it sure is a DLG-4300 related problem. I rebooted the 4300 and CS:S now works from two PC's at once.
Maybe the 4300 is not as infalible as I once thought.
|
|
|
|
Post by Johnny Grenade on Sept 24, 2006 5:40:25 GMT -8
Stop messing with it. Its set it and forget it. Lol
Seriously, I've had stuff happen like that before, but then again my old SMC did that as well periodically. A good flush of the routing cache usually is the fix. (IE. reboot )
Ive noticed problems related to the ingame browser when you have a rule always forwarding traffic from your wan to the game server. IF you always connect to the server from the WAN IP address, rather than the server LAN address, the problem seems to go away.
|
|
|
|
Post by unisol on Oct 21, 2006 21:29:00 GMT -8
Ok, I think I figured out how to get Gamefuel to work right. I was uploading a couple of episodes of BSG tonight via FTP and I couldn't surf at all. I made a rule in Gamefuel and got nothing. I then went searching and came upon this thread over at Broadband Reports: www.dslreports.com/forum/remark,16964922?r=396 I was setting the internal port range to 20:21 and the external port range to 20:21 as well. This got me no improvement at all. After reading that thread and seeing this screenshot:  I have it set like this now, and it seems to be doing it's thing now. |
|
|
|
Post by House Of Boom on Oct 23, 2006 6:13:51 GMT -8
Cool. glad its working for you. Thanks for posting so when I have this problem I will be able to fix it. I see you only apply it to 5 IP addresses. Why dont you include the entire DHCP range on the 192.168 net, or do you only dole out 5 IP addresses on your network?
|
|
|
|
Post by unisol on Oct 23, 2006 21:36:16 GMT -8
Thats not my screenshot. I meant to use that for an example of not restricting the source ports range. I think that is where my problem was, I noticed in the status page that the port was 21, but under the NAT column it could be anything.
|
|
