LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 04-06-2009, 09:20 PM   #1
DeepSeaNautilus
Member
 
Registered: Jul 2008
Posts: 65

Rep: Reputation: 15
After installing virtual box , eth0 and ath0 interfaces were lost


Hello, I recently installed virtual box in my ubuntu 8.10 netbook, because its free and I want to use to virtualize win xp in my machine. I downloaded the .deb file from virtual box homepage, it asked me if I wanted to compile the headers and I said yes. It seemed to install ok, but then I realized that my eth0 and my ath0 network interfaces were lost. I tried to use ifconfig eth0 up to configure my ethernet connection, but It is not working. When I try to use wlanconfig for creating ath0 interface, I get an ioctl error message. Can anyone help please?
 
Old 04-07-2009, 04:00 PM   #2
irishbitte
Senior Member
 
Registered: Oct 2007
Location: Brighton, UK
Distribution: Ubuntu Hardy, Ubuntu Jaunty, Eeebuntu, Debian, SME-Server
Posts: 1,213
Blog Entries: 1

Rep: Reputation: 87
Do you know what version of VirtualBox you are running? VB does not yet play very well with wireless chipsets, and I have heard of your problem before.

I'm wondering whether your problem is actually that you setup your virtual machine to use host interface networking, that is how this problem is generally caused. If it is, then change the network settings on your VM to use NAT. If you have any questions, post and I'll try to help.
 
Old 04-07-2009, 08:50 PM   #3
DeepSeaNautilus
Member
 
Registered: Jul 2008
Posts: 65

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by irishbitte View Post
Do you know what version of VirtualBox you are running? VB does not yet play very well with wireless chipsets, and I have heard of your problem before.

I'm wondering whether your problem is actually that you setup your virtual machine to use host interface networking, that is how this problem is generally caused. If it is, then change the network settings on your VM to use NAT. If you have any questions, post and I'll try to help.
Yes, the vmware version I am using is graphic user interface 2.1.4.
I donīt know how to change my network settings in my vm to use nat, could you tell me?
 
Old 04-09-2009, 11:35 PM   #4
irishbitte
Senior Member
 
Registered: Oct 2007
Location: Brighton, UK
Distribution: Ubuntu Hardy, Ubuntu Jaunty, Eeebuntu, Debian, SME-Server
Posts: 1,213
Blog Entries: 1

Rep: Reputation: 87
When you open the VirtualBox GUI, highlight the machine you want to amend settings for, then go to 'Network' in blue writing on the right of the screen. Click this, and a new window will open: Under 'Adapter 0', select 'NAT' for the 'Attached To' menu. Then click ok, and power up the VM. Now, this is the default setting in VB, so if you haven't already changed it, it's probably not your problem!
 
Old 04-12-2009, 11:43 PM   #5
DeepSeaNautilus
Member
 
Registered: Jul 2008
Posts: 65

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by irishbitte View Post
When you open the VirtualBox GUI, highlight the machine you want to amend settings for, then go to 'Network' in blue writing on the right of the screen. Click this, and a new window will open: Under 'Adapter 0', select 'NAT' for the 'Attached To' menu. Then click ok, and power up the VM. Now, this is the default setting in VB, so if you haven't already changed it, it's probably not your problem!
I still dont have any virtual machine installed. Its a blank install. I havent yet installed any host operating system. Do you think that if I install a host operating system and then choose nat, I will get my network interfaces?
 
Old 04-13-2009, 01:08 PM   #6
irishbitte
Senior Member
 
Registered: Oct 2007
Location: Brighton, UK
Distribution: Ubuntu Hardy, Ubuntu Jaunty, Eeebuntu, Debian, SME-Server
Posts: 1,213
Blog Entries: 1

Rep: Reputation: 87
Well, I doubt putting a guest OS on will change the properties of the host. If you check up on what VirtualBox 2.1.4 does, what you find is that it installs new drivers for your network interfaces. This may be solved be downloading the newest version of VIrtualBox 2.2.0, and installing it in place of 2.1.4. That is the course of action I recommend, since VirtualBox will have done more work on their drivers.

