public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Innocenti Maresin <qq@inCTV.ru>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: remapping IP addresses for inbound and outbound traffic
Date: Sun, 13 Aug 2006 06:02:17 +0000	[thread overview]
Message-ID: <44DEC069.85C6D3E3@inCTV.ru> (raw)
In-Reply-To: NBBBIHMOBLOHKCGIMJMDOEBFFMAA.g.tomassoni@libero.it

Giampaolo Tomassoni:
 
> I guess you can't do this, since a believe there is a single linux arp table.
> It is not per-interface.

It is a problem generally, but happily not in my case 
because at least one of my networks has this overlapping IP area behind a router. 
More precisely, one network almost entirely stands behind a router. 
I do not need any ARP for IPs those I want to remap. 

 
> If you had hosts with unique IPs on both nets, that would be another story:
> you could use some sort of VPN or Bridge functionality.
> You could also be able to avoid packets passing through the bridged/VPNed interfaces
> thanks to iptables.

May be I do not understand what means "some sort of VPN or Bridge functionality", 
but any solution requiring an extra soft on the client side would be inadequate 
and I will not take such proposals into account. 
My server must accept pure IP from both sides. 
I am not willing to set up packet forwarding, GRE, nor any another "advanced technique". 
Only one simple thing is required: to shift a block of IPs at one interface. 




-- 
qq~~~~\	
/ /\   \
\  /_/ /
 \____/

  reply	other threads:[~2006-08-13  7:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-12 15:09 Q: remapping IP addresses for inbound and outbound traffic Innocenti Maresin
2006-08-12 15:42 ` R: " Giampaolo Tomassoni
2006-08-13  6:02   ` Innocenti Maresin [this message]
2006-08-12 17:22 ` Q: " Jan Engelhardt
2006-08-13 15:17 ` 2.4 - net/ipv4/route.c/ip_route_output_slow() Innocenti Maresin
2006-08-14  0:00   ` David Miller
2006-08-29  8:07 ` Q: remapping IP addresses for inbound and outbound traffic 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=44DEC069.85C6D3E3@inCTV.ru \
    --to=qq@inctv.ru \
    --cc=linux-kernel@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