solucion Received fragment (router linsys)

borja75

soN1

algunos routers marca linksys tienen problemas de un poco mas de ping de lo normal y tb aparere un error en console received fragment out of order 1/4,2/4, etc, decir q es un tipo de incompatibilidad con la marca de router q ya he dixo y q estan trabajando entre ambas compañias para solucionarlo, de todas formas si kereis intentar solucionarlo por vuestra parte aki os lo dejo aunk esta en ingles si teneis 1traductor automatico pues mejor:

Received fragment out of order:

I believe I have found the solution to the problem for users of the Linksys Router that receive the
"Received fragment out of order" error in console...

1) Upgrade to the latest firmware, being very careful to note the exact version # of the router. Ignore other suggestions to downgrade firmware, as this will make you vulnerable to known security issues.

2) Log on to the router page, and then go to the "Filters" page.

3) From Linksys Website regardig MTU size:
To find the proper MTU Size, you’ll have to do a special ping of the destination you’re trying to go to. A destination could be another computer, or a URL. (I recommend to input the server IP that you get the packet fragment error on - Use the Linksys outbound log to see the last Counter-Strike server you connected to on)

  1. Click on the Start button, then select the Run option.

  2. In the “Open” field type in command (If you’re using Windows 2K/NT/XP use CMD instead).

  3. Once the window opens, you’ll need to do a special ping. It should be formatted:

ping /?
Example: (substitute the server IP x.x.x.x)
ping x.x.x.x –f –l 1472 result = fragmented packet

ping yahoo.com –f –l 1462 result = fragmented packet

ping yahoo.com –f –l 1452 result = reply

You should always start at 1472 and work your way down by 10 each time. Once you get a reply, go up by 2 until you get a fragmented packet. Take that value and add 28 to the value to account for the

various TCP/IP headers. For example, lets say that 1452 was the proper value, the actual MTU size

would be 1480, which is the optimum for the network we’re working with.

  1. Once you’ve found the optimum MTU size open up your browser, usually Internet Explorer, which

is located on your desktop (Or on the Start menu in Windows XP).

  1. Once Internet Explorer has opened input http://192.168.1.1/Filters.htm into the “Address” bar.

  2. You will be prompted for a User Name and Password. Leave the User Name blank and input admin
    as the password then click OK. (Use the password that you chaged it to - if your password is default, then CHANGE IT!)

  3. Once you’ve done this you should find your self on the Filters tab. Scroll down to the bottom and look for “MTU”. Enable the option and input the optimum value you got earlier. So for our example this would be 1480. After that value has been inputted click Apply then Continue and you’re done.

4) Log back on to a CS server, and then go to console, and look for the packet error. If it continues, disconnect from the server, Alt-Tab back to the Linksys, and decrease the MTU by 100 each time until there are no longer packet fragment errors.

5) There is absolutely no need to open up any UDP ports to get this working properly. Only open up the UDP ports if you are hosting a server, and need inbound connections on those ports.

6) Also, after upgrading the firmware, realize that with DHCP enabled, that the port forwarding options change... So, if you need static routes, you must disable DHCP, and assign static IP's to your client computers.

If you get too low, then you will eventually get an error:

"Disconnect: Buffer overflow in net message.
Host_EndGame: Buffer overflow in net message"

and other errors I have seen as a result of messing with MTU size:

"Netchannel: failed reading message svc_GameEvent from 216.86.155.99:27015.
Netchannel: failed reading message svc_GameEvent from 216.86.155.99:27015.

Host_Error: String tables must be powers of two in size!, 0 is not a power of 2"

This worked semi-reliably for me...

Perhaps this will help someone to come out with a permafix...

ojala se os solucione a los q teneis este router, saludos gl