Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Michelle Deathmind
Amarr The Merchant Marines Miners With Attitude
|
Posted - 2006.11.23 02:43:00 -
[1]
Right, so I have three accounts of EVE, all of which I like to play on the same machine.
Lately thought I've been having some problems with my router, newly purchased. It seems to love disconnecting me quite often, and the problem only gets worse if I play more than one account at a time. I've checked the logs on my router, and here's an excert:
[INFO] Sat Feb 07 20:12:27 2004 Blocked incoming packet from 70.53.158.82:60222 to 210.233.201.210:6881 (protocol 6) [INFO] Sat Feb 07 20:12:26 2004 Blocked incoming packet from 24.68.232.105:2403 to 210.233.201.210:6881 (protocol 6) [INFO] Sat Feb 07 20:12:25 2004 Blocked incoming packet from 88.218.4.227:60690 to 210.233.201.210:6881 (protocol 6) [INFO] Sat Feb 07 20:12:25 2004 Blocked incoming packet from 60.50.240.7:2266 to 210.233.201.210:6881 (protocol 6) [INFO] Sat Feb 07 20:12:24 2004 Blocked incoming packet from 70.53.158.82:60222 to 210.233.201.210:6881 (protocol 6) [INFO] Sat Feb 07 20:12:23 2004 Blocked incoming packet from 24.68.232.105:2403 to 210.233.201.210:6881 (protocol 6) [INFO] Sat Feb 07 20:12:21 2004 Blocked incoming packet from 60.50.240.7:2266 to 210.233.201.210:6881 (protocol 6) [INFO] Sat Feb 07 20:12:21 2004 Blocked incoming packet from 70.53.158.82:60222 to 210.233.201.210:6881 (protocol 6) [INFO] Sat Feb 07 20:12:21 2004 SPI dropped TCP packet with flags 0x14 from 218.186.99.5:6881 to 210.233.201.210:51284 (unexpected in state 1) [INFO] Sat Feb 07 20:12:19 2004 SIP ALG rejected packet from 192.168.0.129:9001 to 67.133.32.41:5060 (protocol 17) [INFO] Sat Feb 07 20:12:18 2004 SPI dropped TCP packet with flags 0x14 from 144.136.79.55:6881 to 210.233.201.210:48334 (unexpected in state 1)
See all that protocol 6 nonsense? I'm near sure that that is the problem. I get a protocol 17 from time to time, but 6 is rampant in the logs.
Any ideas how to fix this? This is much a last ditch effort. If I don't get a solution by tomarrow, it's off to get a new router I go!
|
Lucid Nightmare
|
Posted - 2006.11.23 07:03:00 -
[2]
According to your logs it blocks ports used by Bittorrent. Running bittorrent and the gamefuel option in the router gets your uplink saturated. Gamefuel will schedule traffic but if it runs out of buffer space it will disconnect your internet for a bit to clear the buffer. Either turn off gamefuel or make sure your bittorrent application never is able to saturate your line (having to much open outgoing connections can saturate aswell). If you want to try with gamefuel on, make sure your bittorrent forwarding rules have the lowest priority.
|
Lucid Nightmare
|
Posted - 2006.11.23 07:19:00 -
[3]
One tip; remove your ip from the log above. Alot of new routers are easy to get into shutdown or slow responsiveness with a simple fast packet flood, because of the build in protections against denial of service attacks. Unless you turned those off. And you don't want that to happen when someone sneaky sees you in game and on purpose lags you out.
消すあなたのインターネット・ナンバーをよくしなさい
|
Michelle Deathmind
Amarr The Merchant Marines Miners With Attitude
|
Posted - 2006.11.23 12:12:00 -
[4]
1. Gamerfuel is off. I had it on for a bit, but deactivated it some time ago figuring it to be the problem. No results.
2. I don't have bit torret. :< I used limewire for a bit, but deleted it. I just recently obtained Bit Comet.
3. AIM has begun suffering disconnects as well. :<
4. IPs modified. ^_^
|
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |