Hi list, Is it just me, or is something totally broken in scan function of kernel protocol? # ping -i 0.01 -c 2500 127.0.0.1 PING 127.0.0.1 (127.0.0.1): 56 data bytes 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.019 ms (...) 64 bytes from 127.0.0.1: icmp_seq=1149 ttl=64 time=0.018 ms 64 bytes from 127.0.0.1: icmp_seq=1150 ttl=64 time=0.018 ms 64 bytes from 127.0.0.1: icmp_seq=1151 ttl=64 time=176.896 ms 64 bytes from 127.0.0.1: icmp_seq=1152 ttl=64 time=204.953 ms 64 bytes from 127.0.0.1: icmp_seq=1153 ttl=64 time=0.027 ms 64 bytes from 127.0.0.1: icmp_seq=1154 ttl=64 time=0.026 ms (...) 64 bytes from 127.0.0.1: icmp_seq=2499 ttl=64 time=0.019 ms --- 127.0.0.1 ping statistics --- 2500 packets transmitted, 2500 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.007/0.187/204.953/5.495 ms This generates quite a lot of funny things, among them being SIP breakage, freezes in games, hair-pulling in my person - whole network freezes for the scan-time. Does this happen only on my system? Bird 1.3.4+FIB, 8-STABLE current as of 2 hours ago. Pawel.