NetBSD IANZAG 2.0_BETA NetBSD 2.0_BETA (IANZAG) #1: Tue Jun 15 16:15:27 NOVST 
2004  ianzag@IANZAG:/usr/src/sys/arch/i386/compile/IANZAG i386

I have two PCs, let's say A and B.

PC A dmesg:
rtk0 at pci2 dev 9 function 0: Realtek 8139 10/100BaseTX
rtk0: interrupting at irq 11
rtk0: Ethernet address 00:20:ed:42:63:05
ukphy0 at rtk0 phy 7: Generic IEEE 802.3u media interface
ukphy0: OUI 0x000000, model 0x0000, rev. 0
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

PC B dmesg:
rtk0 at pci0 dev 10 function 0: Realtek 8139 10/100BaseTX
rtk0: interrupting at irq 11
rtk0: Ethernet address 00:05:b7:00:2a:f6
ukphy0 at rtk0 phy 7: Generic IEEE 802.3u media interface
ukphy0: OUI 0x000000, model 0x0000, rev. 0
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

So both have RTL8139 eth chipsets which looks to be identical. On both PCs i'm 
running NetBSD-release-2-0 built from same sources tree. There's only one 
"options INET" network option is set in both kernel configs. Both PCs are 
connected in 100MBit LAN.

on A ping B:
$ ping nbsd1
PING nbsd1 (192.168.100.5): 56 data bytes
64 bytes from 192.168.100.5: icmp_seq=0 ttl=255 time=0.276 ms
64 bytes from 192.168.100.5: icmp_seq=1 ttl=255 time=0.270 ms
64 bytes from 192.168.100.5: icmp_seq=2 ttl=255 time=0.286 ms
64 bytes from 192.168.100.5: icmp_seq=3 ttl=255 time=0.292 ms
64 bytes from 192.168.100.5: icmp_seq=4 ttl=255 time=0.298 ms

on B ping A:
PING ianzag (192.168.100.37): 56 data bytes
64 bytes from 192.168.100.37: icmp_seq=0 ttl=255 time=2.444 ms
64 bytes from 192.168.100.37: icmp_seq=1 ttl=255 time=57.479 ms
64 bytes from 192.168.100.37: icmp_seq=2 ttl=255 time=44.911 ms
64 bytes from 192.168.100.37: icmp_seq=3 ttl=255 time=46.508 ms
64 bytes from 192.168.100.37: icmp_seq=4 ttl=255 time=0.004 ms

Maybe i'm missing something but this isn't obvious for me why at the same time 
inside same idle LAN pings from A to B and ping from B to A differ so much.

ps: no kernel output like "rtk0: timeout" etc produces. Just silence.

Any ideas ?

// wbr