ping round trip times freebsd - windows

[Stefan]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Greetings,

First  I  would  like to say hello to everyone and want to admit, that
I'm not that expert in freebsd ;-).

I've  took an interest in freebsd at v5.0 and have been playing around
since  that  (technical  curiosity).  Due  to  my job I only work with
Windows-machines/servers.  Until  now I was happy not to be confronted
with  major problems in freebsd and it worked very well so far (for my
personal needs) - but I just recognized something strange...

I  have  an test-machine at work (w2003 server) and freebsd running in
an  vmware (via dhcp). I tried simple round trip time measurements via
ping-command  but  got  different  results. I'm pretty sure, that this
might  only  be  a  config  or  commandline  issue,  but I didn't find
anything  useful  so  far.  (man  ping  included).  Ping  shows (in my
knowledge)   the   complete   round  trip  time  a  packet  needs  for
echo_request  and echo_reply. In case of the freebsd ouput it seems to
me, that it is only one-way.

Please  find  the results for the two different commands below - maybe
someone has an hint for me.


freebsd:

PING xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx): 56 data bytes
64 bytes from xxx.xxx.xxx.xxx: icmp_seq=0 ttl=128 time=151.541 ms
64 bytes from xxx.xxx.xxx.xxx: icmp_seq=1 ttl=128 time=146.279 ms
64 bytes from xxx.xxx.xxx.xxx: icmp_seq=2 ttl=128 time=169.988 ms
64 bytes from xxx.xxx.xxx.xxx: icmp_seq=3 ttl=128 time=151.510 ms
64 bytes from xxx.xxx.xxx.xxx: icmp_seq=4 ttl=128 time=141.120 ms
64 bytes from xxx.xxx.xxx.xxx: icmp_seq=5 ttl=128 time=153.513 ms
64 bytes from xxx.xxx.xxx.xxx: icmp_seq=6 ttl=128 time=168.278 ms
64 bytes from xxx.xxx.xxx.xxx: icmp_seq=7 ttl=128 time=148.961 ms
64 bytes from xxx.xxx.xxx.xxx: icmp_seq=8 ttl=128 time=159.754 ms
64 bytes from xxx.xxx.xxx.xxx: icmp_seq=9 ttl=128 time=199.485 ms

- --- xxx.xxx.xxx.xxx ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 141.120/159.043/199.485/16.033 ms


windows 2003 server (vmware-host):

Pinging xxx.xxx.xxx.xxx with 32 bytes of data:
Reply from xxx.xxx.xxx.xxx: bytes=32 time=289ms TTL=125
Reply from xxx.xxx.xxx.xxx: bytes=32 time=290ms TTL=125
Reply from xxx.xxx.xxx.xxx: bytes=32 time=387ms TTL=125
Reply from xxx.xxx.xxx.xxx: bytes=32 time=352ms TTL=125
Reply from xxx.xxx.xxx.xxx: bytes=32 time=372ms TTL=125
Reply from xxx.xxx.xxx.xxx: bytes=32 time=311ms TTL=125
Reply from xxx.xxx.xxx.xxx: bytes=32 time=289ms TTL=125

Ping statistics for xxx.xxx.xxx.xxx:
    Packets: Sent = 7, Received = 7, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 289ms, Maximum = 387ms, Average = 327ms



The  connection is approx. around half the world The rtt is definitely
between 300-600ms.


Current networking setup looks like the following:

test-machine---[LAN]---[Firewall]----Internet----[Firewall]---[LAN]---target-server


Current pc setup:

source:
Windows 2003 standard edition
vmware 5.5
freebsd 6.1 release (generic kernel install; no further configuration changes)

destination:
windows 2003 server

As  soon  as the ping pass the firewall and will be routed (either vpn
or mpls) it seems that the rtt is only the half-way time.

best regards
Stefan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)

iQEVAwUBRV7e5asBSJW3BUHpAQP5ugf8CCUDbtRoGBrsh1ujAheeLzCYa2X1bCu7
PD9PMvs2alQTgn7C4OD8ihpUJ2HdJodWxVfJefe6T60rPV2PuQu+qNsPy69Rt6JW
IhIDtbvOaagpF/PmjMT7yZ+1TstAK3QUX4SEWQYRyRogg2tGYYWv8hfQl14VEbGU
QpGuAZqXe3Qw056J2cweTzE5x9xX3lnihGxGq1brlPI4EPpT2LtfUy2GVFShrDeZ
IGYO4HAebQD8TPf1iPdBPlpuQXbvVos5he/SPKbFTx1NYpJ46vWVrfgc7VQdffWD
DCAtfIV+BzI9aiCrPtw3++XCp2rdyzKA8puYoK6IPimlALsiroMJUA==
=cSOY
-----END PGP SIGNATURE-----