virtualbox.org

All,

I am trying to get an IP off of eth1(which is bridged to my wlan on host). This Mac requires a USB WiFi stick, so I do not know if that is part of the problem. I just know that my other VMs seem to work fine with the WLAN adapter.

I'm attaching all the information, I can think of that could attempt to isolate the issue. If more information is needed, please let me know, I've seen other articles that I've already tried but it still fails to get an IP. At the moment, I have my Mac on a wired connection and it is pulling an IP.

Also, I've tried the following "Attach to:" in the Network Settings of the overall Virtual Machine Settings.

Also, I've copied the the ifcfg-eth0 and renamed it as ifcfg-eth1, then deleted the 70-persistant-net.rules, rebooted and that did not work.


Bridged(Currently set with my wlan).
NAT
Internal
Host-Only
Generic

All are coming up with the same issue on Eth1.. I am not sure what I am doing wrong but most likely it is something simple that I am overlooking.

Below are the ifcfg-eth0, ifcfg-eth1, and the 70-persistent-net.rules config files.

Attached is the ifconfig -a results

__________The 70-persistent-net.rules:__________________
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.

# PCI device 0x8086:0x100e (e1000)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="08:00:27:76:55:c8", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x8086:0x100e (e1000)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="08:00:27:fe:fc:89", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
_____________________________________________________

______________ifcfg-eth0:______________
DEVICE=eth0
HWADDR=
TYPE=Ethernet
UUID=
ONBOOT=yes
NM_CONTROLLED=yes
BOOTPROTO=dhcp
_____________________________________

_________ifcfg-eth1__________
DEVICE=eth1
HWADDR=
TYPE=Ethernet
UUID=
ONBOOT=yes
NM_CONTROLLED=yes
BOOTPROTO=dhcp
____________________________

______ifup_____
ifup eth1

Determining IP information for eth1... failed.
_______________

Post the results of the following from the host.

Perryg wrote:Post the results of the following from the host.

Code: Select all

VBoxManage showvminfo <VM-name> | grep NIC

I may be doing something wrong.

My VB machine name is: CentOS-DNS(Possibly DynDNS as well)

My host is Mac OS X 10.8.5

When I type in the command I get:
_____________________________________________
ken$ VboxManage showvminfo "CentOS-DNS(Possibly DynDNS as well)" | grep NIC
VBoxManage: error: Could not find a registered machine named 'CentOS-DNS(Possibly DynDNS as well)'
VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBox, interface IVirtualBox, callee nsISupports
VBoxManage: error: Context: "FindMachine(Bstr(VMNameOrUuid).raw(), machine.asOutParam())" at line 2611 of file VBoxManageInfo.cpp
_____________________________________________

Type the following to see what the real name is:

Perryg wrote:Type the following to see what the real name is:

Code: Select all

VBoxManage list vms

Thank you for that. I had a hidden space in the name.

Here is the information you asked.

VboxManage showvminfo "CentOS-DNS(Possibly DynDNS as well) " | grep NIC
NIC 1: MAC: 080027FEFC89, Attachment: Bridged Interface 'en0: Ethernet', Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: allow-all, Bandwidth group: none
NIC 2: MAC: 0800277655C8, Attachment: Bridged Interface 'en1: RTL8191S WLAN Adapter ', Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: allow-all, Bandwidth group: none
NIC 3: disabled
NIC 4: disabled
NIC 5: disabled
NIC 6: disabled
NIC 7: disabled
NIC 8: disabled

Some wireless APs don't deal well with virtual machines. You can test to see if the cause is due to bonding though by disabling the NIC1 adapter and see if it will allow the bridge connection on NIC 2.

I'll try that and see if it works. I'm also going to take it a step further and see if Wireshark can trace where and if the request is dropping on the network. Though this is a virtual machine, it still has to connect to the router for an IP thus going across the network right?

Yes it does. You can use NAT and it would work but then you would have to deal with other issues.
Usually WRT (Linux based) APs do fine but most of the others don't.

Perryg wrote:Yes it does. You can use NAT and it would work but then you would have to deal with other issues.
Usually WRT (Linux based) APs do fine but most of the others don't.

I've already tried NAT and I'm not getting an IP still.. I know that works with other Linux Versions I am running, the only difference between those and this one is that the others are GUI based.