From: Jim Doble <jim.doble@tavve.com>
To: netfilter@lists.netfilter.org
Subject: Local Routing without IP Aliasing
Date: Mon, 17 Jul 2006 14:12:54 -0400 [thread overview]
Message-ID: <44BBD326.7010506@tavve.com> (raw)
I am trying to configure a Linux host to treat a potentially large range
of IP addresses as "local", without having to define these addresses as
aliases. When packets (UDP or TCP) arrive addressed to any of these
addresses, I need these packets to be delivered locally (that is,
treated as if they were addressed to the IP address of my Linux host,
even though they were not), without losing knowledge of the original
destination address and port.
I am defining static routes in any other hosts that need to communicate
with these addresses, in order to ensure that packets addressed to these
addresses will be sent to my Linux host. The problem I am having is that
these packets are being discarded in my Linux host, unless I redirect
them to the address associated with my Linux host, in which case the
original destination address is lost (except in the case of TCP, where
there is a mechanism to recover it via getsockopt).
I would prefer to find a way to do this using iptables or routing
configuration, or via a netfilter extension, if that is possible. Any
advice would be appreciated.
Jim Doble
Tavve Software Company
next reply other threads:[~2006-07-17 18:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-17 18:12 Jim Doble [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-17 20:48 Local Routing without IP Aliasing Jim Doble
2006-07-17 23:31 ` Pascal Hambourg
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=44BBD326.7010506@tavve.com \
--to=jim.doble@tavve.com \
--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 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.