From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jordan Russell Subject: Re: ICMP packets associated with NAT connections sent out wrong interface? Date: Thu, 05 Jul 2007 19:50:52 -0500 Message-ID: <468D91EC.5090103@quo.to> References: <468C86C9.7050204@quo.to> <200707051117.l65BHBA6013655@toshiba.co.jp> <468CE260.2040500@trash.net> <200707060014.l660EMSv000026@toshiba.co.jp> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200707060014.l660EMSv000026@toshiba.co.jp> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: netfilter-devel-bounces@lists.netfilter.org Errors-To: netfilter-devel-bounces@lists.netfilter.org Content-Type: text/plain; charset="us-ascii" To: Yasuyuki KOZAKAI Cc: netfilter-devel@lists.netfilter.org, netfilter@lists.netfilter.org, kaber@trash.net Yasuyuki KOZAKAI wrote: > Jordan, is there the message "nf_conntrack: table full, dropping packet" > in your log ? I've heard that BitTorrent creates huge connections. No; there are no messages from the kernel other than "nf_ct_icmp: bad HW ICMP checksum" and "[packet out wrong interface]" (my LOG rule). Note that my LOG rule isn't only triggered when using BitTorrent. It's hit during normal web browsing from the client machines too (i.e. outbound port 80 through my MASQUERADE rule), just not nearly as often. -- Jordan Russell