Diagnoce this connection problem

[joeblow]

Been having a slight connection issue. Looking at my logs on my router I keep seeing these packets being blocked from other ISP when I'm in game. Any ideas.


[INFO] Mon May 14 00:30:29 2007 Log viewed by IP address MY IP ADDY
[INFO] Mon May 14 00:30:15 2007 Allowed configuration authentication by IP address
[INFO] Mon May 14 00:30:15 2007 Previous message repeated 2 times
[INFO] Mon May 14 00:29:06 2007 Blocked incoming TCP connection request from 60.230.63.144:60001 to 71.203.223.155:21089
[INFO] Mon May 14 00:28:30 2007 Blocked incoming UDP packet from 66.150.223.30:12415 to 71.203.223.155:33441
[INFO] Mon May 14 00:28:25 2007 Blocked incoming UDP packet from 66.150.223.18:12415 to 71.203.223.155:33439
[INFO] Mon May 14 00:28:25 2007 Blocked incoming UDP packet from 66.150.223.30:12415 to 71.203.223.155:33441
[INFO] Mon May 14 00:28:20 2007 Blocked incoming UDP packet from 66.150.223.18:12415 to 71.203.223.155:33439
[INFO] Mon May 14 00:28:20 2007 Blocked incoming UDP packet from 66.150.223.30:12415 to 71.203.223.155:33441
[INFO] Mon May 14 00:28:15 2007 Blocked incoming UDP packet from 66.150.223.18:12415 to 71.203.223.155:33439
[INFO] Mon May 14 00:28:15 2007 Blocked incoming UDP packet from 66.150.223.30:12415 to 71.203.223.155:33441
[INFO] Mon May 14 00:28:10 2007 Blocked incoming UDP packet from 66.150.223.18:12415 to 71.203.223.155:33439
[INFO] Mon May 14 00:28:10 2007 Blocked incoming UDP packet from 66.150.223.30:12415 to 71.203.223.155:33441
[INFO] Mon May 14 00:28:05 2007 Blocked incoming UDP packet from 66.150.223.18:12415 to 71.203.223.155:33439
[INFO] Mon May 14 00:28:05 2007 Blocked incoming UDP packet from 66.150.223.30:12415 to 71.203.223.155:33441
[INFO] Mon May 14 00:28:00 2007 Blocked incoming UDP packet from 66.150.223.18:12415 to 71.203.223.155:33439
[INFO] Mon May 14 00:28:00 2007 Previous message repeated 2 times
[INFO] Mon May 14 00:24:43 2007 Blocked incoming TCP connection request from 60.230.63.144:59457 to 71.203.223.155:21089
[INFO] Mon May 14 00:23:28 2007 Blocked incoming UDP packet from 204.16.208.33:57851 to 71.203.223.155:1026
[INFO] Mon May 14 00:23:28 2007 Previous message repeated 2 times
[INFO] Mon May 14 00:19:03 2007 Blocked incoming TCP connection request from 60.230.63.144:58696 to 71.203.223.155:21089
[INFO] Mon May 14 00:17:54 2007 Blocked incoming UDP packet from 81.47.152.252:30338 to 71.203.223.155:1026
[INFO] Mon May 14 00:17:54 2007 Previous message repeated 2 times
[INFO] Mon May 14 00:14:10 2007 Blocked incoming TCP connection request from 60.230.63.144:58042 to 71.203.223.155:21089
[INFO] Mon May 14 00:14:10 2007 Previous message repeated 2 times
[INFO] Mon May 14 00:07:41 2007 Blocked incoming TCP connection request from 60.230.63.144:57071 to 71.203.223.155:21089
[INFO] Mon May 14 00:05:16 2007 Blocked incoming UDP packet from 204.16.208.63:44740 to 71.203.223.155:1026
[INFO] Mon May 14 00:05:16 2007 Previous message repeated 2 times

wp


[

[DW_ACY]

ah ............. joe it looks as if no one wnats to even come close to your little problem. :dark1:

[DW_Tsanger]

try turning off your firewall. not sure if that is it or not but it's a start.

[DW_e_aLpHa]

- This is completely normal, Unless it's giving you ''Trouble'' .. You can't never stop your router from generating this kind of reports!! If It's instructed to do so (bloking kinds of conection atempts) .. -

It all depends in your Firewall Settings(on the router) and or Port Settings / Forwarding or not / also on your router capabilities .


IF you think this is somehow causing you 'lag' in game , Don't blame it on your router since it can go furter than that and extend to other isues like other routers on your path to the servers or you computer itself . ( Of course considering that your Conection Speed is Good)

Don't worry about this kind of reports from your Router, you will see them all the time and don't necessary have to mean trouble . Take a look at your router configuration instead and make sure it allows what needs to be allowed tru it's firewall settings. (for whatever your needs are, wich I surely ignore )

[joeblow]

Well I did a ping test and eveything looks pretty good right after I wrote that. The hops after me to Comcast the ping average was 32 -860 so thats prolly why i see funny things in game. 0% packet loss on a thousand packets is great!.

I was one Dremus running for the tunnel and fell off to the sides is when I really started noticing it.

I just don't remember that router sending me those messages blocking those Ips. There not on the tracer route to the server either. The UDP is whats wierd to I thought only games use UDP mostly.

Am I seeing people's IPs that Im playing against for some reason?

Am i being packet flooded maybe ?


I did flash the Firmware its a D-links d4100 I think Game fuel router. I need to set up the Game fuel part again I forgot I reset it a few times and lost all that when I added on a wireless router to it. I will also change the date sorry its off a few days by the log.


wp

[joeblow]

Ok heres another quick log. Im a little wary about turning off the fire wall. I dunno if im being attacked or not.

[INFO] Sat May 19 16:17:23 2007 Blocked outgoing TCP packet from 192.168.0.147:49407 to 69.73.36.76:443 as FIN:PSH:ACK received but there is no active connection
[INFO] Sat May 19 16:17:09 2007 Blocked outgoing TCP packet from 192.168.0.147:49404 to 69.73.36.71:80 as FIN:ACK received but there is no active connection
[INFO] Sat May 19 16:17:09 2007 Blocked outgoing TCP packet from 192.168.0.147:49409 to 69.73.36.76:443 as FIN:PSH:ACK received but there is no active connection
[INFO] Sat May 19 16:17:09 2007 Blocked outgoing TCP packet from 192.168.0.147:49411 to 69.73.36.72:80 as FIN:ACK received but there is no active connection
[INFO] Sat May 19 16:16:19 2007 Blocked outgoing TCP packet from 192.168.0.147:49407 to 69.73.36.76:443 as FIN:PSH:ACK received but there is no active connection
[INFO] Sat May 19 16:16:05 2007 Blocked outgoing TCP packet from 192.168.0.147:49404 to 69.73.36.71:80 as FIN:ACK received but there is no active connection
[INFO] Sat May 19 16:16:05 2007 Blocked outgoing TCP packet from 192.168.0.147:49409 to 69.73.36.76:443 as FIN:PSH:ACK received but there is no active connection
[INFO] Sat May 19 16:16:05 2007 Blocked outgoing TCP packet from 192.168.0.147:49411 to 69.73.36.72:80 as FIN:ACK received but there is no active connection
[INFO] Sat May 19 16:15:33 2007 Blocked outgoing TCP packet from 192.168.0.147:49404 to 69.73.36.71:80 as FIN:ACK received but there is no active connection
[INFO] Sat May 19 16:15:33 2007 Blocked outgoing TCP packet from 192.168.0.147:49409 to 69.73.36.76:443 as FIN:PSH:ACK received but there is no active connection
[INFO] Sat May 19 16:15:33 2007 Blocked outgoing TCP packet from 192.168.0.147:49411 to 69.73.36.72:80 as FIN:ACK received but there is no active connection
[INFO] Sat May 19 16:15:31 2007 Blocked outgoing TCP packet from 192.168.0.147:49407 to 69.73.36.76:443 as FIN:PSH:ACK received but there is no active connection
[INFO] Sat May 19 16:15:09 2007 Blocked outgoing TCP packet from 192.168.0.147:49404 to 69.73.36.71:80 as FIN:ACK received but there is no active connection
[INFO] Sat May 19 16:15:09 2007 Blocked outgoing TCP packet from 192.168.0.147:49409 to 69.73.36.76:443 as FIN:PSH:ACK received but there is no active connection
[INFO] Sat May 19 16:15:09 2007 Blocked outgoing TCP packet from 192.168.0.147:49411 to 69.73.36.72:80 as FIN:ACK received but there is no active connection
[INFO] Sat May 19 16:15:07 2007 Blocked outgoing TCP packet from 192.168.0.147:49407 to 69.73.36.76:443 as FIN:PSH:ACK received but there is no active connection
[INFO] Sat May 19 16:14:57 2007 Blocked outgoing TCP packet from 192.168.0.147:49404 to 69.73.36.71:80 as FIN:ACK received but there is no active connection
[INFO] Sat May 19 16:14:57 2007 Blocked outgoing TCP packet from 192.168.0.147:49409 to 69.73.36.76:443 as FIN:PSH:ACK received but there is no active connection
[INFO] Sat May 19 16:14:57 2007 Blocked outgoing TCP packet from 192.168.0.147:49411 to 69.73.36.72:80 as FIN:ACK received but there is no active connection
[INFO] Sat May 19 16:14:55 2007 Blocked outgoing TCP packet from 192.168.0.147:49407 to 69.73.36.76:443 as FIN:PSH:ACK received but there is no active connection
[INFO] Sat May 19 16:14:51 2007 Blocked outgoing TCP packet from 192.168.0.147:49404 to 69.73.36.71:80 as FIN:ACK received but there is no active connection
[INFO] Sat May 19 16:14:51 2007 Blocked outgoing TCP packet from 192.168.0.147:49409 to 69.73.36.76:443 as FIN:PSH:ACK received but there is no active connection
[INFO] Sat May 19 16:14:51 2007 Blocked outgoing TCP packet from 192.168.0.147:49411 to 69.73.36.72:80 as FIN:ACK received but there is no active connection
[INFO] Sat May 19 16:14:49 2007 Blocked outgoing TCP packet from 192.168.0.147:49407 to 69.73.36.76:443 as FIN:PSH:ACK received but there is no active connection
[INFO] Sat May 19 16:14:48 2007 Blocked outgoing TCP packet from 192.168.0.147:49404 to 69.73.36.71:80 as FIN:ACK received but there is no active connection
[INFO] Sat May 19 16:14:48 2007 Blocked outgoing TCP packet from 192.168.0.147:49409 to 69.73.36.76:443 as FIN:PSH:ACK received but there is no active connection
[INFO] Sat May 19 16:14:48 2007 Blocked outgoing TCP packet from 192.168.0.147:49411 to 69.73.36.72:80 as FIN:ACK received but there is no active connection
[INFO] Sat May 19 16:14:47 2007 Blocked outgoing TCP packet from 192.168.0.147:49404 to 69.73.36.71:80 as FIN:ACK received but there is no active connection
[INFO] Sat May 19 16:14:47 2007 Blocked outgoing TCP packet from 192.168.0.147:49409 to 69.73.36.76:443 as FIN:ACK received but there is no active connection
[INFO] Sat May 19 16:14:47 2007 Blocked outgoing TCP packet from 192.168.0.147:49409 to 69.73.36.76:443 as PSH:ACK received but there is no active connection
[INFO] Sat May 19 16:14:47 2007 Blocked outgoing TCP packet from 192.168.0.147:49407 to 69.73.36.76:443 as FIN:ACK received but there is no active connection
[INFO] Sat May 19 16:14:47 2007 Blocked outgoing TCP packet from 192.168.0.147:49407 to 69.73.36.76:443 as PSH:ACK received but there is no active connection
[INFO] Sat May 19 16:14:47 2007 Blocked outgoing TCP packet from 192.168.0.147:49411 to 69.73.36.72:80 as FIN:ACK received but there is no active connection
[INFO] Sat May 19 16:14:47 2007 Previous message repeated 1 time
[INFO] Sat May 19 16:11:07 2007 Blocked incoming TCP connection request from 69.20.61.30:45894 to 71.203.223.155:21
[INFO] Sat May 19 16:09:44 2007 Blocked incoming UDP packet from 24.64.200.138:22457 to 71.203.223.155:1028
[INFO] Sat May 19 16:09:44 2007 Blocked incoming UDP packet from 24.64.200.138:22457 to 71.203.223.155:1027
[INFO] Sat May 19 16:09:44 2007 Blocked incoming UDP packet from 24.64.200.138:22457 to 71.203.223.155:1026
[INFO] Sat May 19 16:08:22 2007 Blocked incoming UDP packet from 24.64.67.151:2659 to 71.203.223.155:1028
[INFO] Sat May 19 16:08:22 2007 Blocked incoming UDP packet from 24.64.67.151:2659 to 71.203.223.155:1027


Its bugging me thats its the same IP's that showing up. I shut off ICQ and anything else that I thought might be sending out info.

wp

[DW_Cheapshot]

Thought I would confuse things,



KNOLOGY Holdings, Inc. KNOLOGY-NET (NET-69-73-0-0-1)
69.73.0.0 - 69.73.127.255

this is the block your machine was trying to reach.

[joeblow]

Well that is interesting. We do have Knology available in Knoxville but I have not had it since we moved to this new house about a year ago. In fact its never been on either the XP or Vista box since there new this year and its not available on this side of time. Its the B service here. Where on Comcast again.

Should I just go ahead and block these addresses with my router?



wp

[DW_Cheapshot]

If you were really curious as to what is trying to phone home or whatever
try to get a copy of zone alarm. just run it long enough to see who or
what is calling out. thy had a free version at one time.
it can block all outgoing unless you allow it. and will list and ask if it is
allowed.
If your router can deny a group of IPs I think its a good idea,
being that Im a parinoid person anywhy. I run zone alarm full time,
guess im lucky never a problem with it. Cheap :bigsmurf: