• April 26, 2024, 09:04:28 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: Anyone help? Pls review log  (Read 6783 times)

Jimbo2552

  • Level 1 Member
  • *
  • Posts: 5
Anyone help? Pls review log
« on: October 09, 2010, 09:20:54 PM »

So I am playing Global Agenda, and it loses connection for 5-9 seconds then comes back. This happened earlier today with StarCraft 2, I would lag out for 5-9 seconds. So I decided to log into the router and see what was going on, and I saw this in the logs (excerpt from log):

It seems for some reason the connection gets blocked randomly... why is this happening?

I installed my router yesterday, and updated it with the latest firmware.  I have road runner from Time Warner cable.

[INFO]   Sat Oct 09 18:09:24 2010   Blocked incoming TCP packet from 67.162.185.***:2361 to 66.91.3.205:***as RST received but there is no active connection
[INFO]   Sat Oct 09 18:09:24 2010   Blocked incoming UDP packet from 99.11.23.168:57067 to 66.91.3.205:61018
[INFO]   Sat Oct 09 18:09:22 2010   SIP ALG rejected packet from 192.168.0.***:8146 to 70.42.62.***:5062
[INFO]   Sat Oct 09 18:09:14 2010   Blocked incoming TCP packet from 98.67.217.***:1837 to 66.91.3.***:57887 as RST:ACK received but there is no active connection
[INFO]   Sat Oct 09 18:08:42 2010   SIP ALG rejected packet from 192.168.0.***:8146 to 70.42.62.***:5062
[INFO]   Sat Oct 09 18:08:35 2010   Blocked incoming UDP packet from 78.55.243.***:63562 to 66.91.3.***.****
[INFO]   Sat Oct 09 18:08:05 2010   Above message repeated 6 times
[INFO]   Sat Oct 09 18:08:02 2010   SIP ALG rejected packet from 192.168.0.***:8146 to 70.42.62.***:5062
[INFO]   Sat Oct 09 18:08:00 2010   Blocked incoming UDP packet from 78.55.243.153:63562 to 66.91.3.205:49380
[INFO]   Sat Oct 09 18:07:35 2010   Above message repeated 5 times
[INFO]   Sat Oct 09 18:07:22 2010   SIP ALG rejected packet from 192.168.0.***:8146 to 70.42.62.***:5062


Thanks!
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Anyone help? Pls review log
« Reply #1 on: October 10, 2010, 11:54:27 AM »

Have you set up IP reservations, Gaming and possible gamefuel rules for the PC your playing on? I presume your playing on a PC for these games? Check out the gameing and gamefuel sticky. It pertains to game consoles however you can sub the info for PC Ip addressing. You'll need to find the exact port numbers for SC and GA and use those. It's fairly easy to do. I have XBOX live set on my one PC for Halo2 for PC however in Gaming however I don't use gamefuel for PC, just my 2 xboxes. All the other options mentioned in the sticky work well for both gaming and general internet use. I'm also on cable so I don't think your cable modem has any extra feature like a internal router like some DSL modems too. You should be good, lets see if you can get the gaming set up. Let us know how it goes.
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

Jimbo2552

  • Level 1 Member
  • *
  • Posts: 5
Re: Anyone help? Pls review log
« Reply #2 on: October 10, 2010, 06:25:40 PM »

Thanks I will try it out...

Should I shut SPI off?
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Anyone help? Pls review log
« Reply #3 on: October 10, 2010, 09:13:28 PM »

No, I have mine set on. Try End Point Independent for both UDP and TCP and also try Address Restricted for UDP and Port and Address Restricted for TCP and see how well it works. No performance, this is just safety.
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

Trikein

  • Guest
Re: Anyone help? Pls review log
« Reply #4 on: October 11, 2010, 08:35:29 PM »

Perhaps this will be helpful. Global Agenda Port Forwarding

