Re: Is vmnet broken in 4.5?

2002-02-22 Thread Andy Sparrow


Hey Eugene,

With the exception that I *can* ping the vmnet1 interface but the ICMP echo 
replies from FreeBSD never make it back to the VMware hosted OS, and neither 
side can get the ARP address of the other, I see very much the same symptoms 
as you.

I'm running 4.4-STABLE RC2 (I'm waiting for XFree86-4.2.0 to make it back into 
ports before I update again, as this version works for me).

All my ports and everything in the OS are at the same level (buildworld, 
buildkernel, portupgrade etc). Everything's working great AFAICS, with the 
minor exception of this.

Cheers,

AS

 Hi.
 
 My vmware2 use netgraph bridge to access the network. Under 4.4 all work
 fine. But after upgrade to 4.5 I got some trouble. I can't see my FBSD box
 under vmware, but all other boxes in network work fine. I can't ping from
 FBSD box to vmnet1 address.
 
 It seems, vmware guest OS can't get arp address of FBSD.
 
 +
 xl0   172.17.1.206/16   -- 172.17/16 (DHCP server, Internet, etc)
 |
 FBSD 4.5|
 ++
  vmnet1   172.17.240.241/16 -- 172.17.5.121/16 (vmware2, win98se) |
 -+
 
 Some usefull info:
 
 Win98SE (guest OS) use DHCP server for assigning IP address, DNSes 
 default gateway. 
 
 -
 box$ ping 172.17.1.206
 PING 172.17.1.206 (172.17.1.206): 56 data bytes
 64 bytes from 172.17.1.206: icmp_seq=0 ttl=64 time=0.162 ms
 
 -
 box$ ping 172.17.240.241
 PING 172.17.240.241 (172.17.240.241): 56 data bytes
 ping: sendto: Host is down
 
 and in the same time we can see next 
 
 box# tcpdump -i xl0 host 172.17.240.241
 tcpdump: listening on xl0
 arp who-has 172.17.240.241 tell 172.17.1.206
 arp who-has 172.17.240.241 tell 172.17.1.206
 .
 
 -
 c:\Program files\FAR ping 172.17.1.206
 pinging 172.17.1.206
 timeout
 ...
 timeout
 
 and in the same time
 
 box# tcpdump -i vmnet1 host 172.17.5.121
 tcpdump: listening on vmnet1
 172.17.1.206  172.17.5.121: icmp: echo reply
 172.17.1.206  172.17.5.121: icmp: echo request
 172.17.1.206  172.17.5.121: icmp: echo request
 172.17.1.206  172.17.5.121: icmp: echo request
 172.17.1.206  172.17.5.121: icmp: echo request
 172.17.1.206  172.17.5.121: icmp: echo request
 172.17.1.206  172.17.5.121: icmp: echo request
 172.17.5.121  172.17.1.206: icmp: echo request
 172.17.1.206  172.17.5.121: icmp: echo reply
 
 
 
 c:\Program files\FAR ping 172.17.0.1
 
 answer, size=32 bytes, time=21ms, TTL=64
 .
 
 c:\Program files\FAR ping www.mtu.ru
 
 pinging 195.34.32.10
 answer, size=32 bytes, time=157ms, TTL=248
 .
 
 
 
 box# uname -a
 FreeBSD badger.imedia.ru 4.5-RELEASE FreeBSD 4.5-RELEASE #29: Tue Feb  5
 11:00:19 MSK 2002
 [EMAIL PROTECTED]:/var/devel/CVSUP/src/sys/compile/BADGER i386
 
 box# kldstat
 Id Refs AddressSize Name
  1   15 0xc010 2873d0   kernel
  21 0xc0388000 542c snd_es137x.ko
  31 0xc038e000 157b4snd_pcm.ko
  41 0xc0f92000 c3000vinum.ko
  51 0xc1088000 7000 linprocfs.ko
  61 0xc1112000 2000 green_saver.ko
  73 0xc11c 15000linux.ko
  81 0xc1115000 2000 rtc.ko
 101 0xc12b6000 4000 if_tap.ko
 121 0xc13d2000 3000 ng_socket.ko
 133 0xc13d8000 9000 netgraph.ko
 151 0xc13e1000 3000 ng_ether.ko
 161 0xc13e4000 4000 ng_bridge.ko
 171 0xc12aa000 9000 vmmon_up.ko
 181 0xc17de000 8000 cd9660.ko
 
 box# ifconfig -a
 xl0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500
 options=3rxcsum,txcsum
 inet 172.17.1.206 netmask 0x broadcast 172.17.255.255
 atalk 228.127 range 220-230 phase 2 broadcast 0.255
 ether 00:50:da:cd:b2:0e 
 media: Ethernet autoselect (100baseTX full-duplex)
 status: active
 lp0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500
 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384
 inet 127.0.0.1 netmask 0xff00 
 atalk 0.0 range 0-0 phase 2
 vmnet1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
 inet 172.17.240.241 netmask 0x broadcast 172.17.255.255
 ether 00:bd:e7:14:00:01 
 Opened by PID 41162
 
 box# netstat -nr -f inet
 Routing tables
 
 Internet:
 DestinationGatewayFlagsRefs  Use  Netif Expire
 default172.17.0.1 UGSc   34   75xl0
 127.0.0.1  127.0.0.1  UH  3   102683lo0
 172.17 link#1 UC 110xl0
 172.17.0.1 0:d0:b7:a9:f:f9UHLW   38  5864104xl0   1193
 172.17.1.206   0:50:da:cd:b2:eUHLW2 1114lo0
 172.17.5.121   0:bd:e7:da:d5:31   UHLW1 1336xl0762
 172.17.120.66  link#1 UHLW1   49xl0
 172.17.124.5   0:50:8b:69:c3:d5   UHLW0  714xl0   1195
 172.17.124.209 0:d0:b7:a9:37:c8   

Re: Is vmnet broken in 4.5?

2002-02-20 Thread Garance A Drosihn

At 11:38 AM +0300 2/19/02, Eugene Mitrofanov wrote:
Hi.

My vmware2 use netgraph bridge to access the network. Under 4.4 all
work fine. But after upgrade to 4.5 I got some trouble. I can't see
my FBSD box under vmware, but all other boxes in network work fine.
I can't ping from FBSD box to vmnet1 address.

It seems, vmware guest OS can't get arp address of FBSD.

I do not know enough to help with the problem you are seeing, but I
thought I would mention that I am running vmware2 on a freebsd-4.5
system, and it is working for me.  I follow the 4-stable branch, so
I have been rebuilding my system every few weeks.  It may be that I
had to do special steps at some point to keep vmware2 working, but
I don't remember what those would have been.  I do remember that at
some point I had to rebuild the port.

I am using netgraph bridging too.  So, it is possible for vmware2
to still work under 4.5-release.  It is not completely broken.

-- 
Garance Alistair Drosehn=   [EMAIL PROTECTED]
Senior Systems Programmer   or  [EMAIL PROTECTED]
Rensselaer Polytechnic Instituteor  [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message