Let's pull your post apart to clarify some things and provide some answers....
Before discussing anything, I'd suggest you run the following command which will display all your interfaces, it's a quick check to identify the names of any interface installed including the network bridge devices... like br0 and virbr0. If you're not sure what you're seeing, post it with your questions, I doubt there is anything in there that should threaten your system if publicly known.
Speaking of which, let's straighten out some confusing terminology since the label "bridge" will be used a couple of different ways...
Linux Bridge Device aka
Bridge Device aka
Network Bridge Device
A networking object that shims the network connection between the Guest VM and the network interface on the HostOS.
Bridge Device aka
Bridging Device
A device that's invisible to the network, normally but not always has the same NetworkID on all interfaces which distinguishes it from a router (where each interface usually has a different NetworkID).
And, for a little bit more confusion, "bridge" and "bridging" might be used interchangeably for any of the above.
Sometimes the only way to really understand what is described is to listen extremely carefully at how the device is named and how it's used.
If you understand the above, then you can start to understand that
A Bridge Device might be configured with a
Bridge configuration.
A Bridge Device might be configured with a
NAT configuration
A Bridge Device might be configured with a
Host-only network configuration.
I agree with @arvidjaar that even when you were running VMware that you used a bridging bridge device over your Wifi connection... unless you had security turned entirely off and was running an open hotspot.
The most common configuration is to use a NAT bridge device,
It's probably the most versatile bridge device that hardly ever requires any attention after it's configured no matter the Host's network connection... which might be WiFi, Wireless carrier, wired ethernet, direct to the Internet, proxied, filtered, etc.
I recommend that unless you want to connect to your Guest from another machine, you always set up a NAT configuration.
Now, regarding your post...
As I described earlier, you can run the following on your Linux host which will tell you for sure whether you have bridge devices set up like br0 (which is the general label convention) or virbr0 (which is the convention used by any bridge devices created by libvirt). Although some documentation suggests libvirt might create a vnet interface I've never seen it. AFAIK vnet is the label for "virtual network" which is the address space associated with the specified bridge device.
As I suggested, most people typically use a NAT bridge device so that the Guest gets its IP address automatically in a separate network from the HostOS, so will work regardless whether there is a working DHCP on the real, physical network or not.
The only reason to try to set up a Guest with a bridging bridge device is to allow remote machines to initiate a network connection to your Guest. If you really need to make this work over a wireless connection, you might try setting up a tap interface... I haven't set this up for a very long time, and is rarely configured today by anyone. One place this is still described is buried in the deprecated section of the following KVM documentation
https://www.linux-kvm.org/page/Networking
You're using old LEAP 42.1 documentation when brctl was the standard tool to configure bridge devices.
Nowadays the following command is supposed to be used instead
This part of the YaST network configuration isn't active or used when using Network Manager.
Network Manager is the preferred way to manage your networking because it remembers configuration settings as you move around from wireless network to wireless network.
If you only set up on one wireless network permanently or don't mind manually setting up your network every time you move to a new network, you can change from Network Manager to Wicked (It's the leftmost tab "Global" when you first open YaST network settings. When in Wicked mode, everything in YaST network settings becomes active but the bridge section should generally be ignored except to create and manage the bridge networking object...
You should use libvirt vm manager or kvm or qemu commands only to configure how the Guest selects and uses a bridge networking device.
If you installed KVM using the YaST Virtualization install module, you would have installed libvirt's vm manager.
Although the navigation is a bit clunky compared to VMware, almost all the parts are the same... You can create a new virtual network and in the process create a bridge device to access that virtual network.
And, from the Guest's properties you can configure networking properties to use a particular bridge device to access that network.
This part of the documentation only describes one way to create a bridge device and you might be able to access it only when in Wicked mode.
Instead of using YaST, I highly recommend using vm manager instead, it's not only easier to understand, it's also more versatile for setting up different kinds of bridge devices. The following is a link to the current LEAP documentation
https://doc.opensuse.org/documentati...ual-vmm-define
Keep in mind,
You can create network bridge devices by almost any method using any application... Using YaST, vm manager, command line, another virtualization technology, etc. Network bridge devices are very standard devices so no matter how it was created by whatever, if a VM can see it, it can be used.
HTH,
TSU
kvm and using a bridge
Reply With Quote
Originally Posted by Neal
Bookmarks