<div dir="ltr">FWIW, I first tried using the physical interface instead of the bridge, which also fails:<br><br>[root@katyusha ~]# prlsrvctl net set firewalla -t bridged --ifname enp5s0 -d "firewalla bridge"<br>WARNING: You are using a deprecated CLI component that will be dropped in the next major release. Please use virsh instead<br>Failed to update Virtual Network firewalla: Could not find a bridge for network adapter "firewalla". Please make sure the bridge is created.<br><br>Jake</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Apr 15, 2023 at 8:56 PM jjs - mainphrame <<a href="mailto:jjs@mainphrame.com">jjs@mainphrame.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hello all, <br><br>After testing ovz-9 alpha releases for some weeks using VMs, I have OVZ9 installed on a physical machine to do some further testing. Containers with host routed connections are working fine, and can migrate to and from OVZ-7 machines. <br><br>So I wanted to go to the next level, create lan and wan bridges for bridged networks, but it seems the prlsrvctl syntax has changed, and the commands no longer work as they did on OVZ-7. <br><br>A bridge br0 was created by the installer on the internal lan, and I added a bridge br1 which connects to the default gateway device, but trying to associate a bridge with a network fails with an error.<br><br>I created the network "Bridged" (which used to be automatically created on OVZ-7 install) and it defaulted to type host-only. Then I added the network "firewalla" as I have done on the OVZ-7 machine, and it also defaulted to host-only"<br><br>root@katyusha ~]# prlsrvctl net list<br>WARNING: You are using a deprecated CLI component that will be dropped in the next major release. Please use virsh instead<br>Network ID Type Bound To Bridge Slave interfaces<br>Bridged host-only virbr3 <br>Host-Only host-only virbr1 <br>firewalla host-only virbr4 <br><br>My next step was to change the type from "host-only" to "bridged", and that's where things went south:<br><br><div>[root@katyusha ~]# prlsrvctl net set Bridged -t bridged --ifname br0 -d "internal bridge"<br>WARNING: You are using a deprecated CLI component that will be dropped in the next major release. Please use virsh instead<br>Failed to find network adapter br0 on the server.</div><div><br>[root@katyusha ~]# prlsrvctl net set firewalla -t bridged --ifname br1 -d "firewalla bridge"<br>WARNING: You are using a deprecated CLI component that will be dropped in the next major release. Please use virsh instead<br>Failed to find network adapter br1 on the server.<br><br>Is there some documentation on the updated syntax?<br><br>Jake<br><br></div></div>
</blockquote></div>