From: Flavio Visentin via pve-user <pve-user@lists.proxmox.com>
To: pve-user@lists.proxmox.com
Cc: Flavio Visentin <flavio-pve@zipman.it>
Subject: Re: [PVE-User] OSPF when migrating from v8 to v9
Date: Wed, 8 Oct 2025 20:24:34 +0200 [thread overview]
Message-ID: <mailman.789.1759948435.390.pve-user@lists.proxmox.com> (raw)
In-Reply-To: <7B6E9EB5-6BFE-43FF-B44E-7CF030A938D0@xoxo.fr>
[-- Attachment #1: Type: message/rfc822, Size: 5135 bytes --]
From: Flavio Visentin <flavio-pve@zipman.it>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] OSPF when migrating from v8 to v9
Date: Wed, 8 Oct 2025 20:24:34 +0200
Message-ID: <0ae0296c-db0f-4924-a9ab-f517dc9230e9@zipman.it>
Hi,
On 10/7/25 17:58, Julien OHAYON wrote:
> Thanks for your reply. Unfortunately, when we apply the SDN
> configuration, it modifies the daemons file and sets it to “no”, since
> we haven’t configured OSPF directly in Proxmox. That’s the file I
> would like to prevent from being modified.
Did you try to make the file /etc/frr/daemons immutable during SDN enabling?
chattr +i /etc/frr/daemons
Maybe it fails with error, but giving a try doesn't cost anything.
Then you can configure the routing and finally remove the immutable
attribute.
Flavio
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
prev parent reply other threads:[~2025-10-08 18:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 6:16 Julien OHAYON
2025-10-07 13:52 ` Stefan Hanreich
2025-10-07 15:58 ` Julien OHAYON
2025-10-08 9:34 ` Stefan Hanreich
2025-10-08 10:48 ` Julien OHAYON
2025-10-08 18:24 ` Flavio Visentin via pve-user [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=mailman.789.1759948435.390.pve-user@lists.proxmox.com \
--to=pve-user@lists.proxmox.com \
--cc=flavio-pve@zipman.it \
/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.