From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: netfilter@vger.kernel.org
Subject: Re: Forwarding packets over the same LAN
Date: Wed, 15 Jul 2009 09:32:54 +0200 [thread overview]
Message-ID: <4A5D8626.6060002@plouf.fr.eu.org> (raw)
In-Reply-To: <e1ba8dde0907141201i5647546r78c2a66e24cad18f@mail.gmail.com>
Simion Onea a écrit :
>
> Maybe I should examine more carefully the INPUT and FORWARD chains of
> the filter table. They are configured to allow inbound traffic to port
> 10025 and to allow forwarding to port 25. Are there any other
> requirements?
The INPUT chain is only for local delivery, forwarded traffic does not
go through it. So you do not need to accept inbound traffic to port
10025 in the INPUT chain. You need to accept the return traffic in the
FORWARD chain.
> Is there any means to "debug" or to "see" how a packet traverses the
> chains and tables?
If the TRACE target is not available, you can insert rules with the LOG
target at the beginning of each table/chain. You can also use a packet
sniffer such as tcpdump or wireshark to watch the traffic at each interface.
next prev parent reply other threads:[~2009-07-15 7:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 14:00 Forwarding packets over the same LAN Simion Onea
2009-07-13 14:14 ` Thomas Jacob
2009-07-14 7:58 ` Simion Onea
2009-07-14 9:25 ` Mart Frauenlob
2009-07-14 12:20 ` Simion Onea
2009-07-14 12:40 ` Mart Frauenlob
2009-07-14 12:30 ` Thomas Jacob
2009-07-14 12:27 ` Thomas Jacob
2009-07-14 13:06 ` Simion Onea
2009-07-15 7:38 ` Simion Onea
2009-07-14 15:33 ` Pascal Hambourg
2009-07-14 18:50 ` Simion Onea
2009-07-14 15:34 ` Thomas Jacob
2009-07-14 19:01 ` Simion Onea
2009-07-14 20:36 ` Vincent Bernat
2009-07-15 7:32 ` Pascal Hambourg [this message]
2009-07-15 7:40 ` Simion Onea
2009-07-15 20:12 ` Mike Williams
2009-07-16 5:59 ` Simion Onea
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=4A5D8626.6060002@plouf.fr.eu.org \
--to=pascal.mail@plouf.fr.eu.org \
--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 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.