interface en0 does not exist

Discussions related to using VirtualBox on Mac OS X hosts.
Post Reply
oneofthedamons
Posts: 15
Joined: 1. Mar 2019, 17:09

interface en0 does not exist

Post by oneofthedamons »

I've revived an old VM with an OS X 10.11 El Capitan guest under VirtualBox 6.0.10 running on MacOS 10.14.6 Mojave.

Everything has returned to normal except that the guest has no networking interfaces aside from lo0, gif0 and stf0.

VirtualBox is configured for the guest to have one NAT interface and it is showing:
Adapter 1 (NAT)
Cable: Connected
This VM has had some quirks and a history of multiple exports/imports — see viewtopic.php?f=8&t=92041

Thoughts?
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: interface en0 does not exist

Post by socratis »

oneofthedamons wrote:Everything has returned to normal except that the guest has no networking interfaces aside from lo0, gif0 and stf0.
Post the output when run from the host:
  • 
    ifconfig -a
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
oneofthedamons
Posts: 15
Joined: 1. Mar 2019, 17:09

Re: interface en0 does not exist

Post by oneofthedamons »

On the host running VirtualBox? Sure:

Code: Select all

$ ifconfig -a
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
	options=1203<RXCSUM,TXCSUM,TXSTATUS,SW_TIMESTAMP>
	inet 127.0.0.1 netmask 0xff000000 
	inet6 ::1 prefixlen 128 
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 
	nd6 options=201<PERFORMNUD,DAD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
EHC29: flags=0<> mtu 0
XHC20: flags=0<> mtu 0
EHC26: flags=0<> mtu 0
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
	lladdr 00:3e:e1:ff:fe:13:28:f4 
	media: autoselect <full-duplex>
	status: inactive
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=10b<RXCSUM,TXCSUM,VLAN_HWTAGGING,AV>
	ether 40:6c:8f:40:db:31 
	media: autoselect (none)
	status: inactive
en2: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=60<TSO4,TSO6>
	ether d2:00:11:32:8f:40 
	media: autoselect <full-duplex>
	status: inactive
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1491
	ether 7c:d1:c3:73:d9:0c 
	inet6 fe80::1c49:e929:40f3:2e99%en1 prefixlen 64 secured scopeid 0xa 
	inet 10.1.1.243 netmask 0xffffff00 broadcast 10.1.1.255
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect
	status: active
p2p0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2304
	ether 0e:d1:c3:73:d9:0c 
	media: autoselect
	status: inactive
awdl0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1484
	ether 32:3c:a5:54:92:4a 
	inet6 fe80::303c:a5ff:fe54:924a%awdl0 prefixlen 64 scopeid 0xc 
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect
	status: active
bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=63<RXCSUM,TXCSUM,TSO4,TSO6>
	ether d2:00:11:32:8f:40 
	Configuration:
		id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
		maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
		root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
		ipfilter disabled flags 0x2
	member: en2 flags=3<LEARNING,DISCOVER>
	        ifmaxaddr 0 port 9 priority 0 path cost 0
	media: <unknown type>
	status: inactive
utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 2000
	inet6 fe80::cd89:3726:c8e6:871e%utun0 prefixlen 64 scopeid 0xe 
	nd6 options=201<PERFORMNUD,DAD>
In case it's relevant, I have another VM on this host (guest is Windows 10) which uses a bridged interface. However, this host is not running and I've tried deactivating the bridge interface to see if that made a difference to the OS X El Capitan guest, but it did not.
fth0
Volunteer
Posts: 5677
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: interface en0 does not exist

Post by fth0 »

Since you have multiple active network interfaces on the host, maybe you have to bind the NAT network to a specific host IP address. Look in the VirtualBox User Manual for a small section called 'Binding NAT sockets to a specific interface'.
oneofthedamons
Posts: 15
Joined: 1. Mar 2019, 17:09

Re: interface en0 does not exist

Post by oneofthedamons »

Thanks for that, unfortunately it appears to be unsuccessful in this case. I've now included the diagnostic information requested in Minimum information needed for assistance (my bad).

Code: Select all

$ VBoxManage list vms
"Windows 10" {9766fc95-22f5-4210-848b-6dd7b543c7a6}
"MacOS Server 5.2" {0038f070-0611-4323-8351-51f119322a5e}
$ ifconfig en1
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1491
	ether 7c:d1:c3:73:d9:0c 
	inet6 fe80::1c49:e929:40f3:2e99%en1 prefixlen 64 secured scopeid 0xa 
	inet 172.16.17.2 netmask 0xffffff00 broadcast 172.16.17.255
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect
	status: active
