Strange Framentation behaviour
Dear Oleg,
first of all let me thank you for your great work :D
I run into some trouble, when I tried to connect a netgear wg500v2 wlan card with the wg-500g with your 1.9.2.7 CR6b Firmware.
I watched the behaviour that the card connects well and a first transmission of data from a website was succesfull. But after a short time (a minute or two) the transmission went down and no more packets could be received.
After some troubleshooting I found that the problem comes from the packet size / mtu settings of the card. The default was set to 3000. When I change it to 1490 everything went well.
I am no IP-expert, but I wonder if there is something wrong with the fragmentation handling in the firmware. I would have expect, that the router would fragment the respond packets, even if the default mtu settings form the netgear card are nonsense.
Fixed in 2.4.21-pre5 and later.
Just a quick tought. Are there any llimitations to upgrade kernel from 2.4.20 to somewhat higher (eg 2.4.31)
I have thist annoying messages:
Code:
KERNEL: assertion (newsk->state != TCP_SYN_RECV) failed at tcp.c(2225)
KERNEL: assertion ((1<<sk2->state)&(TCPF_ESTABLISHED|TCPF_CLOSE_WAIT|TCPF_CLOSE)) failed at af_inet.c(689)
KERNEL: assertion (newsk->state != TCP_SYN_RECV) failed at tcp.c(2225)
KERNEL: assertion ((1<<sk2->state)&(TCPF_ESTABLISHED|TCPF_CLOSE_WAIT|TCPF_CLOSE)) failed at af_inet.c(689)
KERNEL: assertion (newsk->state != TCP_SYN_RECV) failed at tcp.c(2225)
KERNEL: assertion ((1<<sk2->state)&(TCPF_ESTABLISHED|TCPF_CLOSE_WAIT|TCPF_CLOSE)) failed at af_inet.c(689)
KERNEL: assertion (newsk->state != TCP_SYN_RECV) failed at tcp.c(2225)
KERNEL: assertion ((1<<sk2->state)&(TCPF_ESTABLISHED|TCPF_CLOSE_WAIT|TCPF_CLOSE)) failed at af_inet.c(689)
KERNEL: assertion (newsk->state != TCP_SYN_RECV) failed at tcp.c(2225)
KERNEL: assertion ((1<<sk2->state)&(TCPF_ESTABLISHED|TCPF_CLOSE_WAIT|TCPF_CLOSE)) failed at af_inet.c(689)
Which is fixed in 2.4.21-pre5 and later.
Another annoying thing which is hopefuly fixed in latest kernels is USB timeout issue on busy server with gift and torrent with load rarely under 1. But for this I've found solution (Revoltec case and WD3200 disk).
Now if you skipped bla-bla from above. The question is? What are the issues when upgrading to other kernel? Are kernel pathes needed for WL500GX? Does stock kernel suffice? Only .config needed, lzma patch, usb patch ...?
I've compiled Oleg source and unslug tree w/o problem. But bricking router with naive replacement with other kernel bothers me.
stupid-ftp filesize limit
Hi Oleg,
Thanks for your answer. I will try to upload VSFTP, I read on another site how to implement this, so I will give it a try. Thanks for your support and keep up the good work.
BJ
MAC filter x ping respond & WAN web access
Hi,
I have firmware v1.9.2.7 CR6b in my Asus WL-500b and have little problem. When I enable MAC filter in Internet firewall settings to accept mode and ping respond from WAN, web access from WAN is enabled too, then ping respond from WAN and web access from WAN does not work.
MAC filter is determined for LAN. Why have a effect for WAN too?
Thank's for answer.