Hi Wei,

So instead of the vlan interface as bridge slave, I should have the bond?



-----Original Message-----
From: Wei ZHOU <ustcweiz...@gmail.com> 
Sent: Wednesday, July 17, 2024 11:25 AM
To: users@cloudstack.apache.org
Subject: Re: Networking issue with VLAN setup

It looks like there is no physical interface (ethX/bondX) added to the bridge 
for guest networks (cloudbrX).

-Wei



On Wed, Jul 17, 2024 at 10:07 AM Alexandru Stan 
<alexandru.s...@lifeincloud.com.invalid> wrote:
>
> Hi everyone. I have a specific network setup that doesn't seem to be working 
> with CS for some reason, I think it's a missconfiguration on my part. So, 
> there are 2 interfaces on the host, one it's a bond interface and one it's a 
> vlan interface that's a member of the bond. Since I need a bridge for CS, I 
> added one, with the ipv4 settings and everything, and made the vlan interface 
> the slave of the bridge. When I tried to add the zone (advanced) I set the 
> bridge label on the management interface and added the ip range with untagged 
> traffic, but it couldn't add the hosts correctly, they all had alert status. 
> Removing the label from the management interface seems to work somehow, the 
> hosts are up and running, the system vms are up and connected, etc. I added 
> an isolated network and tried to create a vm, but this is where the main 
> issue starts, I cannot deploy any vm, they all fail with the same error and 
> it has something to do with networking. The error on the host is this 
> (obviously the device name varies):
>
> Process [206176] for command 
> [/usr/share/cloudstack-common/scripts/vm/network/vnet/modifyvlan.sh -v 1277 
> -p  -b br-1277 -o add ] encountered the error: [Cannot find device 
> "br-1277"/usr/share/cloudstack-common/scripts/vm/network/vnet/modifyvlan.sh: 
> line 37: /proc/sys/net/ipv6/conf/br-1277.1277/disable_ipv6: No such file or 
> directoryCannot find device "br-1277.1277"Failed to create vlan 1277 on pif: 
> br-1277.].
>
> Does anyone have a clue about what could be wrong here?
>
> Thank you!

Reply via email to