search for: 3007ms

...ow Reachable. (9ms / 3000ms) [Jan 14 06:45:04] NOTICE[29231] chan_sip.c: Peer '100' is now Lagged. (5008ms / 3000ms) [Jan 14 06:45:14] NOTICE[29231] chan_sip.c: Peer '100' is now Reachable. (7ms / 3000ms) [Jan 14 07:10:27] NOTICE[29231] chan_sip.c: Peer '100' is now Lagged. (3007ms / 3000ms) [Jan 14 07:10:37] NOTICE[29231] chan_sip.c: Peer '100' is now Reachable. (8ms / 3000ms) [Jan 14 07:20:37] NOTICE[29231] chan_sip.c: Peer '100' is now Lagged. (4007ms / 3000ms) If I run a constant ping to that peer all looks fine: PING 192.168.1.110 (192.168.1.110) 56(84)...

...oss, time 3000ms rtt min/avg/max/mdev = 0.069/0.080/0.091/0.010 ms And then the problematic size: $ ping -c 4 -s 3981 localhost PING localhost.localdomain (127.0.0.1) 3981(4009) bytes of data. --- localhost.localdomain ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3007ms And verifying such large packet works without NFQUEUE: # iptables -F $ ping -c 4 -s 3981 localhost PING localhost.localdomain (127.0.0.1) 3981(4009) bytes of data. 3989 bytes from localhost.localdomain (127.0.0.1): icmp_seq=1 ttl=64 time=0.028 ms 3989 bytes from localhost.localdomain (127.0.0.1)...