From: mj <lists@merit.unu.edu>
To: dorsy <dorsyka@yahoo.com>,
Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] ip address on both bond0 and vmbr0
Date: Tue, 23 Mar 2021 12:36:03 +0100 [thread overview]
Message-ID: <2edd3b56-ab3b-28c2-c87f-3b6f0a7158ac@merit.unu.edu> (raw)
In-Reply-To: <c32dec75-3644-3f82-4615-7fbc18630126@yahoo.com>
Hi Dorsy,
Thanks for the quick reply! :-)
On 23/03/2021 11:51, dorsy wrote:
> Also, if You look at the examples, they do not use a bond and VM bridge
> with 2 addresses, in the first, an IP is on the bond, the VM bridge is
> another physical IF.
>
> The second example shows the VM bridge is over the bond, and the IP is
> on the bridge IF (no IP on the bond there).
Yes, I realise they are not identical. (that's why I said: freely based
on..)
I thought: adding the ceph IP on the bond0 would be a nice and easy way
to seperate ceph traffic from the VMs.
I have tried now as you suggested, and that works, yes. Thank you!
> iface vmbr0 inet static
> address 192.168.143.10/24
> gateway 192.168.143.1
> bridge-ports bond0
> bridge-stp off
> bridge-fd 0
> post-up /sbin/ip addr add 10.0.0.10/24 dev vmbr0
I just remain curious why it would be so strange to put the IP on bond0.
I do see most examples on the net NOT having an IP on bond0. So I
understand it's not normal.
But what's wrong with it?
I tried also putting the "post-up addr add" stanza to bond0 config, but
it doesn't work as well. (strange, given that adding it works, after
boot has finished)
I will use your suggestion, thanks, appreciated.
But still: Why is putting an ip on bond0 considered strange, and why
doesn't it work *during* boot, and does it work *after* boot?
MJ
next prev parent reply other threads:[~2021-03-23 11:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 10:42 mj
[not found] ` <c32dec75-3644-3f82-4615-7fbc18630126@yahoo.com>
2021-03-23 11:36 ` mj [this message]
2021-03-23 12:02 ` Ronny Aasen
2021-03-23 14:28 ` mj
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=2edd3b56-ab3b-28c2-c87f-3b6f0a7158ac@merit.unu.edu \
--to=lists@merit.unu.edu \
--cc=dorsyka@yahoo.com \
--cc=pve-user@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