From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: Problem with FORWARD hook
Date: Tue, 11 Nov 2003 22:12:46 +0000 [thread overview]
Message-ID: <200311112212.hABMCmj17939@agate.rockstone.co.uk> (raw)
In-Reply-To: <Pine.SOL.4.20.0311111655550.29271-100000@csa.bu.edu>
On Tuesday 11 November 2003 9:59 pm, Leonid Veytser wrote:
> When I dump the output of all the packets traveling thru my machine, I
> notice that none go thru FORWARD hook.
There's no other way packets are going to get routed through your machine
except by passing through the FORWARD chain.
> So, I tried to make a packet have
> to go thru the FORWARD hook (ie by changing the packet dest at PREROUTING
> hook), but the packet never goes to the FORWARD hook, but disappears.
Show us an example of your rules so we can see what you are trying to do.
> Can there be some incorrect configuration on my machine that would cause
> it not to be able to forward packets?
There are many ways of (mis)configuring a machine so that it doesn't forward
packets. Some people might say this is a highly secure router :)
Antony.
--
Your email has been returned due to insufficient voltage.
Please reply to the list;
please don't CC me.
next prev parent reply other threads:[~2003-11-11 22:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-11 19:13 NF_STOLEN effect on TCP A K A
2003-11-11 21:59 ` Problem with FORWARD hook Leonid Veytser
2003-11-11 22:06 ` Stuart J. Browne
2003-11-11 22:12 ` Antony Stone [this message]
2003-11-11 22:55 ` NF_QUEUE target and ip_queue.c Leonid Veytser
2003-11-21 20:15 ` Checksumming Issues Leonid Veytser
2003-11-21 20:27 ` Antony Stone
2003-11-12 0:40 ` Problem with FORWARD hook Leonid Veytser
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=200311112212.hABMCmj17939@agate.rockstone.co.uk \
--to=antony@soft-solutions.co.uk \
--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