From: Wolfgang Bumiller <w.bumiller@proxmox.com>
To: "DERUMIER, Alexandre" <Alexandre.DERUMIER@groupe-cyllene.com>
Cc: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>,
"mark@tuxis.nl" <mark@tuxis.nl>
Subject: Re: [pve-devel] [PATCH pve-common] fix #4299: network : disable_ipv6: fix path checking
Date: Fri, 21 Oct 2022 10:16:31 +0200 [thread overview]
Message-ID: <20221021081631.lhywt7pmr3h6q2os@wobu-vie.proxmox.com> (raw)
In-Reply-To: <504aecd55d5422b0f401309c938c3df69a454b9f.camel@groupe-cyllene.com>
On Fri, Oct 21, 2022 at 04:55:08AM +0000, DERUMIER, Alexandre wrote:
> Hi,
>
> This is to avoid to have ipv6 local-link ip address on every generated
> tap interfaces (and fwbr bridges too).
> (and have bad packets send to the network)
To be more precise: it's a security measure.
You don't want the host to get IPv6-link-local addresses on every tap,
veth, fw-link, fw-bridge device we create, as each of those would
potentially allow VMs to send packets addressed to that device, which is
very unexpected :-)
>
>
> This, of course, don't disabling ipv6 support inside the vm/ct.
>
>
>
> Le jeudi 20 octobre 2022 à 17:07 +0000, Mark Schouten via pve-devel a
> écrit :
> > Hi,
> >
> > Sorry. But I always get extremely triggered by functions called
> > ‘disable_ipv6()’.
> >
> > Can someone hit me with a cluebat as to why that function even
> > exists?
> > (Since we deploy Proxmox without IPv4, so anywhere where ipv6 is
> > actively disabled, will break stuff for us).
You obviously don't use...
...umm
...any software out there that does networking :-D
Well, maybe Ceph Hammer, that one worked, but IPv6-only got increasingly
inbearable afterwards until I gave up.
next prev parent reply other threads:[~2022-10-21 8:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 22:24 Alexandre Derumier
2022-10-20 10:05 ` Wolfgang Bumiller
2022-10-20 16:18 ` DERUMIER, Alexandre
[not found] ` <mailman.64.1666287516.489.pve-devel@lists.proxmox.com>
2022-10-21 4:55 ` DERUMIER, Alexandre
2022-10-21 8:16 ` Wolfgang Bumiller [this message]
2023-01-16 9:45 ` [pve-devel] applied: " Wolfgang Bumiller
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=20221021081631.lhywt7pmr3h6q2os@wobu-vie.proxmox.com \
--to=w.bumiller@proxmox.com \
--cc=Alexandre.DERUMIER@groupe-cyllene.com \
--cc=mark@tuxis.nl \
--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 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.