From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: More ethernet port same ip address
Date: Tue, 22 Jul 2008 10:06:44 -0500 [thread overview]
Message-ID: <4885F784.1050906@riverviewtech.net> (raw)
In-Reply-To: <38db14850807220603p15221841g4fcfb72a2d91ddf0@mail.gmail.com>
On 07/22/08 08:03, Anatoly Muliarski wrote:
> I have just now the next working configuration:
<snip>
> arp_proxy is set on.
> Also you need to set up forwarding:
> echo 1 > /proc/sys/net/ipv4/ip_forward
*nod*
> + I recommend to clear firewall rules for testing purpose:
> iptables -F
> iptables -P INPUT ACCEPT
> iptables -P OUTPUT ACCEPT
> iptables -P FORWARD ACCEPT
Based on experience (shooting my self in the foot) I *strongly*
recommend that you set the chain policies *BEFORE* flushing the table /
chains. Just think what will happen if the chain policy is DENY and you
are trying to do this via an SSH connection.
Grant. . . .
next prev parent reply other threads:[~2008-07-22 15:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-19 7:34 More ethernet port same ip address Michele Petrazzo - Unipex srl
2008-07-19 8:18 ` Bernhard Bock
2008-07-19 13:46 ` Michele Petrazzo - Unipex srl
2008-07-19 14:01 ` Leonardo Rodrigues Magalhães
2008-07-19 14:13 ` Jan Engelhardt
2008-07-19 15:14 ` Michele Petrazzo - Unipex srl
2008-07-19 15:42 ` Jan Engelhardt
2008-07-19 16:05 ` Michele Petrazzo - Unipex srl
2008-07-19 16:13 ` Jan Engelhardt
2008-07-19 16:17 ` Leonardo Rodrigues Magalhães
2008-07-19 16:34 ` Jan Engelhardt
2008-07-19 16:45 ` Leonardo Rodrigues Magalhães
2008-07-19 15:11 ` Michele Petrazzo - Unipex srl
2008-07-20 23:41 ` Grant Taylor
2008-07-21 7:00 ` Anatoly Muliarski
2008-07-21 14:08 ` Grant Taylor
2008-07-21 18:11 ` Michele Petrazzo - Unipex srl
2008-07-21 19:46 ` Grant Taylor
2008-07-22 13:03 ` Anatoly Muliarski
2008-07-22 15:06 ` Grant Taylor [this message]
2008-07-22 15:20 ` Jan Engelhardt
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=4885F784.1050906@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--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.