/* HINT: Search archives @ http://www.indyramp.com/masq/ before posting! /* ALSO: Don't quote this header. It makes you look lame :-) */
Julian Eduardo de Anquin <[EMAIL PROTECTED]> wrote: > > cat /proc/net/ip_conntrack | wc -l gives me 145 > and cat /proc/sys/net/ipv4/ip_conntrack_max 32720 Do you mean that those are the results when you checked just now? Or that this is what you saw during a time when some of your clients could not reach the net? It is important to take these measurements during a time when the net is not reachable. > what is the max ip_conntrack_max can i use? The ip_conntrack_max is NOT the maximum the firewall has ever seen.. It is actually the absolute maximum allowed. You should not need to tune it, as your system apparently has a large amount of memory, and the kernel has already set this to a huge value. As for your problem, you might still find something in the system logs, that might indicate the nature of the problem. Especially if you know what time an outage occurred, you can try to match it up to a time in the logs. -- [EMAIL PROTECTED] (Fuzzy Fox) || "Good judgment comes from experience. sometimes known as David DeSimone || Experience comes from bad judgment." _______________________________________________ Masq maillist - [EMAIL PROTECTED] Admin requests can be handled at http://www.indyramp.com/masq-list/ -- THIS INCLUDES UNSUBSCRIBING! or email to [EMAIL PROTECTED] PLEASE read the HOWTO and search the archives before posting. You can start your search at http://www.indyramp.com/masq/ Please keep general linux/unix/pc/internet questions off the list.
