> Patrick Dupre wrote:
> > > Jeffrey Walton wrote:
> > > On Tue, Sep 30, 2025 at 7:47 AM Joe Average [email protected] wrote:
> > > ....
> > > What VM software are you using?
> > > I seem to recall Virtual Box had some sharp edges when using a
> > > wireless adapter. Something along the lines of the internet did not
> > > work for NAT'd guests when using a wifi adapter.
> > > You might try disabling wifi, and using wired ethernet.
> > > Jeff
> > > I wonder who was asked (running Fedora user ML on the internet forum not 
> > > via mailclient)
> > > If me was asked: VBox from Oracle downloaded: 
> > > VirtualBox-7.2-7.2.2_170484_fedora40-1.x86_64.rpm
> > > all is working here: Host connected via LAN or Wifi (VM always via LAN)
> > > The bizarre thing is that I can never reach the internet USB key from 
> > > Windows
> > ping 192.168.1.1
> > is never reachable.
> > On the other side
> > ping  10.40.0.1 (Bridge connection 1)
> > is always reachable in NAT of Bridged adapter
> > It seems that Windows is not configured properly
> 
> 
> tested a Win7 VM.
> 
> Host is conneted via Wifi only
> 
> configured in the "Vbox Manager" is:
> Nat Networks with IPv4: 10.0.2.0/24
> ===
> 
> in the "Win7 VM" is configured:
> Attached to: NAT (*NOT* "Nat Networks")
> Adapter: Intel Pro/1000
> in the win7 device manager I also see the Intel Pro/1000 as network device
> ===
> 
> in an terminal under win7 I have with the command "ipconfig":
> IPv4: 10.0.2.15
I have the same
> Standardgateway: 10.0.2.2
Default Gateway . . . . . . . . . : fe80::2%11
                                       10.0.2.2

> ===
> with this all the internet is reachable

ping 10.0.2.15 works


route

Interface List
 16...88 d7 f6 c5 a3 9d ......Intel(R) PRO/1000 MT Network Connection
  1...........................Software Loopback Interface 1
 13...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0         10.0.2.2        10.0.2.15     10
         10.0.2.0    255.255.255.0         On-link         10.0.2.15    266
        10.0.2.15  255.255.255.255         On-link         10.0.2.15    266
       10.0.2.255  255.255.255.255         On-link         10.0.2.15    266
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link         10.0.2.15    266
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
  255.255.255.255  255.255.255.255         On-link         10.0.2.15    266
===========================================================================
Persistent Routes:
  None

IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
 16    266 ::/0                     fe80::2
  1    306 ::1/128                  On-link
 16     18 fd17:625c:f037:2::/64    On-link
 16    266 fd17:625c:f037:2:31b2:dca2:5786:5d64/128
                                    On-link
 16    266 fd17:625c:f037:2:4134:2821:4b04:b8c9/128
                                    On-link
 16    266 fe80::/64                On-link
 16    266 fe80::4134:2821:4b04:b8c9/128
                                    On-link
  1    306 ff00::/8                 On-link
 16    266 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None


nslookup
Default Server:  UnKnown
Address:  10.0.2.3

Connection-specific DNS Suffix: .
Description: Intel(R) PRO/1000 MT Network Connection
Physical Address:  88-D7-F6-C5-A3-9D
DHCP Enabled: Yes
IPv4 Address: 10.0.2.15
IPv4 Subnet Mask: 255.255.255.0
Lease Obtained: Tuesday, September 30, 2025 8:46:05 PM
Lease Expires: Wednesday, October 01, 2025 8:46:06 PM
IPv4 Default Gateway: 10.0.2.2
IPv4 DHCP Server: 10.0.2.2
IPv4 DNS Server: 10.0.2.3
IPv4 WINS Server: 
NetBIOS over Tcpip Enabled: Yes
IPv6 Address: fd17:625c:f037:2:4134:2821:4b04:b8c9
Temporary IPv6 Address: fd17:625c:f037:2:31b2:dca2:5786:5d64
Link-local IPv6 Address: fe80::4134:2821:4b04:b8c9%16
IPv6 Default Gateway: fe80::2%16
IPv6 DNS Server


It seems that the DNS is set

Is it an issue with the driver?


Windows\system32\DRIVERS\E1G3032E.sys




> _______________________________________________
> 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
>
-- 
_______________________________________________
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