Guest VM is only using vmnet0

[sbudach]

Hi everybody,

I have just started with VMWare Fusion 2.0.2 (build 146107) and I am having problems configuring the network interfaces. That is, I have already configured Fusion to provide two bridged interfaces (en1 and en7) but I am unable to connect mv guest VM to en7.

I have searched the forum and tried to configure my vmx file accordingly, but either Fusion will tell me that it can't connect to the interfaces, if I use

ethernet0.connectionType = "custom"

or, the guest VM will habe both interfaces bound to vmnet0, if I use bridged mode.

Btw, if I set ethernet0.connectionType to "custom", Fusion will show this as a user defined config, which I can't alter, since its dimmed.

Any ideas anyone?

Thanks,

budy

[RDPetruska · Accepted solution]

When you define the connectionType as custom, you ALSO need to define the vmnet.

ethernet0.vnet = "VMnet2" as an example.

[sbudach]

Yes, I know. And that's exactly what I did. These are my current settings for ethernet0:

ethernet0.ignoreMACAddressConflict = "TRUE"

ethernet0.connectionType = "custom"

ethernet0.addressType = "generated"

ethernet0.generatedAddress = "00:0c:29:e3:86:1f"

ethernet0.generatedAddressOffset = "0"

ethernet0.linkStatePropagation.enable = "TRUE"

ethernet0.pciSlotNumber = "32"

ethernet0.wakeOnPcktRcv = "FALSE"

ethernet0.startConnected = "TRUE"

When I now open the guest in Fusion and take a look at the network settings it reads (translated from german): This interface might not work properly. Chose one of the available network options". At this time, there is a fourth radio button that reads: use user-defined settings, that is inactive.

If I start the VM Fusion tells me this: can't bind ti vnet-1: action not supported and vritual device ethernet0 will start up disconnected

Thanks,

budy

[RDPetruska]

You need to add the line I showed you into your vmx file as well. replace "VMnet2" with the appropriate VMnet you defined.

[sbudach]

Sorry, I copied the wrong text from my terminal window and there was that line missing.

This is how my networks looks like from the Fusion-side of things:

VM@Work Tokamak 2.0.0: Extended network scripting - Dave Parsons

Bridged networking on vmnet0 using en1 is running

Host-only/NAT networking on vmnet1 using 192.168.71.1/255.255.255.0 is running

DHCP server on vmnet1 is running

Bridged networking on vmnet2 using en7 is running

Host-only/NAT networking on vmnet8 using 192.168.220.1/255.255.255.0 is running

DHCP server on vmnet8 is running

NAT networking on vmnet8 is running

So, since I want to access en7, I'll have to use vmnet2.

This is the correct snippet from my current vmx file:

ethernet0.present = "TRUE"

ethernet0.vmnet = "VMnet2"

ethernet0.ignoreMACAddressConflict = "TRUE"

ethernet0.connectionType = "custom"

ethernet0.addressType = "generated"

ethernet0.generatedAddress = "00:0c:29:e3:86:1f"

ethernet0.generatedAddressOffset = "0"

ethernet0.linkStatePropagation.enable = "TRUE"

ethernet0.pciSlotNumber = "32"

ethernet0.wakeOnPcktRcv = "FALSE"

ethernet0.startConnected = "TRUE"

This is my current config, that gives me trouble.

Thanks,

budy

Message was edited by: sbudach: Ahh - now I see… it's vnet - not vmnet… let mr try this…