Create separate bridge with public ip nat.

Hi, i been struggling with this now.
host machine using public_ip_1
host machine have access public_ip_2 public_ip_3 public_ip_4
host machine will have vm_1 vm_2 vm_3
custom private bridge that will be used by all vms, and uses public_ip_4 for nat.
any help appreciated.

Although it’s probably OK to post this request in the Networking Forum,
Your question has more to do with virtualization and setting up virtual networks.

You’ll also need to provide more details about the virtualization technology you’ve installed because networking that use bridge devices is used by practically every virtualization technology but the management tools can be radically different.

If you’ve installed KVM, Xen or LXC, you’d be strongly advised to install using the YaST Install Virtualization module which will install not only your chosen virtualization but also the libvirt tools (graphical management tools) and offer to install a bridging bridge device. Whether you intend to use this bridge device or not, it’s advised to install it anyway so that it’s available should you want that kind of network connectivity in the future.

Should you want to create a NAT bridge by command line (not advisable, this particular configuration is not easy using command line), you should ask your question that way.


Hi @tsu2; am using lxd. i have tried yast2 terminal, to add all my additional ip’s under the eth0, then from same network windows added routes and enabled v4 routing. no luck has been stuck with it for 2 days.
note; lxd has a way for creating bridges easily, but that will make use of public_ip_1 which used by host. thus. i avoid using it, and wish to use public_ip_4 as stated on my question.
am using firewalld as default. after a lot of readings i found that, yast2 network routing uses iptables, and iptables are avoided while using firewalld.
am asking for a guide using yast2 or cmd, well, am just asking for a guide that will allow me get the result wanted on my question, the method not important, by prefer to stick with software i already have.
i suggest to ignore what i have done and not ask me what i done and not done, becasue that will make more harder on me to understand it. i rather have a working example, so i learn from it.

A bridge is a virtual device that is bound to an interface.
I don’t know that you can bind a device with an IP address type that is not supported by the underlying interface… That’s something I’ve never encountered and doubt can or should be done.

IMO you should enable both IPv4 and IPv6 addresses on your HostOS interface, and only then I would assume a bridging bridge device would support configuring an IP address of your choice in the VM.

If you don’t want the VM and HostOS to share the same interface for normal networking, I suppose you can create a new interface dedicated to be used by the VM and not the HostOS.
You can also do a hardware pass-through of a physical Network card which would both remove HostOS access and grant access to a specific VM.

There may be other possible configurations I haven’t thought of…