Connection problem!

[Castanheiro]

I have an adsl connection (pppoe), i'm using a ethernet modem connected to my wl500g router. The router has the firmware v.1.7.5.6 CR3 [Oleg] . My connection drops from time to time, sometimes every hour and i'm getting this in the router log:

May 20 22:14:48 WL500g daemon.err pppoe[473]: Bad TCP checksum b595
May 20 22:19:03 WL500g daemon.err pppoe[473]: Bad TCP checksum 3d95
May 20 22:20:14 WL500g daemon.err pppoe[473]: Bad TCP checksum b595
May 20 22:28:33 WL500g daemon.err pppoe[473]: Bad TCP checksum b095
May 20 22:28:38 WL500g daemon.err pppoe[473]: Bad TCP checksum b095
May 21 08:55:20 WL500g daemon.err pppoe[473]: Bad TCP checksum 645e
May 21 10:08:45 WL500g daemon.err pppoe[473]: Bad TCP checksum 866f
May 21 11:39:36 WL500g daemon.err pppoe[473]: Bad TCP checksum 25a5
May 21 16:38:27 WL500g daemon.notice pppd[310]: Serial link appears to be
disconnected.
May 21 16:38:27 WL500g daemon.notice pppd[310]: Connection terminated.
May 21 16:38:27 WL500g daemon.err pppoe[473]: read (asyncReadFromPPP): Session
6474: Input/output error
May 21 17:38:27 WL500g user.notice PPPoE: disconnected
May 21 16:38:37 WL500g daemon.notice pppd[310]: Connect: ppp0 <--> /dev/pts/0
May 21 16:38:37 WL500g daemon.err pppoe[10223]: retryloopindex=1
May 21 16:38:41 WL500g daemon.warn pppd[310]: Local IP address changed to
80.172.32.235
May 21 17:38:41 WL500g user.notice PPPoE: connect to server since boot up for
69203 seconds
May 21 17:57:05 WL500g daemon.err pppoe[10223]: Bad TCP checksum bfff
May 21 20:50:31 WL500g daemon.notice pppd[310]: Serial link appears to be
disconnected.
May 21 20:50:32 WL500g daemon.notice pppd[310]: Connection terminated.
May 21 20:50:32 WL500g daemon.err pppoe[10223]: read (asyncReadFromPPP):
Session 6055: Input/output error
May 21 21:50:32 WL500g user.notice PPPoE: disconnected
May 21 20:50:42 WL500g daemon.notice pppd[310]: Connect: ppp0 <--> /dev/pts/0
May 21 20:50:42 WL500g daemon.err pppoe[12413]: retryloopindex=1
May 21 20:50:43 WL500g daemon.warn pppd[310]: Local IP address changed to
80.172.32.183
May 21 21:50:43 WL500g user.notice PPPoE: connect to server since boot up for
84275 seconds
May 21 22:28:04 WL500g user.emerg NTP client: time is synchronized to
131.107.1.10
May 21 22:10:32 WL500g daemon.err pppoe[12413]: Bad TCP checksum 6f0c
May 21 23:18:59 WL500g daemon.err pppoe[12413]: Bad TCP checksum bcea
May 21 23:20:13 WL500g daemon.err pppoe[12413]: Bad TCP checksum a3b9
May 21 23:54:30 WL500g daemon.err pppoe[12413]: Bad TCP checksum 10db
May 21 23:57:12 WL500g daemon.err pppoe[12413]: Bad TCP checksum eceb
May 22 00:03:23 WL500g daemon.err pppoe[12413]: Bad TCP checksum 8ece
May 22 00:03:32 WL500g daemon.err pppoe[12413]: Bad TCP checksum 2dbf


What could be the problem? The modem stays syncronized even when the connection drops.

Thanks.

[dizz]

yeah

i have the same problem with CR3!

i had the "Bad TCP checksum" with CR2, too.
but not all the "Connection terminated" messages..
this seem to bee a CR3 thing.

the original versions didn´t show this error!

greetinx

[Castanheiro]

Today i tried my modem plugged to my pc, no router, and i didn't had a single connection drop. Then i tried the router without the firewall, and so far no drops.. i tested with wlan+lan access... I really don't know what is causing the drops

[Castanheiro]

I already know what triggers the connection drops, today i hadn' t a single drop until i started aMule and Azureus... 10 minutes later it dropped.... What could be the problem?


Log:
May 24 17:10:46 WL500g daemon.notice pppd[311]: Connection terminated.
May 24 17:10:46 WL500g daemon.err pppoe[579]: read (asyncReadFromPPP): Session 1091: Input/output error
May 24 17:10:56 WL500g daemon.notice pppd[311]: Connect: ppp0 <--> /dev/pts/0
May 24 17:10:56 WL500g daemon.err pppoe[5002]: retryloopindex=1

[Castanheiro]

After many tests, i finally found the source of my connection problems. The problem is triggered with the use of aMule and azureus at the same time, so i guess that it has something to do with the number of connections. Now the good part... this only happens with the 1.7.5.6 version of the firmware (with Oleg's version also). I'm now using the 1.6.5.3 version and it's stable as a rock! What can i do the help solving the problem?