Quantcast
Channel: VMware Communities : All Content - Workstation Player
Viewing all articles
Browse latest Browse all 5660

Configure automatic bridging in Player 7 installed on Debian/GNU Linux 7

$
0
0

Hello everybody,

 

I'd like to run Player 7 on a host running Debian GNU/Linux 7. This host has two hardware NICs. The VM is configured to use a virtual NIC, that is bridged. Unfortunately the automatic bridging of Player 7 seems to make some trouble in my scenario. I think I have to specify one NIC explicitly and exclude the other one to be used in automatic bridging.

 

Player 7 running on Windows 7 offers an option to achieve this. Under "Virtual Machines -> Network adapter -> Configure Adapters" a list of NICs physically installed in the host is available. I can check or uncheck certain adapters to be part of the automatic bridging.

 

Running Player 7 on Debian/GNU Linux 7 I don 't have this configuration option. There, the button "Configure Adapters" is completely missing in the Player GUI.

 

Does anybody know an alternative to limit bridging to a specific NIC in Player 7 on Debian GNU/Linux 7?

 

In case you 're interested in why I'm looking for this configuration option, the following additional notes on my scenario may be helpful: NIC "eth0" is connected to an ethernet switch, which connects some more machines. If only "eth0" is connected / plugged in, everything works as expected: VM can reach the machines on LAN and vice versa. NIC "eth1" provides an internet connection.

 

As soon as "eth1" is connected / plugged in, the following logs are visible with "dmesg":

 

[11096.648225] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx

[11096.649449] device eth0 left promiscuous mode

[11096.649458] bridge-eth0: disabled promiscuous mode

[11096.649463] bridge-eth0: disabling the bridge on dev down

[11096.649617] bridge-eth0: down

[11096.649623] bridge-eth0: detached

[11096.649652] /dev/vmnet: open called by PID 3298 (vmnet-bridge)

[11096.649664] /dev/vmnet: port on hub 0 successfully opened

[11096.649673] bridge-eth1: up

[11096.649675] bridge-eth1: attached

[11096.649679] device eth1 entered promiscuous mode

[11096.649692] bridge-eth1: enabled promiscuous mode

[11096.849083] userif-4: sent link down event.

[11096.849087] userif-4: sent link up event.

 

After that, there is no communication possible from host to VM and no communication possible from LAN to VM and vice versa . Plugging out the cable of "eth1" makes the connections to and from VM work again.

 

 

Greetings,

Stefan


Viewing all articles
Browse latest Browse all 5660

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>