public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Wolfgang Link <w.link@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
	Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [pve-docs] Correct the device declaration in the bonding example.
Date: Mon, 2 Nov 2020 07:38:15 +0100 (CET)	[thread overview]
Message-ID: <687327362.523.1604299095996@webmail.proxmox.com> (raw)
In-Reply-To: <5b2088b1-6dc9-5c90-7c4c-60450861fb07@proxmox.com>

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.

> Thomas Lamprecht <t.lamprecht@proxmox.com> hat am 30.10.2020 15:23 geschrieben:
> 
>  
> On 30.10.20 10:01, Wolfgang Link wrote:
> > Signed-off-by: Wolfgang Link <w.link@proxmox.com>
> > ---
> >  pve-network.adoc | 4 +++-
> >  1 file changed, 3 insertions(+), 1 deletion(-)
> > 
> > diff --git a/pve-network.adoc b/pve-network.adoc
> > index 294c201..692326f 100644
> > --- a/pve-network.adoc
> > +++ b/pve-network.adoc
> > @@ -355,6 +355,8 @@ iface eno1 inet manual
> >  
> >  iface eno2 inet manual
> >  
> > +iface eno3 inet manual
> > +
> >  auto bond0
> >  iface bond0 inet static
> >        slaves eno1 eno2
> > @@ -369,7 +371,7 @@ iface vmbr0 inet static
> >          address  10.10.10.2
> >          netmask  255.255.255.0
> >          gateway  10.10.10.1
> > -        bridge-ports eno1
> > +        bridge-ports eno3
> 
> or bond0 ?
> 
> >          bridge-stp off
> >          bridge-fd 0
> >  
> >




  reply	other threads:[~2020-11-02  6:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-30  9:01 Wolfgang Link
2020-10-30 14:23 ` Thomas Lamprecht
2020-11-02  6:38   ` Wolfgang Link [this message]
2020-11-02  7:04     ` [pve-devel] applied: " Thomas Lamprecht

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=687327362.523.1604299095996@webmail.proxmox.com \
    --to=w.link@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=t.lamprecht@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal