From: proxmox@selund.se
To: matthew@peregrineit.net,
Proxmox VE user list <pve-user@lists.proxmox.com>,
duluxoz <duluxoz@gmail.com>,
Stefan Hanreich <s.hanreich@proxmox.com>
Subject: Re: [PVE-User] Problem With Bond & VLANs - Help Please
Date: Fri, 16 Aug 2024 13:32:05 +0200 [thread overview]
Message-ID: <ea8cf9c2-6cea-4dd9-af11-96e4a8298350@selund.se> (raw)
In-Reply-To: <534f2488-4441-43eb-9767-5e20b531f6b3@gmail.com>
On 16/08/2024 12:42, duluxoz wrote:
> Hi Stephan,
>
> My apologises, I should have been more precise.
>
> What doesn't work? Most of the ifaces are down (won't come up
> automatically as I expect (not even NIC3)), and so I have no
> connectivity to the LAN, let alone the rest of the outside world.
>
> Yes, each VLAN should have its own gateway - each VLAN is its own
> subnet, of course.
>
> Results of `ip r`:
>
> ~~~
> default via 10.0.200.1 dev vmbr0 proto kernal onlink linkdown
> 10.0.100.0/24 dev bond0.100 proto kernal scope link src 10.0.100.0
> linkdown
> 10.0.200.0/24 dev bond0.200 proto kernal scope link src 10.0.200.0
> linkdown
> 10.0.200.0/24 dev vmbr0 proto kernal scope link src 10.0.200.100 linkdown
> ~~~
>
I believe your problem is in your definition of bond0
~~~
auto bond0
iface bond0 inet manual
bond-members eno1 eno2
~~~
Bond members here should be eno1 and eno2, and not nic1 nic2
Looking at the eno3 nic, you have done the same problem nic3 should be eno3
~~~
auto eno3
iface eno3 inet static
address 10.0.300.100/24
~~~
Another problem I see with your configuration is that you define
gateways on each vlan interface. Linux only have one routing domain.
Remember that you don't need either gateway nor ip address on the bridge
you use for vm's.
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent reply other threads:[~2024-08-16 11:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 7:36 duluxoz
2024-08-16 8:05 ` Christian Kivalo
2024-08-16 9:43 ` duluxoz
2024-08-16 9:53 ` Stefan Hanreich
2024-08-16 10:42 ` duluxoz
2024-08-16 11:26 ` Gilberto Ferreira
2024-08-16 11:26 ` proxmox
2024-08-16 11:32 ` proxmox [this message]
2024-08-18 11:14 duluxoz
2024-08-18 14:07 ` Gilberto Ferreira
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=ea8cf9c2-6cea-4dd9-af11-96e4a8298350@selund.se \
--to=proxmox@selund.se \
--cc=duluxoz@gmail.com \
--cc=matthew@peregrineit.net \
--cc=pve-user@lists.proxmox.com \
--cc=s.hanreich@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