But as the site says, most routers will configure this with UPnP, make sure that is enabled on your router. As long as your not on some other more complex network, you should be set. But if not, just forward the ports.
Logged

Trikein

  • Guest
Re: Anyone help? Pls review log
« Reply #5 on: October 11, 2010, 08:38:06 PM »

By the way...Kill the elves!!! Well except Drizzt. Heh

Was a inside joke from Global Agenda's smear campaign against WoW. Enemy of my enemy and all that. Annnnnyway, let me know how it goes Jimbo
« Last Edit: October 11, 2010, 09:38:47 PM by Trikein »
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Anyone help? Pls review log
« Reply #6 on: October 11, 2010, 09:12:43 PM »

 ???
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

Jimbo2552

  • Level 1 Member
  • *
  • Posts: 5
Re: Anyone help? Pls review log
« Reply #7 on: October 12, 2010, 10:29:48 PM »

Ok I am still getting alot of messages in my log:

Priority   Time   Message
[INFO]   Tue Oct 12 19:21:54 2010   Blocked incoming UDP packet from 70.42.62.252:5062 to 66.91.*.***:8146
[INFO]   Tue Oct 12 19:21:29 2010   Blocked incoming TCP connection request from 98.232.51.190:50186 to 66.91.*.***:443
[INFO]   Tue Oct 12 19:21:23 2010   Above message repeated 1 times
[INFO]   Tue Oct 12 19:21:20 2010   Blocked incoming TCP connection request from 208.54.4.58:32186 to 66.91.*.***:443
[INFO]   Tue Oct 12 19:21:20 2010   Blocked incoming TCP connection request from 98.232.51.190:50186 to 66.91.*.***:443
[INFO]   Tue Oct 12 19:21:09 2010   Blocked incoming TCP connection request from 76.30.77.102:53533 to 66.91.*.***:443
[INFO]   Tue Oct 12 19:21:08 2010   Blocked incoming UDP packet from 99.175.211.20:57195 to 66.91.*.***:56136
[INFO]   Tue Oct 12 19:21:03 2010   Blocked incoming TCP connection request from 76.30.77.102:53533 to 66.91.*.***:443
[INFO]   Tue Oct 12 19:21:00 2010   Blocked incoming UDP packet from 99.175.211.20:57195 to 66.91.*.***:56136
[INFO]   Tue Oct 12 19:21:00 2010   Blocked incoming TCP connection request from 76.30.77.102:53533 to 66.91.*.***:443
[INFO]   Tue Oct 12 19:20:56 2010   Blocked incoming UDP packet from 112.207.58.74:1095 to 66.91.*.***:56131
[INFO]   Tue Oct 12 19:20:56 2010   Blocked incoming TCP connection request from 208.54.4.58:22204 to 66.91.*.***:443
[INFO]   Tue Oct 12 19:20:50 2010   Blocked incoming UDP packet from 112.207.58.74:1095 to 66.91.*.***:56131
[INFO]   Tue Oct 12 19:20:46 2010   Blocked incoming TCP connection request from 208.54.4.58:22807 to 66.91.*.***:80
[INFO]   Tue Oct 12 19:20:44 2010   Blocked incoming TCP connection request from 208.54.4.58:22204 to 66.91.*.***:443
[INFO]   Tue Oct 12 19:20:42 2010   Blocked incoming TCP packet from 94.254.28.197:57313 to 66.91.*.***:57887 as RST:ACK received but there is no active connection
[INFO]   Tue Oct 12 19:20:38 2010   Blocked incoming TCP connection request from 208.54.4.58:16107 to 66.91.*.***:443
[INFO]   Tue Oct 12 19:20:38 2010   Blocked incoming TCP packet from 116.15.7.43:2737 to 66.91.*.***:57887 as RST:ACK received but there is no active connection
[INFO]   Tue Oct 12 19:20:35 2010   Blocked incoming TCP connection request from 208.54.4.58:16107 to 66.91.*.***:443
[INFO]   Tue Oct 12 19:20:34 2010   Blocked incoming TCP connection request from 208.54.4.74:29752 to 66.91.*.***:80
[INFO]   Tue Oct 12 19:20:32 2010   Blocked incoming TCP connection request from 208.54.4.58:16107 to 66.91.*.***:443
[INFO]   Tue Oct 12 19:20:29 2010   Above message repeated 1 times
[INFO]   Tue Oct 12 19:20:28 2010   Blocked incoming TCP connection request from 208.54.4.58:16714 to 66.91.*.***:80
[INFO]   Tue Oct 12 19:20:26 2010   Blocked incoming TCP connection request from 208.54.4.58:16107 to 66.91.*.***:443
[INFO]   Tue Oct 12 19:20:25 2010   Blocked incoming TCP connection request from 208.54.4.58:16714 to 66.91.*.***:80
[INFO]   Tue Oct 12 19:20:23 2010   Blocked incoming TCP connection request from 208.54.4.58:16107 to 66.91.*.***:443


I have this setup:

Priority   Time   Message
[INFO]   Tue Oct 12 19:21:54 2010   Blocked incoming UDP packet from 70.42.62.252:5062 to 66.91.*.***:8146
[INFO]   Tue Oct 12 19:21:29 2010   Blocked incoming TCP connection request from 98.232.51.190:50186 to 66.91.*.***:443
[INFO]   Tue Oct 12 19:21:23 2010   Above message repeated 1 times
[INFO]   Tue Oct 12 19:21:20 2010   Blocked incoming TCP connection request from 208.54.4.58:32186 to 66.91.*.***:443
[INFO]   Tue Oct 12 19:21:20 2010   Blocked incoming TCP connection request from 98.232.51.190:50186 to 66.91.*.***:443
[INFO]   Tue Oct 12 19:21:09 2010   Blocked incoming TCP connection request from 76.30.77.102:53533 to 66.91.*.***:443
[INFO]   Tue Oct 12 19:21:08 2010   Blocked incoming UDP packet from 99.175.211.20:57195 to 66.91.*.***:56136
[INFO]   Tue Oct 12 19:21:03 2010   Blocked incoming TCP connection request from 76.30.77.102:53533 to 66.91.*.***:443
[INFO]   Tue Oct 12 19:21:00 2010   Blocked incoming UDP packet from 99.175.211.20:57195 to 66.91.*.***:56136
[INFO]   Tue Oct 12 19:21:00 2010   Blocked incoming TCP connection request from 76.30.77.102:53533 to 66.91.*.***:443
[INFO]   Tue Oct 12 19:20:56 2010   Blocked incoming UDP packet from 112.207.58.74:1095 to 66.91.*.***:56131
[INFO]   Tue Oct 12 19:20:56 2010   Blocked incoming TCP connection request from 208.54.4.58:22204 to 66.91.*.***:443
[INFO]   Tue Oct 12 19:20:50 2010   Blocked incoming UDP packet from 112.207.58.74:1095 to 66.91.*.***:56131
[INFO]   Tue Oct 12 19:20:46 2010   Blocked incoming TCP connection request from 208.54.4.58:22807 to 66.91.*.***:80
[INFO]   Tue Oct 12 19:20:44 2010   Blocked incoming TCP connection request from 208.54.4.58:22204 to 66.91.*.***:443
[INFO]   Tue Oct 12 19:20:42 2010   Blocked incoming TCP packet from 94.254.28.197:57313 to 66.91.*.***:57887 as RST:ACK received but there is no active connection
[INFO]   Tue Oct 12 19:20:38 2010   Blocked incoming TCP connection request from 208.54.4.58:16107 to 66.91.*.***:443
[INFO]   Tue Oct 12 19:20:38 2010   Blocked incoming TCP packet from 116.15.7.43:2737 to 66.91.*.***:57887 as RST:ACK received but there is no active connection
[INFO]   Tue Oct 12 19:20:35 2010   Blocked incoming TCP connection request from 208.54.4.58:16107 to 66.91.*.***:443
[INFO]   Tue Oct 12 19:20:34 2010   Blocked incoming TCP connection request from 208.54.4.74:29752 to 66.91.*.***:80
[INFO]   Tue Oct 12 19:20:32 2010   Blocked incoming TCP connection request from 208.54.4.58:16107 to 66.91.*.***:443
[INFO]   Tue Oct 12 19:20:29 2010   Above message repeated 1 times
[INFO]   Tue Oct 12 19:20:28 2010   Blocked incoming TCP connection request from 208.54.4.58:16714 to 66.91.*.***:80
[INFO]   Tue Oct 12 19:20:26 2010   Blocked incoming TCP connection request from 208.54.4.58:16107 to 66.91.*.***:443
[INFO]   Tue Oct 12 19:20:25 2010   Blocked incoming TCP connection request from 208.54.4.58:16714 to 66.91.*.***:80
[INFO]   Tue Oct 12 19:20:23 2010   Blocked incoming TCP connection request from 208.54.4.58:16107 to 66.91.*.***:443

GAMING:
Enabled     Name     IP Address     TCP Ports     UDP Ports     Schedule     Inbound Filter 
1 true    Xbox Live    192.168.0. **   3074    88, 3074    Always    Allow All    
1 true    World of Warcraft    192.168.0. **   3724, 6112, 6881-6999       Always    Allow All    
1 true    TeamSpeak    192.168.0.**      8767    Always    Allow All    
1 true    Steam    192.168.0.199    27030-27039    1200, 27000-27015    Always    Allow All    
1 true    Starcraft    192.168.0.**    6112-6119, 4000    6112-6119    Always    Allow All    
1 true    Global Agenda    192.168.0.**    9000,9001    9002-9999    Always    Allow All    

GAME FUEL:

   Name     Priority     Local IP Range     Remote IP Range     Protocol / Ports           
   xBox    2    192.168.0.**- 192.168.0.** 0.0.0.0 - 255.255.255.255
   Both
0 / 65535
0 / 65535
   PC    1    192.168.0.**- 192.168.0.** 0.0.0.0 - 255.255.255.255
   TCP
0 / 65535
0 / 65535



Logged

Jimbo2552

  • Level 1 Member
  • *
  • Posts: 5
Re: Anyone help? Pls review log
« Reply #8 on: October 12, 2010, 10:30:45 PM »

NAT ENDPOINT FILTERING

Both set to Endpoint Independent

But I think I may have a UPnP issue with my router?  This seems non-standard, and I only have a PC, PS3, and Xbox 360 hooked up to the router, and intermittently an iphone and laptop.  But typically only one device is using the router at a time anyways... what do you think is going on?
« Last Edit: October 12, 2010, 10:40:38 PM by Jimbo2552 »
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Anyone help? Pls review log
« Reply #9 on: October 12, 2010, 11:36:40 PM »

Need to remove the XBL from gaming, it's not needed as Gamefuel handles that for your console, unless your doing XBL on a PC for gaming then your fine.
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

Reinvented

  • Level 4 Member
  • ****
  • Posts: 437
Re: Anyone help? Pls review log
« Reply #10 on: October 14, 2010, 01:39:06 AM »

Do you understand how the priorities work at all?  128 is normal priority.  Setting it for 1 or 2 can cause error transmission and definitely latency issues.  So, if you still are confused, let me explain.

1 is the highest priority you can set it for.  128 is normal priority, and 255 is the lowest.  Optimally, if you want things to have a slightly higher priority than normal, then set it for like 100 or something.  Ideally, you are probably starving your connection and causing retransmit errors for prioritizing stuff.  Hence why you get the lag that you do. 
Logged