Problem with host-only network

Discussions related to using VirtualBox on Linux hosts.
Post Reply
TPJ
Posts: 4
Joined: 27. Aug 2009, 13:45
Primary OS: Linux other
VBox Version: OSE other
Guest OSses: Windows XP Home, Linux

Problem with host-only network

Post by TPJ »

I'd like my VM to use host-only network, but I can't set my VM to use the host-only adapter:

Image

There aren't any host-only networks available:

Image

And I can't add a new ones:

Image

Here are outputs from my console (on the host):

Code: Select all

$ VBoxManage list dhcpservers
VirtualBox Command Line Management Interface Version 3.0.0
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.

NetworkName:    HostInterfaceNetworking-vboxnet0
IP:             192.168.56.2
NetworkMask:    255.255.255.0
lowerIPAddress: 192.168.56.3
upperIPAddress: 192.168.56.255
Enabled:        Yes

$ VBoxManage list hostonlyifs
VirtualBox Command Line Management Interface Version 3.0.0
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.

$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:1D:60:08:EB:B7  
          inet addr:195.140.154.99  Bcast:195.140.155.255  Mask:255.255.254.0
          inet6 addr: fe80::21d:60ff:fe08:ebb7/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:77127 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5235 errors:0 dropped:0 overruns:0 carrier:2
          collisions:0 txqueuelen:1000 
          RX bytes:8305144 (7.9 Mb)  TX bytes:1209587 (1.1 Mb)

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:16436  Metric:1
          RX packets:295 errors:0 dropped:0 overruns:0 frame:0
          TX packets:295 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:8699 (8.4 Kb)  TX bytes:8699 (8.4 Kb)
And here's my output from my guest:

Image

The rc.vboxnet is run and it didn't report any problems. I haven't found any /etc/vbox/interfaces file, though.
Top
Sasquatch
Volunteer
Posts: 17798
Joined: 17. Mar 2008, 13:41
Primary OS: Debian other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows XP, Windows 7, Linux
Location: /dev/random

Re: Problem with host-only network

Post by Sasquatch »

What does ifconfig -a say? And are you a member of the vboxusers group? You must be a member of that group to have a little problems with VB as possible. I'm guessing that you need to be a member before you can see or use the NIC.
Read the Forum Posting Guide before opening a topic.
VirtualBox FAQ: Check this before asking questions.
Online User Manual: A must read if you want to know what we're talking about.
Howto: Install Linux Guest Additions
Howto: Use Shared Folders on Linux Guest
See the Tutorials and FAQ section at the top of the Forum for more guides.
Try searching the forums first with Google and add the site filter for this forum.
E.g. install guest additions site:forums.virtualbox.org

Retired from this Forum since OSSO introduction.
Top
TPJ
Posts: 4
Joined: 27. Aug 2009, 13:45
Primary OS: Linux other
VBox Version: OSE other
Guest OSses: Windows XP Home, Linux

Re: Problem with host-only network

Post by TPJ »

I am a member of the vboxusers group.

Here's my ifconfig -a (executed on my host):

Code: Select all

$ ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:1D:60:08:EB:B7  
          inet addr:195.140.154.99  Bcast:195.140.155.255  Mask:255.255.254.0
          inet6 addr: fe80::21d:60ff:fe08:ebb7/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:156484 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7507 errors:0 dropped:0 overruns:0 carrier:2
          collisions:0 txqueuelen:1000 
          RX bytes:18838253 (17.9 Mb)  TX bytes:1279294 (1.2 Mb)

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:16436  Metric:1
          RX packets:26 errors:0 dropped:0 overruns:0 frame:0
          TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:3950 (3.8 Kb)  TX bytes:3950 (3.8 Kb)

wlan0     Link encap:Ethernet  HWaddr 00:1B:77:DA:05:BC  
          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)

wmaster0  Link encap:UNSPEC  HWaddr 00-1B-77-DA-05-BC-00-00-00-00-00-00-00-00-00-00  
          [NO FLAGS]  MTU:0  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)
