/* HINT: Search archives @ http://www.indyramp.com/masq/ before posting! /* ALSO: Don't quote this header. It makes you look lame :-) */
AJ Bostian <[EMAIL PROTECTED]> wrote: > > It seems to stop forwarding after about 30 minutes. The problem does > not go away if I simply flush the chains and reload the rules; I have > to do a full reboot. This sounds like a problem that used to come up under 2.2 with ipchains. If the clients continued to open lots of connections (especially using connectionless queries, such as DNS requests), it would fill up the masq table keeping track of all the NAT, and eventually it would runt out of room. The answer was to list the table out and see what traffic is filling the table (how ever that is done with iptables... I need to learn!), and then either somehow prevent the traffic from reaching the router, or reduce the amount of time that the entries remain in the table, allowing them to expire and let new entries come in. -- [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.
