From: David Madore <david+ml@madore.org>
To: netdev@vger.kernel.org
Cc: Lukas Tribus <luky-37@hotmail.com>
Subject: Re: assigning an entire subnet of addresses to an interface
Date: Sun, 3 Feb 2013 23:35:49 +0100 [thread overview]
Message-ID: <20130203223549.GA14927@achernar.madore.org> (raw)
In-Reply-To: <20130203220057.GA14363@achernar.madore.org>
On Sun, Feb 03, 2013 at 11:00:57PM +0100, David Madore wrote:
> This is indeed, interesting, and I'm glad you pointed out this
> possibility, because it had escaped my radar. (Note that there are
> two slightly different things, though: the TPROXY iptables/ip6tables
> target which redirects packets to a local socket, and the IP-level
> IP_TRANSPARENT socket option which allows a user application to bind
> to an arbitrary address. The latter is closer to what I was asking.)
Another related and interesting IP-level socket option is IP_FREEBIND.
I suppose the different between IP_FREEBIND and IP_TRANSPARENT is that
the former does not cause any routing changes, but the net effect is
that, after the "ip -6 route add local 2001:db8:f00f::/48 dev lo"
command that I had contemplated, binding with IP_FREEBIND does allow
the socket to obtain packets destined to an arbitrary address inside
the subnet. Without requiring administrator privileges (of course,
they are required to run the ip route command).
But I'd still be happier if there were some way that required
absolutely no modification on the userland side after a few
administrative commands to make the prefix available.
--
David A. Madore
( http://www.madore.org/~david/ )
prev parent reply other threads:[~2013-02-03 22:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-03 20:51 assigning an entire subnet of addresses to an interface David Madore
2013-02-03 21:45 ` Lukas Tribus
2013-02-03 22:00 ` David Madore
2013-02-03 22:35 ` David Madore [this message]
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=20130203223549.GA14927@achernar.madore.org \
--to=david+ml@madore.org \
--cc=luky-37@hotmail.com \
--cc=netdev@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