Re: Creating a bridge

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


On 8/14/23 20:54, Alex wrote:
I've just installed fedora38 over my previous fedora install but didn't save my network config that included a bridge to allow for local IPs for my virtual machines. Is there a network tool that I can use to create a bridge so I can then use the bridge option with virt-manager to assign IPs to my Win10 virtual machine?

I'm used to doing the old-school network-scripts/ifcfg-eth0 stuff by hand, but realize that doesn't exist anymore.

Perhaps someone has a basic /etc/NetworkManager/system-connections bridge config they could paste here to get me started or the proper nmcli commands I need?

I suppose I could probably also use NAT, but I'd rather have my gateway doing the NAT.

# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
     inet <> scope host lo
        valid_lft forever preferred_lft forever
     inet6 ::1/128 scope host noprefixroute
        valid_lft forever preferred_lft forever
2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
     link/ether c8:7f:54:cd:b7:bc brd ff:ff:ff:ff:ff:ff
    inet <> brd scope global dynamic noprefixroute enp4s0
        valid_lft 31976sec preferred_lft 31976sec
     inet6 fe80::ca7f:54ff:fecd:b7bc/64 scope link noprefixroute
        valid_lft forever preferred_lft forever
3: wlo1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000     link/ether 4a:d4:02:42:a2:2e brd ff:ff:ff:ff:ff:ff permaddr 2c:3b:70:47:ce:08
     altname wlp5s0
4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
     link/ether 52:54:00:c8:a0:df brd ff:ff:ff:ff:ff:ff
    inet <> brd scope global virbr0
        valid_lft forever preferred_lft forever

If you have cockpit installed, fire up your browser and go to the networking section. Choose to create a bridge, associate the interface you want attached to the bridge, and it will set it all up for you.

Otherwise, the nmcli steps outlined will do it for you. I find it a lot easier to just use cockpit. Literally a couple of clicks and it creates the bridge, attaches the interface, and you don't have to remember the crazy nmcli syntax.

But I'm lazy, so take it for what it's worth. ;-)

users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct:
List Guidelines:
List Archives:
Do not reply to spam, report it:

[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux