From mboxrd@z Thu Jan 1 00:00:00 1970 From: jamal Subject: Re: [tproxy,regression] tproxy broken in 2.6.32 Date: Sat, 28 Nov 2009 14:26:08 -0500 Message-ID: <1259436368.3864.43.camel@bigi> References: <1259137434.9191.3.camel@nienna.balabit> <1259310417.3809.5.camel@nienna.balabit> <1259337932.3299.3.camel@bigi> <20091128151515.GA20476@sch.bme.hu> <1259423157.3864.9.camel@bigi> <20091128185019.GA12264@sch.bme.hu> Reply-To: hadi@cyberus.ca Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: KOVACS Krisztian , Andreas Schultz , tproxy@lists.balabit.hu, netdev@vger.kernel.org To: KOVACS Krisztian Return-path: Received: from mail-qy0-f194.google.com ([209.85.221.194]:49428 "EHLO mail-qy0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752120AbZK1T0E (ORCPT ); Sat, 28 Nov 2009 14:26:04 -0500 Received: by qyk32 with SMTP id 32so993195qyk.4 for ; Sat, 28 Nov 2009 11:26:10 -0800 (PST) In-Reply-To: <20091128185019.GA12264@sch.bme.hu> Sender: netdev-owner@vger.kernel.org List-ID: On Sat, 2009-11-28 at 19:50 +0100, KOVACS Krisztian wrote: > Well, the only route we're interested in is the following (see > Documentation/networking/tproxy.txt for the details): > > ip route add local 0.0.0.0/0 dev lo table 100 > ip route add unicast 0.0.0.0/0 dev lo table 100 would work. > Adding a unicast route is not really an option, Can you explain this part? cheers, jamal