Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: netfilter <netfilter@lists.netfilter.org>
Subject: Re: FORWARD packet problem
Date: Wed, 19 Jul 2006 21:09:57 +0200	[thread overview]
Message-ID: <44BE8385.4080509@plouf.fr.eu.org> (raw)
In-Reply-To: <44BE4BCE.8060509@darkstar.nom.za>

Hello,

Paulo Andre a écrit :
> I have a multiple isp fw
> eth0 = int
> eth1 = default isp
> eth2 = sec isp
> 
> when I try and make a connection to and internal server via the eth2 , 
> the packet appears on the PREROUTING table, and then not on FORWARD , 
> anyone have any ideas?

I guess there is a default route via eth1.
If so, first check that /proc/sys/net/ipv4/conf/eth2/rp_filter=0 else 
the input routing, which takes place between PREROUTING and INPUT or 
FORWARD, may drop incoming IP packets on eth2 whose source address is 
not routed out via eth2 as a protection against IP spoofing.


  parent reply	other threads:[~2006-07-19 19:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-19 15:12 FORWARD packet problem Paulo Andre
2006-07-19 17:19 ` Jorge Davila
2006-07-19 19:09 ` Pascal Hambourg [this message]
2006-07-20 13:50   ` Paulo Andre
2006-07-20 15:46     ` Pascal Hambourg

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=44BE8385.4080509@plouf.fr.eu.org \
    --to=pascal.mail@plouf.fr.eu.org \
    --cc=netfilter@lists.netfilter.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