From: Wolfgang Bumiller <w.bumiller@proxmox.com>
To: Alexandre Derumier <aderumier@odiso.com>
Cc: pve-devel@lists.proxmox.com, "R. Grieger" <admin@grie.gr>
Subject: [pve-devel] applied: [PATCH pve-common] fix #4299: network : disable_ipv6: fix path checking
Date: Mon, 16 Jan 2023 10:45:38 +0100 [thread overview]
Message-ID: <20230116094538.5erccmw4hbyfqu3m@casey.proxmox.com> (raw)
In-Reply-To: <20221019222429.997436-1-aderumier@odiso.com>
Sorry for the delay, the change definitely doesn't hurt, I was just
wondering how it would happen.
It's now applied, thanks!
On Thu, Oct 20, 2022 at 12:24:29AM +0200, Alexandre Derumier wrote:
> It's possible to have a
> /proc/sys/net/ipv6/ directory
>
> but no
> /proc/sys/net/ipv6/conf/$iface/disable_ipv6
>
> Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
> ---
> src/PVE/Network.pm | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/src/PVE/Network.pm b/src/PVE/Network.pm
> index c468e40..9d726cd 100644
> --- a/src/PVE/Network.pm
> +++ b/src/PVE/Network.pm
> @@ -210,8 +210,8 @@ my $cond_create_bridge = sub {
>
> sub disable_ipv6 {
> my ($iface) = @_;
> - return if !-d '/proc/sys/net/ipv6'; # ipv6 might be completely disabled
> my $file = "/proc/sys/net/ipv6/conf/$iface/disable_ipv6";
> + return if !-e $file; # ipv6 might be completely disabled
> open(my $fh, '>', $file) or die "failed to open $file for writing: $!\n";
> print {$fh} "1\n" or die "failed to disable link-local ipv6 for $iface\n";
> close($fh);
> --
> 2.30.2
prev parent reply other threads:[~2023-01-16 9:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 22:24 [pve-devel] " 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
2023-01-16 9:45 ` Wolfgang Bumiller [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=20230116094538.5erccmw4hbyfqu3m@casey.proxmox.com \
--to=w.bumiller@proxmox.com \
--cc=aderumier@odiso.com \
--cc=admin@grie.gr \
--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