ifconfig -a, executed on my guest (yes, I'm a noob when it comes to network), doesn't differ from the output I have already posted.

And one more thing. I haven't installed any guest additions yet. If it's needed, I missed it while studying docs.
Top
Sasquatch
Volunteer
Posts: 17798
Joined: 17. Mar 2008, 13:41
Primary OS: Debian other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows XP, Windows 7, Linux
Location: /dev/random

Re: Problem with host-only network

Post by Sasquatch »

Here is the output on my system, where you can see the difference. The last output is when I added and configured the Host-Only adapter(s). You might want to reinstall VB. Which version do you use, the PUEL one (from the website) or the OSE from the distro repositories?

Code: Select all

$ ifconfig
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:16436  Metric:1
          RX packets:6 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:340 (340.0 B)  TX bytes:340 (340.0 B)

marvell   Link encap:Ethernet  HWaddr 00:11:09:c1:28:07  
          inet addr:192.168.1.251  Bcast:192.168.1.255  Mask:255.255.255.248
          inet6 addr: fe80::211:9ff:fec1:2807/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2493810 errors:0 dropped:2 overruns:0 frame:0
          TX packets:2257677 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1881859913 (1.8 GB)  TX bytes:2524924645 (2.5 GB)
          Interrupt:17 

nvidia    Link encap:Ethernet  HWaddr 00:11:09:c1:28:06  
          inet addr:192.168.0.2  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::211:9ff:fec1:2806/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:462 errors:0 dropped:0 overruns:0 frame:0
          TX packets:356 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:193821 (193.8 KB)  TX bytes:378781 (378.7 KB)
          Interrupt:23 Base address:0xe000

Code: Select all

$ ifconfig -a
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:16436  Metric:1
          RX packets:6 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:340 (340.0 B)  TX bytes:340 (340.0 B)

marvell   Link encap:Ethernet  HWaddr 00:11:09:c1:28:07  
          inet addr:192.168.1.251  Bcast:192.168.1.255  Mask:255.255.255.248
          inet6 addr: fe80::211:9ff:fec1:2807/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2494067 errors:0 dropped:2 overruns:0 frame:0
          TX packets:2257957 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1881933771 (1.8 GB)  TX bytes:2525362104 (2.5 GB)
          Interrupt:17 

nvidia    Link encap:Ethernet  HWaddr 00:11:09:c1:28:06  
          inet addr:192.168.0.2  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::211:9ff:fec1:2806/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:462 errors:0 dropped:0 overruns:0 frame:0
          TX packets:356 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:193821 (193.8 KB)  TX bytes:378781 (378.7 KB)
          Interrupt:23 Base address:0xe000 

vboxnet0  Link encap:Ethernet  HWaddr 0a:00:27:00:00:00  
          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)

vboxnet1  Link encap:Ethernet  HWaddr 0a:00:27:00:00:01  
          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)

wlan      Link encap:Ethernet  HWaddr 00:00:00:00:00:00  
          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)

wmaster0  Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          [NO FLAGS]  MTU:0  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)

Code: Select all

$ ifconfig -a
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:16436  Metric:1
          RX packets:6 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:340 (340.0 B)  TX bytes:340 (340.0 B)

marvell   Link encap:Ethernet  HWaddr 00:11:09:c1:28:07  
          inet addr:192.168.1.251  Bcast:192.168.1.255  Mask:255.255.255.248
          inet6 addr: fe80::211:9ff:fec1:2807/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2498753 errors:0 dropped:2 overruns:0 frame:0
          TX packets:2263110 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1883389791 (1.8 GB)  TX bytes:2533268810 (2.5 GB)
          Interrupt:17 

nvidia    Link encap:Ethernet  HWaddr 00:11:09:c1:28:06  
          inet addr:192.168.0.2  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::211:9ff:fec1:2806/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:462 errors:0 dropped:0 overruns:0 frame:0
          TX packets:356 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:193821 (193.8 KB)  TX bytes:378781 (378.7 KB)
          Interrupt:23 Base address:0xe000 

vboxnet0  Link encap:Ethernet  HWaddr 0a:00:27:00:00:00  
          inet addr:172.25.0.1  Bcast:172.25.255.255  Mask:255.255.0.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:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:1814 (1.8 KB)

vboxnet1  Link encap:Ethernet  HWaddr 0a:00:27:00:00:01  
          inet addr:172.25.0.2  Bcast:172.25.255.255  Mask:255.255.0.0
          inet6 addr: fe80::800:27ff:fe00:1/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:1814 (1.8 KB)

wlan      Link encap:Ethernet  HWaddr 00:00:00:00:00:00  
          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)

wmaster0  Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          [NO FLAGS]  MTU:0  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)
[paranoid]I obscured my wireless MAC address, you never know if someone nearby reads this and uses it to access my wireless network[/paranoid].

The Host-Only adapters are listed in the VirtualBox.xml file as extra data:

Code: Select all

      <ExtraDataItem name="HostOnly/vboxnet0/IPAddress" value="172.25.0.1"/>
      <ExtraDataItem name="HostOnly/vboxnet0/IPNetMask" value="255.255.0.0"/>
      <ExtraDataItem name="HostOnly/vboxnet1/IPAddress" value="172.25.0.2"/>
      <ExtraDataItem name="HostOnly/vboxnet1/IPNetMask" value="255.255.0.0"/>
Read the Forum Posting Guide before opening a topic.
VirtualBox FAQ: Check this before asking questions.
Online User Manual: A must read if you want to know what we're talking about.
Howto: Install Linux Guest Additions
Howto: Use Shared Folders on Linux Guest
See the Tutorials and FAQ section at the top of the Forum for more guides.
Try searching the forums first with Google and add the site filter for this forum.
E.g. install guest additions site:forums.virtualbox.org

Retired from this Forum since OSSO introduction.
Top
TPJ
Posts: 4
Joined: 27. Aug 2009, 13:45
Primary OS: Linux other
VBox Version: OSE other
Guest OSses: Windows XP Home, Linux

Re: Problem with host-only network

Post by TPJ »

I have reinstalled the latet VB version (POE). Nothing has changed.

There are no entries about vboxnet0 in my VB.xml file.
Top
Sasquatch
Volunteer
Posts: 17798
Joined: 17. Mar 2008, 13:41
Primary OS: Debian other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows XP, Windows 7, Linux
Location: /dev/random

Re: Problem with host-only network

Post by Sasquatch »

I noted these entries so you could copy them to your own XML file (be sure that no instance of VB is running). Since you already have a VM or two, I won't recommend you to start with clean settings, as you would loose the VM(s) :P.
Read the Forum Posting Guide before opening a topic.
VirtualBox FAQ: Check this before asking questions.
Online User Manual: A must read if you want to know what we're talking about.
Howto: Install Linux Guest Additions
Howto: Use Shared Folders on Linux Guest
See the Tutorials and FAQ section at the top of the Forum for more guides.
Try searching the forums first with Google and add the site filter for this forum.
E.g. install guest additions site:forums.virtualbox.org

Retired from this Forum since OSSO introduction.
Top
TPJ
Posts: 4
Joined: 27. Aug 2009, 13:45
Primary OS: Linux other
VBox Version: OSE other
Guest OSses: Windows XP Home, Linux

Re: Problem with host-only network

Post by TPJ »

Sasquatch wrote:I noted these entries so you could copy them to your own XML file (be sure that no instance of VB is running).
Well, I have done it, although I was *sure* it won't help. It didn't.

(Why I was so sure? Because the content of a file in *my home directory* shouldn't affect the net interfaces available in my system.)

I'm not sure, what is wrong. Perhaps it's because I had an old (2.x) configuration available when I was installing the new VB version?
Top
Sasquatch
Volunteer
Posts: 17798
Joined: 17. Mar 2008, 13:41
Primary OS: Debian other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows XP, Windows 7, Linux
Location: /dev/random

Re: Problem with host-only network

Post by Sasquatch »

I had VB 2 running too and upgraded each time, so that's not the problem. Also, I thought it might work adding the lines to your config file, because I didn't see any instance of vboxnet0 in /etc, only in my own config file. However, I created a second vboxnet, vboxnet1, and it doesn't appear in my ifconfig -a list, nor in my VB prefs. It's 'forgotton' when I close VB or shut down my system. It's still in my config file though.
Read the Forum Posting Guide before opening a topic.
VirtualBox FAQ: Check this before asking questions.
Online User Manual: A must read if you want to know what we're talking about.
Howto: Install Linux Guest Additions
Howto: Use Shared Folders on Linux Guest
See the Tutorials and FAQ section at the top of the Forum for more guides.
Try searching the forums first with Google and add the site filter for this forum.
E.g. install guest additions site:forums.virtualbox.org

Retired from this Forum since OSSO introduction.
Top
Post Reply

Return to “VirtualBox on Linux Hosts”