VirtualBox Internet

Caltrop · 08-02-2018, 11:59 AM

Linux Mint Host
Virtual Box Windows XP Guest

well I had internet at first
then something BAD happened and I had to reinstall the Linux OS

I installed VBox again & attached the backup VDI's
now when I run WinXP there is NO INTERNET

I remember seeing something in Linux Network Connections - a bridge
but I never looked at it closely
since the re-install that bridge is no longer there
the bridge was installed by VBox or when the WinXP driver was installed
I suspect the VBox Guest Add did the bridging

I assume that is what is causing my connection issue
VBox network was set to NAT

so my question is what do I bridge to in Linux?

here is what I have in WinXP Guest

Code:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

c:\>ipconfig /all

Windows IP Configuration

        Host Name . . . . . . . . . . . . : DRAGON-2
        Primary Dns Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter VBox Host:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Desktop Adapter
        Physical Address. . . . . . . . . : 08-00-27-52-75-4C
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 10.0.2.15
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 10.0.2.2
        DHCP Server . . . . . . . . . . . : 10.0.2.2
        DNS Servers . . . . . . . . . . . : 10.0.2.3
        Lease Obtained. . . . . . . . . . : Thu, 02 August 2018 11:28:24
        Lease Expires . . . . . . . . . . : Fri, 03 August 2018 11:28:24

c:\>

jefro · 08-02-2018, 01:20 PM

