From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Wolfgang Link <w.link@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: [pve-devel] applied: [pve-docs] Correct the device declaration in the bonding example.
Date: Mon, 2 Nov 2020 08:04:36 +0100 [thread overview]
Message-ID: <28d1f1f0-9b7c-7867-ff63-efcf85e1fe3f@proxmox.com> (raw)
In-Reply-To: <687327362.523.1604299095996@webmail.proxmox.com>
On 02.11.20 07:38, Wolfgang Link wrote:
> Both is possible.
>
> In the original version there where three nics used.
>
> Personally, I don't like network setup with multiple IP addresses at different layers.
> They are more complex and harder to debug.
after taking a look myself I'd say that the key point to add eno3 is
rather that we have a "Use a bond as bridge port" already after this
example.
So yes, patch is OK as is: applied, thanks!
prev parent reply other threads:[~2020-11-02 7:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 9:01 [pve-devel] " Wolfgang Link
2020-10-30 14:23 ` Thomas Lamprecht
2020-11-02 6:38 ` Wolfgang Link
2020-11-02 7:04 ` Thomas Lamprecht [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=28d1f1f0-9b7c-7867-ff63-efcf85e1fe3f@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=w.link@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