From: "HouCheng Lee" <thisrobert@mail2000.com.tw>
To: netfilter-devel@lists.netfilter.org
Subject: ICMP packets lost with an interval of 30 packets
Date: Sun, 14 Sep 2003 00:00:36 +0800 (CST) [thread overview]
Message-ID: <1063468836.67875.thisrobert@mail2000.com.tw> (raw)
Hi,everyone:
I have ported the 2.4.18 kernel to a board of MIPS arch.
When I "make menuconfig", just turn on connection tracking
option,
and let the MIPS board run,
I got a strange icmp echo and reply pattern.
I config my eth0 of MIPS board "192.168.1.254",
and ping it from my computer with IP,"192.168.1.100".
I got the following messages:
------------------------------------------------------------
PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data.
64 bytes from 192.168.1.254: icmp_seq=1 ttl=255 time=4.80 ms
64 bytes from 192.168.1.254: icmp_seq=31 ttl=255 time=1.62 ms
64 bytes from 192.168.1.254: icmp_seq=61 ttl=255 time=1.94 ms
............................................
-------------------------------------------------------------
And when I change the "ICMP_TIMEOUT" variable in
"ip_conntrack_proto_icmp.c" from (30*Hz) to (20*Hz),
the echo and reply looks like following:
------------------------------------------------------------
PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data.
64 bytes from 192.168.1.254: icmp_seq=1 ttl=255 time=4.80 ms
64 bytes from 192.168.1.254: icmp_seq=21 ttl=255 time=1.62 ms
64 bytes from 192.168.1.254: icmp_seq=41 ttl=255 time=1.94 ms
............................................
-------------------------------------------------------------
I had done the same thing on x86 arch and everything was ok.
I do not know if there are some arch dependent code in
netfilter,
or I have missed some relevant modules or there are bugs in
the hardware.
Please give me some suggestion.
Thanks.
reply other threads:[~2003-09-13 16:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1063468836.67875.thisrobert@mail2000.com.tw \
--to=thisrobert@mail2000.com.tw \
--cc=netfilter-devel@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.