[Kingbonecrusher]

Kennt zufällig jemand dieses Problem und hat eine Lösung zur Hand?

http://vmware-forum....opic.php?t=8275

http://vmware-forum....opic.php?t=7776

Dieser Beitrag wurde von Kingbonecrusher bearbeitet: 13. März 2007 - 12:32

[Kingbonecrusher]

Hallo, ich habe eine Übergangslösung gefunden, welche gut funktioniert.

-> root

vmware-config.pl

Do you wish to configure another NAT network? (yes/no) [no]

Do you want to be able to use host-only networking in your virtual machines?
[yes]

Configuring a host-only network for vmnet1.

Do you want this program to probe for an unused private subnet? (yes/no/help)
[yes] help

Virtual machines configured to use host-only networking are placed on a virtual
network that is confined to this host.  Virtual machines on this network can
communicate with each other and the host, but no one else.

To setup this host-only networking you need to select a network number that is
normally unreachable from the host.  We can automatically select this number
for you, or you can specify a network number that you want.

The automatic selection process works by testing a series of Class C subnet
numbers to see if they are reachable from the host.  The first one that is
unreachable is used.  The subnet numbers are chosen from the private network
numbers specified by the Internet Engineering Task Force (IETF) in RFC 1918
(http://www.isi.edu/in-notes/rfc1918.txt).

Remember that the host-only network that virtual machines reside on will not be
accessible outside the host machine.  This means that it is OK to use the same
number on different systems so long as you do not enable communication between
these networks.

Do you want this program to probe for an unused private subnet? (yes/no/help)
[yes]

Probing for an unused private subnet (this can take some time)...

The subnet 192.168.7.0/255.255.255.0 appears to be unused.

The following host-only networks have been defined:

. vmnet1 is a host-only network on private subnet 192.168.7.0.

Dann sollteet Ihr mit ifconfig ein neues devices vmnet1 sehen. Ihr könnt euch dann an dies IP verbinden und nun sollte alles klappen :-)

Scheint wohl ein Problem mit der Softwarebridge zu sein.

Ps: Habe mit iperf nun recht flinke 30MB/s

mfg