Here is the link for the downloads:http://www.virtualbox.org/wiki/Linux_Downloads

Please note that you will have to uninstall VB 2.1.4 before installing 2.2.0
 
Old 04-13-2009, 02:58 PM   #7
baig
Member
 
Registered: Nov 2008
Location: وادی ھنزہ
Distribution: Solaris 5.10, Debian Server 5.2, CentOS 5.6
Posts: 226
Blog Entries: 3

Rep: Reputation: 38
I don't think installing latest virtual box will solver your network problem.. Because Virtual box doesn't modifies any network setting for your host Linux OS.

Setting up your guest network settings to NAT is another story.

what do you get on

ifconfig

or

iwconfig (if using Wireless)

Cheers!!
 
Old 04-13-2009, 07:01 PM   #8
irishbitte
Senior Member
 
Registered: Oct 2007
Location: Brighton, UK
Distribution: Ubuntu Hardy, Ubuntu Jaunty, Eeebuntu, Debian, SME-Server
Posts: 1,213
Blog Entries: 1

Rep: Reputation: 87
to baig:
Quote:
Because Virtual box doesn't modifies any network setting for your host Linux OS.
I'm afraid you're wrong there, VB does modify your network interfaces, as of version 2.1.2. They done it in order to simplify host interface networking. The fact is, the network interfaces file is stored in VirtualBox's own configuration. It's similar to VMWare server in this regard.
 
Old 04-13-2009, 10:04 PM   #9
DeepSeaNautilus
Member
 
Registered: Jul 2008
Posts: 65

Original Poster
Rep: Reputation: 15
I also installed the same virtual box version at the office in ubuntu 8.04, but it gave me no problems, I am thinking that the problem could be ubuntu 8.10 or that I installed it using a wubi installation, but none of these gave me any problem in the past, what do you think?

Last edited by DeepSeaNautilus; 04-15-2009 at 12:14 AM.
 
Old 04-14-2009, 01:04 PM   #10
baig
Member
 
Registered: Nov 2008
Location: وادی ھنزہ
Distribution: Solaris 5.10, Debian Server 5.2, CentOS 5.6
Posts: 226
Blog Entries: 3

Rep: Reputation: 38
Quote:
Originally Posted by irishbitte View Post
to baig: I'm afraid you're wrong there, VB does modify your network interfaces, as of version 2.1.2. They done it in order to simplify host interface networking. The fact is, the network interfaces file is stored in VirtualBox's own configuration. It's similar to VMWare server in this regard.
You may be right but In what sense network interfaces get change? I don't see any change of config files for network interfaces on my CentOS box?

Cheers!!
 
Old 04-18-2009, 05:42 PM   #11
irishbitte
Senior Member
 
Registered: Oct 2007
Location: Brighton, UK
Distribution: Ubuntu Hardy, Ubuntu Jaunty, Eeebuntu, Debian, SME-Server
Posts: 1,213
Blog Entries: 1

Rep: Reputation: 87
Quote:
You may be right but In what sense network interfaces get change? I don't see any change of config files for network interfaces on my CentOS box?

Cheers!!
To be honest, I don't know the nuts and bolts of it, I'm not involved in programming it or anything. It does declare network bridges, and installs virtual network card drivers. Your old config files are not touched, and won't be, however, your machines network settings are running from a different config file.

It's similar behaviour to VMWare, and they are trying to make VB a really viable alternative to VMWare.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
eth0 and ath0? or eth0 and ath1? tfrei Slackware 5 01-08-2009 08:41 PM
Why does disconnecting eth0 also disconnect ath0 1jnike Linux - Wireless Networking 3 02-01-2007 09:49 PM
eth0 virtual interfaces & iptables Jukas Linux - Networking 2 07-27-2006 12:13 PM
dhcpcd ath0 fails, works for eth0 Josh328 Linux - Wireless Networking 7 02-07-2006 10:45 PM
After installing Sarge it lost the eth0 spiri Debian 8 05-01-2004 08:45 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 03:02 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration