From: Mart Frauenlob <mart.frauenlob@chello.at>
To: Bruno de Paula Larini <bruno.larini@riosoft.com.br>,
"Anton Danilov CC: netfilter@vger.kernel.org Sender:
netfilter-owner@vger.kernel.org X-Mailing-List:
netfilter@vger.kernel.org" <littlesmilingcloud@gmail.com>
Cc: "netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Re: Losing connection between nat and filter tables
Date: Fri, 09 May 2014 23:32:51 +0200 [thread overview]
Message-ID: <536D4983.8040105@chello.at> (raw)
In-Reply-To: <536D3E84.5020102@riosoft.com.br>
On 09.05.2014 23:07, netfilter-owner@vger.kernel.org wrote:
> No deal yet. After inserting the new routing tables and rules it didn't
> really change anything.
> The eth2 doesn't have a gateway set in the config file, only eth1 have
> it. Plus, these two interfaces are in the same subnet and there's only
> one gateway on it (180.1.2.1).
>
> [root@firewall ~]# ip route show table T1
> default via 180.1.2.1 dev eth1
>
> [root@firewall ~]# ip route show table T2
> default via 180.1.2.1 dev eth2
>
> [root@firewall ~]# ip rule show
> 0: from all lookup local
> 10: from 180.1.2.11 lookup T1
> 20: from 180.1.2.12 lookup T2
> 32766: from all lookup main
> 32767: from all lookup default
>
> (I had to add the tables T1 and T2 in the file /etc/iproute2/rt_tables)
>
> Even so, I see it reach the PREROUTING chain in eth2 but it still
> disappears after that. Connections reaching in the eth1 still works.
>
> There's something else to try?
Check values of /proc/sys/net/ipv4/conf/*/rp_filter
and disable them.
To use the TRACE target just put a -j TRACE on the desired place.
next prev parent reply other threads:[~2014-05-09 21:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 14:56 Losing connection between nat and filter tables Bruno de Paula Larini
2014-05-09 15:43 ` Anton Danilov
2014-05-09 16:12 ` Bruno de Paula Larini
2014-05-09 16:48 ` Anton Danilov
2014-05-09 20:45 ` Bruno de Paula Larini
2014-05-09 21:32 ` Mart Frauenlob [this message]
2014-05-10 0:31 ` Bruno de Paula Larini
2014-05-10 17:21 ` Pascal Hambourg
2014-05-12 13:20 ` Bruno de Paula Larini
2014-05-12 22:40 ` Pascal Hambourg
2014-05-11 10:02 ` Mart Frauenlob
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=536D4983.8040105@chello.at \
--to=mart.frauenlob@chello.at \
--cc=bruno.larini@riosoft.com.br \
--cc=littlesmilingcloud@gmail.com \
--cc=netfilter@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).