[openbeosnetteam] Latest Code...

I'll be cvs updating once I've been food shopping, but just as a heads up,
these might be of interest...

All these are taken from an ssh session running on win 2k connected to a
FreeBSD laptop. Network is 100Mbp via a hub.

freebsd pinging openbsd
bash-2.04$ ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttl=255 time=0.182 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=255 time=0.121 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=255 time=0.124 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=255 time=0.128 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=255 time=0.124 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=255 time=0.124 ms

openbsd pinging new net stack (kernel)
bash-2.04$ ping 192.168.0.133
PING 192.168.0.133 (192.168.0.133): 56 data bytes
64 bytes from 192.168.0.133: icmp_seq=0 ttl=64 time=0.260 ms
64 bytes from 192.168.0.133: icmp_seq=1 ttl=64 time=0.218 ms
64 bytes from 192.168.0.133: icmp_seq=2 ttl=64 time=0.219 ms
64 bytes from 192.168.0.133: icmp_seq=3 ttl=64 time=0.215 ms
64 bytes from 192.168.0.133: icmp_seq=4 ttl=64 time=0.224 ms
64 bytes from 192.168.0.133: icmp_seq=5 ttl=64 time=0.200 ms

freebsd pinging new stack (kernel) with one other ping running on machine
bash-2.04$ ping 192.168.0.133
PING 192.168.0.133 (192.168.0.133): 56 data bytes
64 bytes from 192.168.0.133: icmp_seq=0 ttl=64 time=0.248 ms
64 bytes from 192.168.0.133: icmp_seq=1 ttl=64 time=0.177 ms
64 bytes from 192.168.0.133: icmp_seq=2 ttl=64 time=0.164 ms
64 bytes from 192.168.0.133: icmp_seq=3 ttl=64 time=0.203 ms
64 bytes from 192.168.0.133: icmp_seq=4 ttl=64 time=0.313 ms
64 bytes from 192.168.0.133: icmp_seq=5 ttl=64 time=0.168 ms

The above tests with the new kernel use the tulip card, the one belwo uses
the 3Com card - same kernel!

bash-2.04$ ping 192.168.0.134
PING 192.168.0.134 (192.168.0.134): 56 data bytes
64 bytes from 192.168.0.134: icmp_seq=0 ttl=64 time=2.244 ms
64 bytes from 192.168.0.134: icmp_seq=1 ttl=64 time=2.451 ms
64 bytes from 192.168.0.134: icmp_seq=2 ttl=64 time=0.688 ms
64 bytes from 192.168.0.134: icmp_seq=3 ttl=64 time=1.285 ms
64 bytes from 192.168.0.134: icmp_seq=4 ttl=64 time=1.264 ms
64 bytes from 192.168.0.134: icmp_seq=5 ttl=64 time=0.371 ms

So, it looks like the driver is playing a very big role in determining
performance, as we were told by Be numerous times.

The stack seems to be stable enough and the config was done using ifconfig.
sendto and recvfrom both work.

david

Other related posts: