> > Bridged adapter: cable connected
> > all give: IP 169.254.168.63
> 
> The 169.254 address is an Automatic Private IP Addressing (APIPA). You
> are missing a DHCP server somewhere. Or maybe you are missing a
> component that allows access to the DHCP server, like dnsmasq.

You are probably right.
dnsmasq: failed to create listening socket for 127.0.0.1: Address already in use
I do not know what to do

> > enp1s0
> > enp2s0
> > bridge0
> > virbr0
> 
> Use bridge0 when you have a DHCP server on your internal network, and
> you want guests to receive an IP address from the DHCP server. The VM
> guest will be addressable from other hosts on your internal network.

Windows IP Configuration
Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . : 
   Link-local IPv6 Address . . . . . : fe80::f894:cb4:e005:a83f%11
   IPv4 Address. . . . . . . . . . . : 10.40.0.87
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 10.40.0.1

Tunnel adapter isatap.{E7AEAEC1-BF25-487B-B4F4-E3A9279FC132}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 


> Use virbr0 when you want to NAT the guest. It will create a [virtual]
> private network on the host machine. Other machines on your internal
> network will _not_ be able to address the VM guest.

Windows IP Configuration
Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . : 
   Link-local IPv6 Address . . . . . : fe80::f894:cb4:e005:a83f%11
   Autoconfiguration IPv4 Address. . : 169.254.168.63
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . : 

Tunnel adapter isatap.{E7AEAEC1-BF25-487B-B4F4-E3A9279FC132}:

   Media State . . . . . . . . . . . : Media disconnected


NAT
Windows IP Configuration
Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . : .
   IPv6 Address. . . . . . . . . . . : fd17:625c:f037:2:f894:cb4:e005:a83f
   Temporary IPv6 Address. . . . . . : fd17:625c:f037:2:c431:9b88:8edb:897c
   Link-local IPv6 Address . . . . . : fe80::f894:cb4:e005:a83f%11
   IPv4 Address. . . . . . . . . . . : 10.0.2.15
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : fe80::2%11
                                       10.0.2.2
Tunnel adapter isatap..:

   Media State . . . . . . . . . . . : Media disconnected

I am lost

> 
> Jeff
> 
> On Wed, Sep 24, 2025 at 6:30 AM Patrick Dupre via users
> <[email protected]> wrote:
> >
> > Hello,
> >
> > I am not sure that it is entirely relevant for the list.
> >
> > I use oracle VM and Windows 7
> > I cannot connect on internet from windows: unidentified connection
> > I use DHCP under windows
> >
> > on Linux
> > Destination     Gateway         Genmask         Flags Metric Ref    Use 
> > Iface
> > 0.0.0.0         192.168.1.1     0.0.0.0         UG    100    0        0 
> > enp0s20f0u11
> > 10.40.0.0       0.0.0.0         255.255.255.0   U     425    0        0 
> > bridge0
> > 192.168.1.0     0.0.0.0         255.255.255.0   U     100    0        0 
> > enp0s20f0u11
> > 192.168.122.0   0.0.0.0         255.255.255.0   U     0      0        0 
> > virbr0
> >
> > enp0s20f0u11: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
> >         inet 192.168.1.120  netmask 255.255.255.0  broadcast 192.168.1.255
> >         inet6 fe80::c17c:128d:4290:d16f  prefixlen 64  scopeid 0x20<link>
> >         ether 32:5b:54:67:c2:a7  txqueuelen 1000  (Ethernet)
> >         RX packets 1612  bytes 573729 (560.2 KiB)
> >         RX errors 0  dropped 0  overruns 0  frame 0
> >         TX packets 1504  bytes 394533 (385.2 KiB)
> >         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> > bridge0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
> >         inet 10.40.0.1  netmask 255.255.255.0  broadcast 10.40.0.255
> >         ether b2:c9:44:5e:80:67  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 1215 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
> > 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 44 overruns 0  carrier 0  collisions 0
> >
> >
> >
> > Under Windows, I chose (NAT or internal network do not help)
> > Bridged adapter
> > and I have the choices
> > enp1s0
> > enp2s0
> > bridge0
> > virbr0
> >
> > Allows VMs
> > Virtual cable connected
> >
> > Trying all the 4 the connection of the interface is OK
> > Bridged adapter: cable connected
> > all give: IP 169.254.168.63
> >
> > but no gateway and Unidentified Network, without Internet connection
> >
> > Any idea?
>
-- 
_______________________________________________
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

Reply via email to