Dear Developers, I’m sorry bothering you but I don't know personally 
the clever Dev who patched the Linksys WRTP54G 3.1.27 
firmware.http://oldwiki.openwrt.org/attachments/OpenWrtDocs(2f)Hardware(2f)Linksys(2f)WRTP54G/wrt-11.1.1-r070720-3.1.27.ETSI-r070720-aguirre-r080119.imgI'm
 sure there is a wrong set variable (ip_conntrack_tcp_timeout_established) in 
this (and in the original one too) firmware.My router begins dropping 
connections in about every 12 hours with “ip connection table full“ 
message. I know the cause is “heavy” P2P traffic but I would say 
the traffic is moderate, the firmware setting is faulty.I read on 
http://www.dd-wrt.com/wiki/index.php/Router_Slowdownthat the variables should 
be set about to:echo '2048' > 
/proc/sys/net/ipv4/netfilter/ip_conntrack_maxecho '600' > 
/proc/sys/net/ipv4/netfilter/ip_conntrack_generic_timeoutecho '30' > 
/proc/sys/net/ipv4/netfilter/ip_conntrack_icmp_timeoutecho '10&#
 39; > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_closeecho 
'120' > 
/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_close_waitecho 
'120' > 
/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_establishedecho 
'60' > 
/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_syn_sentecho 
'120' > 
/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_syn_recvecho 
'120' > 
/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_fin_waitecho '10' 
> /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_time_waitecho 
'60' > 
/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_last_ackecho '60' 
> /proc/sys/net/ipv4/netfilter/ip_conntrack_udp_timeoutecho '60' > 
/proc/sys/net/ipv4/netfilter/ip_conntrack_udp_timeout_stream instead of this 
the defaults are:cat 
/proc/sys/net/ipv4/netfilter/ip_conntrack_generic_timeout600cat 
/proc/sys/net/ipv4/netfilter/ip_conntrack_icmp_timeout30cat 
/proc/sys/net/ipv4/netfil
 ter/ip_conntrack_tcp_timeout_close10cat 
/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_close_wait120cat 
/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_established86400cat 
/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_syn_sent30cat 
/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_syn_recv60cat 
/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_fin_wait120cat 
/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_time_wait30cat 
/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_last_ack30cat 
/proc/sys/net/ipv4/netfilter/ip_conntrack_udp_timeout90cat 
/proc/sys/net/ipv4/netfilter/ip_conntrack_udp_timeout_stream180cat 
/proc/sys/net/ipv4/netfilter/ip_conntrack_max1024cat 
/proc/sys/net/ipv4/netfilter/ip_conntrack_flush1 I think cat 
/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_established86400 sec is 
insane. I could not find any solution to write the right values to the nvram. 
(No nvram commit command!)Could you give me any advise how to modi
 fy the default values?Could you possibly patch 
wrt-11.1.1-r070720-3.1.27.ETSI-r070720-aguirre-r080119.img again? Thank You, 
Gabor
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Reply via email to