$ VBoxManage modifyvm 0038f070-0611-4323-8351-51f119322a5e --natbindip1 "172.16.17.2"
$ VBoxManage showvminfo 0038f070-0611-4323-8351-51f119322a5e
Name:                        MacOS Server 5.2
Groups:                      /
Guest OS:                    Mac OS X 10.11 El Capitan (64-bit)
UUID:                        0038f070-0611-4323-8351-51f119322a5e
Config file:                 /Volumes/SDXC/El Capitan VM/MacOS Server 5.2/MacOS Server 5.2.vbox
Snapshot folder:             /Volumes/SDXC/El Capitan VM/MacOS Server 5.2/Snapshots
Log folder:                  /Volumes/SDXC/El Capitan VM/MacOS Server 5.2/Logs
Hardware UUID:               0038f070-0611-4323-8351-51f119322a5e
Memory size                  2048MB
Page Fusion:                 disabled
VRAM size:                   128MB
CPU exec cap:                100%
HPET:                        disabled
CPUProfile:                  host
Chipset:                     ich9
Firmware:                    EFI
Number of CPUs:              1
PAE:                         enabled
Long Mode:                   enabled
Triple Fault Reset:          disabled
APIC:                        enabled
X2APIC:                      disabled
Nested VT-x/AMD-V:           disabled
CPUID Portability Level:     0
CPUID overrides:             None
Boot menu mode:              message and menu
Boot Device 1:               Floppy
Boot Device 2:               DVD
Boot Device 3:               HardDisk
Boot Device 4:               Not Assigned
ACPI:                        enabled
IOAPIC:                      enabled
BIOS APIC mode:              APIC
Time offset:                 0ms
RTC:                         UTC
Hardw. virt.ext:             enabled
Nested Paging:               enabled
Large Pages:                 enabled
VT-x VPID:                   enabled
VT-x unr. exec.:             enabled
Paravirt. Provider:          Default
Effective Paravirt. Prov.:   Minimal
State:                       powered off (since 2019-08-27T03:50:53.168000000)
Monitor count:               1
3D Acceleration:             disabled
2D Video Acceleration:       disabled
Teleporter Enabled:          disabled
Teleporter Port:             0
Teleporter Address:          
Teleporter Password:         
Tracing Enabled:             disabled
Allow Tracing to Access VM:  disabled
Tracing Configuration:       
Autostart Enabled:           disabled
Autostart Delay:             0
Default Frontend:            
Storage Controller Name (0):            SATA
Storage Controller Type (0):            IntelAhci
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0):  30
Storage Controller Port Count (0):      3
Storage Controller Bootable (0):        on
SATA (0, 0): /Volumes/SDXC/El Capitan VM/MacOS Server 5.2/Macintosh HD.vdi (UUID: 807de311-a516-4a03-9d82-8e2b57e80304)
SATA (2, 0): Empty
NIC 1:                       MAC: 0800277E2D50, Attachment: NAT, Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 1 Settings:  MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, receive: 64)
NIC 2:                       disabled
NIC 3:                       disabled
NIC 4:                       disabled
NIC 5:                       disabled
NIC 6:                       disabled
NIC 7:                       disabled
NIC 8:                       disabled
NIC 9:                       disabled
NIC 10:                      disabled
NIC 11:                      disabled
NIC 12:                      disabled
NIC 13:                      disabled
NIC 14:                      disabled
NIC 15:                      disabled
NIC 16:                      disabled
NIC 17:                      disabled
NIC 18:                      disabled
NIC 19:                      disabled
NIC 20:                      disabled
NIC 21:                      disabled
NIC 22:                      disabled
NIC 23:                      disabled
NIC 24:                      disabled
NIC 25:                      disabled
NIC 26:                      disabled
NIC 27:                      disabled
NIC 28:                      disabled
NIC 29:                      disabled
NIC 30:                      disabled
NIC 31:                      disabled
NIC 32:                      disabled
NIC 33:                      disabled
NIC 34:                      disabled
NIC 35:                      disabled
NIC 36:                      disabled
Pointing Device:             USB Multi-Touch
Keyboard Device:             USB Keyboard
UART 1:                      disabled
UART 2:                      disabled
UART 3:                      disabled
UART 4:                      disabled
LPT 1:                       disabled
LPT 2:                       disabled
Audio:                       enabled (Driver: CoreAudio, Controller: AC97, Codec: STAC9700)
Audio playback:              disabled
Audio capture:               disabled
Clipboard Mode:              GuestToHost
Drag and drop Mode:          disabled
VRDE:                        disabled
OHCI USB:                    enabled
EHCI USB:                    disabled
xHCI USB:                    disabled

