On 6/16/25 3:24 PM, Samuel Sieb wrote:
On 6/16/25 2:38 PM, Patrick Dupre via users wrote:
On 6/16/25 2:11 PM, Patrick Dupre via users wrote:
OK,
Now it is working with
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window
irtt Iface
0.0.0.0 192.168.1.1 0.0.0.0 UG 0
0 0 enp0s20f0u11
0.0.0.0 192.168.1.1 0.0.0.0 UG 0
0 0 bridge0
10.40.0.0 0.0.0.0 255.255.255.0 U 0
0 0 bridge0
192.168.1.0 0.0.0.0 255.255.255.0 U 0
0 0 enp0s20f0u11
192.168.1.1 0.0.0.0 255.255.255.255 UH 0
0 0 bridge0
192.168.122.0 0.0.0.0 255.255.255.0 U 0
0 0 virbr0
Question
I have enp1s0 ipv4 manually set as
10.40.1.0/24 without GW, neither DNS
enp2s0 ivpv4 also manually set as
10.40.2.0/24 without GW, neither DNS
These should both be unconfigured. They are part of the bridge.
And I'm still concerned that 192.168.1.1 is on the bridge.
It is configured in automatic DHCP
enp0s20f0u11: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.166 netmask 255.255.255.0 broadcast
192.168.1.255
inet6 fe80::a594:2280:6476:1293 prefixlen 64 scopeid
0x20<link>
ether 96:bd:e2:d4:3e:52 txqueuelen 1000 (Ethernet)
Should it be set manually?
That is the USB port. It should not be part of the bridge.
and
enp1s0 port 1 and enp2s0 port 2 set automatic DHCP
Should I keep it like that?
Will be the IP addresses always conserved?
I don't know what you mean by this. I would recommend that PC B and C
have static addresses. I don't think the DHCP reservations are
preserved.
They are static
The only static ones are bridge0 port1 and port2
and
USB Ethernet (enp0s20f0u11)
I don't understand what you mean about the ports. Whatever those are,
they shouldn't be configured.
Hi Patrick,
Samuel has helped me with several things before ,
including network issues. He is genius level
good at this stuff.
About two months ago I had a bridge problem between
a host and a qemu-kvm virtual machine. I was tearing
my hair out trying to figure out why everything seemed
correct but it would not work. I kept tearing it
apart and rebuilding it over and over and over.
Although the network manager is "suppose" to do this
(or something similar), I discovered the following
corrected the problem:
"#" means as "root"
# systemctl restart NetworkManager.service
If you run it as a user, systemctl will prompt you
for the root password.
Once you get all of Samuel fixed in place and if
it just does not seems to work, try the restart command.
-T
Here is my documentation on how to set up a bridge.
Keep in mind that if Sam says something different,
go with him. He is 1000 time more skilled at this
than me. This is aimed at bridging a qemu-kvm
virtual machine.
Setting Up a Network Bridge Using nmcli Tool:
Prerequisite:
# vi /etc/NetworkManager/NetworkManager.conf
[main]
plugins=ifupdown
[ifupdown]
managed=false
nmcli is a widely-used, scriptable and powerful command-line tool to
control NetworkManager and report network status. It communicates
directly to NetworkManager and controls only system-wide
connections. Importantly, it allows users to use abbreviations,
as long as they are a unique prefix in the set of possible options.
First, use the IP command to identify the network interfaces (both physical
and virtual) currently attached to your machine and the networks
they are connected to.
# ip add
From the output of the above command, the Ethernet interface is called
enp2s0,
we will add this interface to the bridge as a slave.
Next, to list the active network connections on the test system, use the
following nmcli command.
# nmcli conn show --active
Important: If the libvirtd daemon (libvirtd) is installed and started, the
default network interface that represents the network bridge (virtual
network
switch) is virbr0 as seen in the above screenshots. It is configured to run
in NAT mode.
Next, create a network bridge interface using the following nmcli
command, where
conn or con stands for connection, and the connection name is br0 and
the interface
name is also br0.
# nmcli conn add type bridge con-name br0 ifname br0
Note: In a bridged mode, the virtual machines are easily accessible to
the physical
network, they appear within the same subnet as the host machine and they can
access services such as DHCP.
To set a static IP address, run the following commands to set IPv4 address,
network mask, default gateway, and DNS server of the br0 connection (set the
values according to your environment).
# nmcli conn modify br0 ipv4.addresses '192.168.1.1/24'
# nmcli conn modify br0 ipv4.gateway '192.168.1.1'
# nmcli conn modify br0 ipv4.dns '192.168.1.1'
# nmcli conn modify br0 ipv4.method manual
Now add the Ethernet interface (enp2s0) as a portable device to the bridge
(br0) connection as shown.
# nmcli conn add type ethernet slave-type bridge con-name bridge-br0
ifname enp2s0 master br0
Next, bring up or activate the bridge connection, you can use the
connection name or
UUID as shown.
# nmcli conn up br0
OR
# nmcli conn up 2f03943b-6fb5-44b1-b714-a755660bf6eb
Then deactivate or bring down the Ethernet or Wired connection.
# nmcli conn down Wired\ connection\ 1
OR
# nmcli conn down e1ffb0e0-8ebc-49d0-a690-2117ca5e2f42
Now when you try to list the active network connections on the system,
the bridge
connection should display on the list.
# nmcli conn show --active
Next, use the following bridge command to display the current bridge port
configuration and flags.
# bridge link show
To deactivate the bridge connection and delete it, run the following
commands.
Note that you first of all have to activate the wired connection.
# nmcli conn up Wired\ connection\ 1
# nmcli conn down br0
# nmcli conn del br0
# nmcli conn del bridge-br0
For more information, see the nmcli manual page.
# man nmcli
--
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
