From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: "M. Buecher" <maddes+kernel@maddes.net>, netdev@vger.kernel.org
Cc: Michal Kubecek <mkubecek@suse.cz>,
Matthias May <matthias.may@neratec.com>,
Heiner Kallweit <hkallweit1@gmail.com>
Subject: Re: IP-Aliasing for IPv6?
Date: Mon, 20 May 2019 22:33:26 +0200 [thread overview]
Message-ID: <87pnocvpbd.fsf@toke.dk> (raw)
In-Reply-To: <d10e40ae062903f15e84c7e3890a0b40@maddes.net>
"M. Buecher" <maddes+kernel@maddes.net> writes:
> On 2019-05-15 11:26, Michal Kubecek wrote:
>> On Tue, May 14, 2019 at 08:49:12PM +0200, M. Buecher wrote:
>>> According to the documentation [1] "IP-Aliasing" is an obsolete way to
>>> manage multiple IP[v4]-addresses/masks on an interface.
>>> For having multiple IP[v4]-addresses on an interface this is
>>> absolutely
>>> true.
>>>
>>> For me "IP-Aliasing" is still a valid, good and easy way to "group" ip
>>> addresses to run multiple instances of the same service with different
>>> IPs
>>> via virtual interfaces on a single physical NIC.
>>>
>>> Short story:
>>> I recently added IPv6 to my LAN setup and recognized that IP-Aliasing
>>> is not
>>> support by the kernel.
>>> Could IP-Aliasing support for IPv6 be added to the kernel?
>>
>> You should probably better explain what is the feature you are using
>> with IPv4 but you are missing for IPv6. The actual IP aliasing has been
>> removed in kernel 2.2, i.e. 20 years ago. Since then, there is no IP
>> aliasing even for IPv4. What exactly works for IPv4 but does not for
>> IPv6?
>
> Used feature is the label option of `ip`, which works for IPv4, but not
> with IPv6.
>
> Goal: Use virtual interfaces to run separate instances of a service on
> different IP addresses on the same machine.
> For example with dnsmasq I use `-interface ens192` for the normal main
> instance, while using `-interface ens192:0` and `-interfaces ens192:1`
> for special instances only assigned to specific machines via their MAC
> addresses.
You would generally instruct your daemon to listen to an address rather
than an interface. For dnsmasq you can do this with the --listen-address
option instead of the --interface option, AFAIK.
-Toke
next prev parent reply other threads:[~2019-05-20 20:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 18:49 IP-Aliasing for IPv6? M. Buecher
2019-05-14 19:15 ` Heiner Kallweit
2019-05-15 8:42 ` Matthias May
2019-05-15 9:26 ` Michal Kubecek
2019-05-20 20:23 ` M. Buecher
2019-05-20 20:33 ` Toke Høiland-Jørgensen [this message]
2019-05-20 20:53 ` Michal Kubecek
2019-05-26 20:13 ` IP-Aliasing for IPv6? (actually "labels") M. Buecher
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=87pnocvpbd.fsf@toke.dk \
--to=toke@redhat.com \
--cc=hkallweit1@gmail.com \
--cc=maddes+kernel@maddes.net \
--cc=matthias.may@neratec.com \
--cc=mkubecek@suse.cz \
--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;
as well as URLs for NNTP newsgroup(s).