USB Device Filters:

<none>

Bandwidth groups:  <none>

Shared folders:<none>

Capturing:                   active
Capture audio:               not active
Capture screens:             0
Capture file:                /Volumes/SDXC/El Capitan VM/MacOS Server 5.2/MacOS Server 5.2.webm
Capture dimensions:          1024x768
Capture rate:                512kbps
Capture FPS:                 25kbps
Capture options:             vc_enabled=true,ac_enabled=false,ac_profile=med

Guest:

Configured memory balloon size: 0MB

Changing the interface type to bridge has no effect, either.
Attachments
MacOS Server 5.2-2019-08-27-13-20-54.log.zip
VM log file
(29.86 KiB) Downloaded 13 times
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: interface en0 does not exist

Post by socratis »

00:00:01.939503 Guest OS type: 'MacOS1011_64'
00:00:01.989076 File system of '/Volumes/SDXC/El Capitan VM/MacOS Server 5.2/Macintosh HD.vdi' is unknown
If my calculations are correct, and you named the VM according to what it is, MacOS Server 5.2 is in fact OSX 10.12, not 10.11. Please fix that.
oneofthedamons wrote:the guest has no networking interfaces aside from lo0, gif0 and stf0. VirtualBox is configured for the guest to have one NAT interface and it is showing:
I'm sorry, I misread the first time what you said, and I asked about the "ifconfig" output from your host. Can you post the output of "ifconfig -a" from the guest? Does that mean that you don't have a network interface in your System Preferences » Network? Because I do see one in the VM configuration:
[quote=""VBoxManage showvminfo 0038f070-0611-4323-8351-51f119322a5e""]

Code: Select all