Appears to be NAT (that isn't bad as such)

DNS Servers . . . . . . . . . . . : 10.0.2.3

Think this should be either your local router or a public dns server maybe??
??

dolphin_oracle · 08-02-2018, 01:34 PM

check your virtualbox settings for the VM in question. Look on the networking tab, and make sure the specified network interface is still present. Might not be the same name since you reinstalled your linux host system.

Caltrop · 08-02-2018, 02:40 PM

continuing this on the virtualbox forum
https://forums.virtualbox.org/viewto...88958&p=426462

basically the networks were not ON in vbox prefs
I turned ON but still no NAT or Internet

It was working until that BAD happened & I had to re-install Linux Mint

there was that bridgded connection I noticed in Mint's 'nm-connection-editor'
like I said I never noticed what it bridged

I will post synopsis of final results here

michaelk · 08-02-2018, 03:25 PM

Quote:

In NAT mode, the guest network interface is assigned to the IPv4 range 10.0.x.0/24 by default where x corresponds to the instance of the NAT interface +2. So x is 2 when there is only one NAT instance active. In that case the guest is assigned to the address 10.0.2.15, the gateway is set to 10.0.2.2 and the name server can be found at 10.0.2.3.

According to the documentation it all looks normal but I agree with jefro and on my Windows host the guest DNS is the server as assigned by my DHCP server on my LAN.

It could be due to how your host is configured or if you are using a VPN or a proxy or maybe even dnsmsaq. Did you reinstall the same version of Mint?

A quick search shows this is not a unique problem although the cause might be. The following command might fix the problem. To use the host's DNS resolver try the command

VBoxManage modifyvm "VM name" --natdnshostresolver1 on

https://www.virtualbox.org/manual/ch09.html#nat-adv-dns

VirtualBox has several types of networking modes. NAT being the default.

https://www.virtualbox.org/manual/ch06.html

Caltrop · 08-03-2018, 08:07 AM

did not help:
VBoxManage modifyvm "VM name" --natdnshostresolver1 on

I know, I've read the manual & can't get anything working right.

Linux Mint
the 10.0.2.15 does not appear at all as it does in VBox WinXP
like I said the original installation had a bridged connection in Linux

and YES, this is the identical installation as before
except for using the old VBox VDI's

Installing VBox Guest Additions
-- or the WinXP Intel(R) PRO/1000 MT Desktop Adapter driver
-- or something else
setup a bridged connection in Linux, I would like to know what it was

Code:

netstat -i
Kernel Interface table
Iface   MTU Met   RX-OK RX-ERR RX-DRP RX-OVR    TX-OK TX-ERR TX-DRP TX-OVR Flg
eno1       1500 0         0      0      0 0             0      0      0      0 BMU
lo        65536 0     55200      0      0 0         55200      0      0      0 LRU
vboxnet0   1500 0         0      0      0 0           140      0      0      0 BMRU
wlo1       1500 0     30375      0      0 0         23674      0      0      0 BMRU

netstat -r
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
default         192.168.5.1     0.0.0.0         UG        0 0          0 wlo1
link-local      *               255.255.0.0     U         0 0          0 wlo1
192.168.5.0     *               255.255.255.0   U         0 0          0 wlo1
192.168.56.0    *               255.255.255.0   U         0 0          0 vboxnet0

ifconfig
eno1      Link encap:Ethernet  HWaddr 48:ba:4e:27:9c:3d  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:55208 errors:0 dropped:0 overruns:0 frame:0
          TX packets:55208 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:4509783 (4.5 MB)  TX bytes:4509783 (4.5 MB)

vboxnet0  Link encap:Ethernet  HWaddr 0a:00:27:00:00:00  
          inet addr:192.168.56.1  Bcast:192.168.56.255  Mask:255.255.255.0
          inet6 addr: fe80::800:27ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:150 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:21273 (21.2 KB)

wlo1      Link encap:Ethernet  HWaddr 90:61:ae:f7:58:2d  
          inet addr:192.168.5.151  Bcast:192.168.5.255  Mask:255.255.255.0
          inet6 addr: fe80::2dc1:1051:f9b4:5f17/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:30377 errors:0 dropped:0 overruns:0 frame:0
          TX packets:23684 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:32842172 (32.8 MB)  TX bytes:2914318 (2.9 MB)

Windows XP
NAT limited of no conectivity
Host Only does not work either

Code:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

c:\>ipconfig /all

Windows IP Configuration

        Host Name . . . . . . . . . . . . : DRAGON-2
        Primary Dns Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter VBox Host:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Desktop Adapter
        Physical Address. . . . . . . . . : 08-00-27-52-75-4C
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 10.0.2.15
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 10.0.2.2
        DHCP Server . . . . . . . . . . . : 10.0.2.2
        DNS Servers . . . . . . . . . . . : 10.0.2.3
        Lease Obtained. . . . . . . . . . : Fri, 03 August 2018 07:54:45
        Lease Expires . . . . . . . . . . : Sat, 04 August 2018 07:54:45

Ethernet adapter NAT:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Intel(R) PRO/1000 T Server Adapter #2
        Physical Address. . . . . . . . . : 08-00-27-90-D5-C2
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 0.0.0.0
        Subnet Mask . . . . . . . . . . . : 0.0.0.0
        Default Gateway . . . . . . . . . :
        DHCP Server . . . . . . . . . . . : 255.255.255.255

c:\>

MY GOD I HATE NETWORKS!
I went through this with Win98, then WinXP, & now Linux & WinXP again...
I deserve a PhD for this!
Or at least a Bachelor Degree.

michaelk · 08-03-2018, 10:49 AM

Basically bridged mode connects the guest directly on the LAN. It gets an IP address from the LAN and other computers can directly connect to it.

With NAT mode the guest is behind a virtual router. The guest IP address are assigned as previously posted. It basically works like a physical router.

Host-only creates a virtual network where guests can only connect between themselves and the host.

After rereading your thread I don't know if you ever really explained your problem. What do you mean by you can't get anything to work?

Caltrop · 08-09-2018, 02:28 PM

Got that working.
What Internet that works with WinXP anymore.

Don't really know what I did...

The BIG Problem was VBox -> File -> Preferences -> Network -> nothing was there, had to add networks

And only use NAT in the virtual device.

Things are working now... I HATE NETWORKS!

On to more Linux Problems...