Hi, On Sun, 28 Jan 2007 at 22:51 +0100, Klaus Reimer wrote: > Waldemar Brodkorb wrote: > > There is no special NAT module for bittorrent protocol. Are you > > loaded any traffic shaping modules? (kmod-sched package) > > kmod-sched is compiled into the kernel because I had the plan to play > with it some day. But up to now I haven't done anything with it. Is this > module already doing something without any configuration? Maybe I should > try again without this module?
All kernel modules from kmod-sched are automatically loaded on bootup. I am really unsure if this is related, but at least it is a chance for you to verify if the problem persist without these modules loaded. Are you using a bridge between WLAN and LAN? I try to find out differences to one other router running fine since more than 3 months.. [EMAIL PROTECTED]:~$ uptime 07:53:40 up 92 days, 11:11, load average: 0.01, 0.00, 0.00 And it is doing DNS/DHCP/Wireless/Firewall/PPPoE/IPv6 for 5-8 people. (no bridging, no kmod-sched) > > Can you try to install rmeote syslog and may be net-snmp to analyze > > the problem further? > > This is the next thing I try. Today I tried watching the output of "cat > /proc/net/ip_conntrack | wc -l". I ran this command together with a > timestamp-adder every five seconds and here is the last minute before > the router stopped working: > > 2007-01-28 22:29:47.580553500 173 > 2007-01-28 22:29:52.736039500 172 > 2007-01-28 22:29:57.872360500 177 > 2007-01-28 22:30:03.036043500 183 > 2007-01-28 22:30:08.193941500 184 > 2007-01-28 22:30:13.336628500 180 > 2007-01-28 22:30:18.465421500 177 > 2007-01-28 22:30:23.617665500 174 > 2007-01-28 22:30:28.776923500 164 > 2007-01-28 22:30:33.929545500 159 > 2007-01-28 22:30:39.054163500 168 > 2007-01-28 22:30:44.186152500 163 > > So it doesn't look like this is a problem. Right. I do not remember any changes between OpenWrt and FreeWRT in this area. May be someone can search in the OpenWrt forums if anybody has problems like these on OpenWrt. We have a newer kernel, may be some stuff has changed in the traffic shaping modules. There is one ugly workaround added to Linux 2.4.x to get wl.o binary running, may be this workaround is the problem... bye Waldemar -- don't open your wrt, free it http://www.freewrt.org _______________________________________________ freewrt-users mailing list [email protected] https://www.freewrt.org/lists/listinfo/freewrt-users
