From: Michele Petrazzo - Unipex srl <michele.petrazzo@unipex.it>
To: netfilter@vger.kernel.org
Cc: Bernhard Bock <bernhard@bock.nu>
Subject: Re: More ethernet port same ip address
Date: Sat, 19 Jul 2008 15:46:09 +0200 [thread overview]
Message-ID: <4881F021.3080101@unipex.it> (raw)
In-Reply-To: <4881A371.3060803@bock.nu>
Bernhard Bock wrote:
> Hi Michele,
>
Hi!
> My proposal has nothing to do with netfilter, but you may have a look
> into "Proxy ARP".
>
I have already tried the proxy_arp trickle, but doesn't help.
> Basically you give each interface the same IP address, put in host
> routes based on interfaces (route add -host 172.16.0.3 dev ethx) and
> enable proxy_arp in /proc/sys/net/ipv4/conf/ethx/proxy_arp. This
> should do the trick.
The problem it's that I don't know who (which ip) wants to talk on which
port...
Starting from this problem I thought to mark the packets for say "you
(packet) with that mark, go out through that port" with iptables, mark
and ip rules
Thanks,
Michele
next prev parent reply other threads:[~2008-07-19 13:46 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 [this message]
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
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=4881F021.3080101@unipex.it \
--to=michele.petrazzo@unipex.it \
--cc=bernhard@bock.nu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox