vmware 4.0.5 - zwilosci sieci...

[Paweł Sikora]

wlasnie koncze prace nad specem do vmware-4.0.5 i dzis spotkalo
mnie cos, co pierwszy raz na oczeta widze, a bylo to tak...

zaladowalem sobie moduly vmmon, vmnet, pcnet32,
podnioslem interfejs vmnet1 (host-only networking).

[root]-[/etc/tcpd] # ip a l
1: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
   link/ether 00:05:5d:e1:f9:45 brd ff:ff:ff:ff:ff:ff
   inet 192.168.24.230/22 brd 192.168.27.255 scope global eth0
(...)
6: vmnet1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
   link/ether 00:50:56:c0:00:0a brd ff:ff:ff:ff:ff:ff
   inet 10.0.0.1/8 brd 10.255.255.255 scope global vmnet1

[root]-[/etc/tcpd] # ip r l
192.168.24.0/22 dev eth0  proto kernel  scope link  src 192.168.24.230
10.0.0.0/8 dev vmnet1  proto kernel  scope link  src 10.0.0.1
default via 192.168.24.1 dev eth0 onlink

konfig od vmware wyglada tak:

[pluto]-[~] # cat .vmware/win2k/win2000Pro.vmx
config.version = "7"
virtualHW.version = "3"
memsize = "128"
scsi0:0.present = "TRUE"
scsi0:0.fileName = "win2000Pro.vmdk"
scsi0.present = "TRUE"
ide0:0.present = "TRUE"
ide0:0.fileName = "/dev/hdc"
ide0:0.deviceType = "atapi-cdrom"
floppy0.fileName = "/dev/fd0"
floppy0.present = "FALSE"
sound.present = "FALSE"
displayName = "win2000Pro"
guestOS = "win2000Pro"
priority.grabbed = "normal"
priority.ungrabbed = "normal"
mouse.hostType = "autodetect"
undopoint.disableSnapshots = "TRUE"
uuid.location = "56 4d 05 0b 43 08 81 51-60 ee 44 12 90 8b de a1"
isolation.tools.dnd.disable = "TRUE"
tools.remindInstall = "FALSE"
ide0:0.startConnected = "TRUE"
tools.syncTime = "TRUE"

ethernet0.present = "TRUE"
ethernet0.connectionType = "hostonly"
ethernet0.addressType = "generated"
ethernet0.generatedAddress = "00:0c:29:8b:de:a1"
ethernet0.generatedAddressOffset = "0"

vmnet1.hostOnlyAddress = "10.0.0.1"
vmnet1.hostOnlyNetMask = "255.0.0.0"

zastartowalem wirtuanego win2k (swieza instalacja, bez zadnych SP).
skonfigurowalem interfejs jak na rysunku:
http://www.ds14.agh.edu.pl/~pluto/tmp/vmware.png
i wyglada na to, ze dziala.
puszczam pinga linux->win2k

[root]-[/etc/tcpd] # ping 10.0.0.2
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.
64 bytes from 10.0.0.2: icmp_seq=1 ttl=128 time=1.92 ms
64 bytes from 10.0.0.2: icmp_seq=2 ttl=128 time=0.545 ms
64 bytes from 10.0.0.2: icmp_seq=3 ttl=128 time=0.489 ms
64 bytes from 10.0.0.2: icmp_seq=4 ttl=128 time=0.624 ms
64 bytes from 10.0.0.2: icmp_seq=5 ttl=128 time=0.541 ms
64 bytes from 10.0.0.2: icmp_seq=6 ttl=128 time=0.494 ms
64 bytes from 10.0.0.2: icmp_seq=7 ttl=128 time=0.563 ms
64 bytes from 10.0.0.2: icmp_seq=8 ttl=128 time=0.608 ms
64 bytes from 10.0.0.2: icmp_seq=9 ttl=128 time=0.641 ms
64 bytes from 10.0.0.2: icmp_seq=10 ttl=128 time=0.513 ms

i ladnie odpowiada. liczniki pakietow w win2k elegancko podbijaja
sie o jeden, wiec obusstronna komunikacja funkcjonuje.

jednakoz proba wyslania pinga win2k->linux pozostaje bez odzewu.
wtf?

ps). firewall mam wylaczony, logi czyste.

-- 
If you think of MS-DOS as mono, and Windows as stereo,
  then Linux is Dolby Digital and all the music is free...