From: Wolfgang Bumiller <w.bumiller@proxmox.com>
To: Dietmar Maurer <dietmar@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH v3 manager] ad #3140: allow interface suffix in dns entries
Date: Wed, 25 Nov 2020 12:51:47 +0100 (CET) [thread overview]
Message-ID: <810836939.438.1606305107732@webmail.proxmox.com> (raw)
In-Reply-To: <307314515.437.1606304361026@webmail.proxmox.com>
What text do you mean exactly? The interface name?
Arbitrary null-terminated byte string...
(Yes I can name an interface "---" or 💩 (poop-emoji)...,
neither of which our iface schema in JSONSchema.pm would allow...)
> On 11/25/2020 12:39 PM Dietmar Maurer <dietmar@proxmox.com> wrote:
>
>
> Thanks for the info. But what encoding does that text use? I cannot find that in RFC4007 (they only
> talk about strings and text).
>
> > > Answering myself, it is defined in RFC4007.
> > >
> > > But "man resolv.conf" say address must be RFC2373 ?
> >
> > It'll still work. It's a very common notation for link local addresses,
> > since with multiple interfaces you have multiple routes with the exact
> > same prefix (including length). One `fe80::/64 dev <iface>` entry for
> > every ipv6 enabled interface, so things such as `ping fe80::1` don't
> > know what to do, so you need to either add `-I IFACE` or use
> > `fe80::1%IFACE`.
> >
> > `getaddrinfo()` also generally supports it, so any application using
> > it properly will work fine with this.
> > (eg. `ssh foo@fe80::1%eth0` works)
next prev parent reply other threads:[~2020-11-25 11:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 10:36 Wolfgang Bumiller
2020-11-25 11:08 ` Dietmar Maurer
2020-11-25 11:22 ` Dietmar Maurer
2020-11-25 11:34 ` Wolfgang Bumiller
2020-11-25 11:39 ` Dietmar Maurer
2020-11-25 11:51 ` Wolfgang Bumiller [this message]
2020-11-25 11:57 ` Dietmar Maurer
2020-11-25 11:22 ` Stoiko Ivanov
2020-11-25 12:31 ` [pve-devel] applied: " Thomas Lamprecht
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=810836939.438.1606305107732@webmail.proxmox.com \
--to=w.bumiller@proxmox.com \
--cc=dietmar@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/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