From: Stefan Hanreich <s.hanreich@proxmox.com>
To: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>,
"pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-network 0/7] add dhcp support for all zones
Date: Thu, 22 Feb 2024 11:52:04 +0100 [thread overview]
Message-ID: <95411a42-01b8-4a2b-aa06-e378ed7a9a35@proxmox.com> (raw)
In-Reply-To: <6c7a0c383c6aee77689433815775e27f5259da91.camel@groupe-cyllene.com>
On 2/22/24 11:41, DERUMIER, Alexandre wrote:
> what is the output of "ifreload -a -d" ?
nothing mentioning ip-forward sadly, I had already looked at
/var/log/ifupdown2 to get an idea of what's going wrong but I couldn't
find anything mentioned there as well (I think the output is the
same..). I think it might just get ignored when applying - but not when
checking.
I guess I'll have to dig deeper into ifupdown2...
> mmm, good catch, I'll look to add a check for this.
> I'll check too for vlan zone, with non vlan-aware bridge without
> interface.
Yes, it shouldn't be too hard to check. I can also do this while I'm at it.
> BTW, for dnsmasq + ipv6 with evpn/vrf, we need to add a patch.
>
> What do you think about providing a proxmox package for dnsmasq with
> this patch, + remove the default dnsmasq service. (as currently it's
> a little bit hacky, with manually disabling the main service)
It's hard to tell - not sure if we want to take on the work of
maintaining a separate dnsmasq package. I'll try and talk with Wolfgang
/ Thomas about this (or maybe they're reading this and can chime in?).
prev parent reply other threads:[~2024-02-22 10:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 8:32 Alexandre Derumier
2023-12-19 8:32 ` [pve-devel] [PATCH pve-network 1/7] dhcp: add vrf support Alexandre Derumier
2023-12-19 8:32 ` [pve-devel] [PATCH pve-network 2/7] dhcp: enable-ra on layer3 zones only Alexandre Derumier
2023-12-19 8:32 ` [pve-devel] [PATCH pve-network 3/7] dnsmasq service: run service in vrf Alexandre Derumier
2023-12-19 8:32 ` [pve-devel] [PATCH pve-network 4/7] zones: evpn: add dhcp support Alexandre Derumier
2023-12-19 8:32 ` [pve-devel] [PATCH pve-network 5/7] zones: vlan: " Alexandre Derumier
2023-12-19 8:32 ` [pve-devel] [PATCH pve-network 6/7] zones: qinq: " Alexandre Derumier
2023-12-19 8:32 ` [pve-devel] [PATCH pve-network 7/7] zones: vxlan: " Alexandre Derumier
2023-12-22 14:01 ` [pve-devel] [PATCH pve-network 0/7] add dhcp support for all zones Stefan Hanreich
2023-12-22 21:27 ` DERUMIER, Alexandre
2024-02-22 10:13 ` Stefan Hanreich
[not found] ` <6c7a0c383c6aee77689433815775e27f5259da91.camel@groupe-cyllene.com>
2024-02-22 10:52 ` Stefan Hanreich [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=95411a42-01b8-4a2b-aa06-e378ed7a9a35@proxmox.com \
--to=s.hanreich@proxmox.com \
--cc=alexandre.derumier@groupe-cyllene.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