On Mon, Sep 29, 2025 at 03:37:22PM +0200, Patrick Dupre via users wrote:
I am back with my issue with more details
Here is the configuration
bridge0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 10.40.0.1 netmask 255.255.255.0 broadcast 10.40.0.255
ether 7a:32:80:77:67:8d txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 66 overruns 0 carrier 0 collisions 0
I'm running a Win 10 VM. It is set to use "Bridged Adapter" and set to
"eth1", my host's primary connection to the network. I think that would
be the equivalent of your "enp0s20f0u11" below. The guest has its own
IP that is visible on my LAN.
Differences:
My lan uses the 10.0.0.X addresses, not the 192.168.1.X shown below.
The guest VM also has a 10.0.0.X address.
I assume the listings are from "ip addr" or "ifconfig". I have no
bridgeX adapter in my listings.
enp0s20f0u11: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.180 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::d8dc:44dd:24df:71e2 prefixlen 64 scopeid 0x20<link>
ether f2:0e:3c:4d:0f:b7 txqueuelen 1000 (Ethernet)
RX packets 661491 bytes 566119617 (539.8 MiB)
RX errors 30 dropped 0 overruns 0 frame 30
TX packets 424779 bytes 116390563 (110.9 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
enp1s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 50:91:e3:c9:58:ab txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
enp2s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 88:d7:f6:c5:a3:9d txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 29651 bytes 3595244 (3.4 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 29651 bytes 3595244 (3.4 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255
ether 52:54:00:99:2e:c5 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 59 overruns 0 carrier 0 collisions 0
enp0s20f0u11 is the interface that I use to connect with internet from fedora.
It is an USB wireless connection
With the VM, the interface offers me
NAT
Bridged Adapter
the other options are not relevant I guess
With NAT there are no additional option
The connection seems working (Identification OK, the connection status shows
sent and received) except that I get
with Bridged Adapter, I have 5 options
virbr0
enp2s0
enp1s0
enp0s20f0u11
bridge0
The only one which make sense is enp0s20f0u11
but it is worst that with NAT, there is no identification of the connection.
I do not know what else I could try !
Thank for ideas.
===========================================================================
Patrick DUPRÉ | | email: [email protected]
===========================================================================
--
Jon H. LaBadie [email protected]
--
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