NIC 1:                       MAC: 0800277E2D50, Attachment: NAT, Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
[/quote][quote=""VBox.log""]
00:00:02.100914 [/Devices/e1000/0/LUN#0/Config/] (level 5)
00:00:02.100916   IfPolicyPromisc      <string>  = "deny" (cb=5)
00:00:02.100916   IgnoreConnectFailure <integer> = 0x0000000000000000 (0)
00:00:02.100917   Network              <string>  = "HostInterfaceNetworking-en1" (cb=28)
00:00:02.100918   SharedMacOnWire      <integer> = 0x0000000000000001 (1)
00:00:02.100919   Trunk                <string>  = "en1" (cb=4)
00:00:02.100919   TrunkType            <integer> = 0x0000000000000003 (3)
[/quote]... which is connected via Bridged-over-en1, and not NAT as you said.

So, let's try to tackle this from the beginning, shall we? As I said, I'd like to see the "ifconfig -a" from the guest, and a screenshot of your System Preferences » Network, again from the guest. Please crop the image accordingly, I don't want to see your whole desktop... ;)
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
oneofthedamons
Posts: 15
Joined: 1. Mar 2019, 17:09

Re: interface en0 does not exist

Post by oneofthedamons »

socratis wrote:If my calculations are correct, and you named the VM according to what it is, MacOS Server 5.2 is in fact OSX 10.12, not 10.11. Please fix that.
Nup, it's Server 5.2 running on OS X 10.11. But given Apple's sub-optimal support of Server in recent years, your confusion is understandable :wink:
Software versions
Software versions
Screen Shot 2019-08-27 at 3.33.59 pm.jpg (125.02 KiB) Viewed 3902 times
socratis wrote:Can you post the output of "ifconfig -a" from the guest?
Network config
Network config
Screen Shot 2019-08-27 at 3.47.30 pm.jpg (122.88 KiB) Viewed 3902 times
socratis wrote:... which is connected via Bridged-over-en1, and not NAT as you said.
Yep, sorry about that. I changed the virtual NIC type from NAT to bridge at some stage to see if that helped (it didn't).

One other observation, perhaps irrelevant: neither VirtualBox's Shared Folders nor Shared Clipboard nor Drag and Drop are working. I think Shared Folders uses the networking subsystem so perhaps that's to be expected; unsure about the others.
fth0
Volunteer
Posts: 5677
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: interface en0 does not exist

Post by fth0 »

I've noticed that SharedMacOnWire is set, which is typically used on wireless network interfaces. Is en1 a wireless network interface?

Additionally, en1 has a MTU of 1491. I've never seen this odd value before ... it could be something like a trailer mode that VirtualBox possibly cannot handle.
oneofthedamons
Posts: 15
Joined: 1. Mar 2019, 17:09

Re: interface en0 does not exist

Post by oneofthedamons »

fth0 wrote:I've noticed that SharedMacOnWire is set, which is typically used on wireless network interfaces. Is en1 a wireless network interface?
Yes en1 is the WiFi ("AirPort") interface. On the host:

Code: Select all

$ networksetup -listallhardwareports

Hardware Port: sierravsp
Device: sierravsp
Ethernet Address: N/A

Hardware Port: Ethernet
Device: en0
Ethernet Address: 40:6c:8f:40:db:31

Hardware Port: FireWire
Device: fw0
Ethernet Address: 00:3e:e1:ff:fe:13:28:f4

Hardware Port: Wi-Fi
Device: en1
Ethernet Address: 7c:d1:c3:73:d9:0c

Hardware Port: Bluetooth PAN
Device: en3
Ethernet Address: 7c:d1:c3:73:d9:0d

Hardware Port: Thunderbolt 1
Device: en2
Ethernet Address: d2:00:11:32:8f:40

Hardware Port: Thunderbolt Bridge
Device: bridge0
Ethernet Address: d2:00:11:32:8f:40

VLAN Configurations
===================
OS X reports no NICs on the VirtualBox guest:

Code: Select all

$ networksetup -listallhardwareports

VLAN Configurations
===================
fth0 wrote:Additionally, en1 has a MTU of 1491. I've never seen this odd value before ... it could be something like a trailer mode that VirtualBox possibly cannot handle.
Interesting! I had this manually set — and I have absolutely no recollection why! It was possibly a connectivity troubleshooting setting (I've been — and remain — behind some truly shitty internet connections, generally double-NATed and previously as slow as a 8000/384 Kbps up/down ADSL connection, although thankfully this has improved to a better although still sub-par fixed wireless connection).

However, changing it back to automatic (default MTU 1500) has had no effect.
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: interface en0 does not exist

Post by socratis »

I think you're missing the bigger picture here... There's a fundamental issue with the guest; even though an Ethernet connection is showing in the guest's System Preferences » Networking, this doesn't show in the guest's "ifconfing -a". Something is screwed up royally in the guest.

I would delete that Ethernet interface/service/connection, reboot the guest and add a new connection. You should have a single "Ethernet" option available if you use the (+) to add it. Then run "ifconfig -a" from the guest again.

@fth0
I don't think that this has anything to do with the host's settings/mappings/MTUs/bindings or anything like that. This should work right out of the box, unless there's been some unusual setup configuration in the guest. It doesn't matter if the network adapter is set to NotAttached, NAT, NATnetwork, Bridged, Internal, or HostOnly (haven't tried the Generic); the guest should always have a en0 adapter, if there's one in the VM configuration, no matter what. If it doesn't, something is screwed up in the guest, not in VirtualBox.

@oneofthedamons
Why do I see a Bluetooth adapter in there? Did you capture your host's Bluetooth adapter. You don't have a USB filter, so I assume that you used the on-the-fly method from the menu Devices » USB » your Bluetooth adapter?

How did you install the ServerOS? On top of an existing 10.11.6 installation? Was 10.11.6 working? Can you try with a fresh VM?
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
fth0
Volunteer
Posts: 5677
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: interface en0 does not exist

Post by fth0 »

socratis wrote:I don't think that this has anything to do with the host's settings/mappings/MTUs/bindings or anything like that. This should work right out of the box, unless there's been some unusual setup configuration in the guest. It doesn't matter if the network adapter is set to NotAttached, NAT, NATnetwork, Bridged, Internal, or HostOnly (haven't tried the Generic); the guest should always have a en0 adapter, if there's one in the VM configuration, no matter what. If it doesn't, something is screwed up in the guest, not in VirtualBox.
I tend to agree with you here. I was just irritated by the MTU value of 1491 and my train of thought was that maybe the host interface has some special properties the VirtualBox code would not expect and therefore fail to offer the guest interface to the guest, especially in bridged mode, where the netfilter driver needs an active host interface. And the other aspect was the combination of bridged mode with a wireless interface.

@oneofthedamons:
If you need to manually set the MTU value for an ADSL connection, you can use 1492 (ADSL often has a PPPoE overhead of 8 bytes).
Post Reply