From: Jorge Davila <davila@nicaraguaopensource.com>
To: Paulo Andre <pandre@darkstar.nom.za>
Cc: netfilter <netfilter@lists.netfilter.org>
Subject: Re: FORWARD packet problem
Date: Wed, 19 Jul 2006 11:19:38 -0600 [thread overview]
Message-ID: <1153329578.9157.2.camel@localhost.localdomain> (raw)
In-Reply-To: <44BE4BCE.8060509@darkstar.nom.za>
There is no so much information to get an answer.
What is your routing table information?
What are your firewall rules?
I'm guessing a routing problem or missed firewall rules.
Jorge.
El mié, 19-07-2006 a las 17:12 +0200, Paulo Andre escribió:
> 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?
>
> Paulo
>
--
Jorge Isaac Davila Lopez
Nicaragua Open Source
+505 808 2478
davila@nicaraguaopensource.com
next prev parent reply other threads:[~2006-07-19 17:19 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 [this message]
2006-07-19 19:09 ` Pascal Hambourg
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=1153329578.9157.2.camel@localhost.localdomain \
--to=davila@nicaraguaopensource.com \
--cc=netfilter@lists.netfilter.org \
--cc=pandre@darkstar.nom.za \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.