From: Michal Simek <michal.simek@petalogix.com>
To: lgb@lgb.hu
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Network driver issue
Date: Thu, 12 Feb 2009 17:04:28 +0100 [thread overview]
Message-ID: <4994488C.8030209@petalogix.com> (raw)
In-Reply-To: <20090212145521.GC18597@vega.lgb.hu>
>> Hi guys,
>>
>> Could you give any hint what can be wrong? I use 2.6.29-rc4.
>> Tcpdump and wireshark show me that board can send packet and get
>> response but don't show
>> timing ping info. For incomming packets (exclude ARP) isn't any response
>> back. ARPs work well.
>>
>
> Are you sure that there is no netfilter rule(s) which filters out responses?
>
Yes, I am 100% sure.
> iptables-save > /tmp/iptables.save
> iptables -F INPUT
> iptables -P INPUT ACCEPT
>
> Sure, you should not leave your rules in this state, just for the time of
> checking. You can load your old ruleset back then with:
>
> iptables-restore < /tmp/iptables.save
>
> I just write this hint, because I've already seen this fault many times
> around ...
>
OK and Thanks,
Michal
>
>
>> Thanks,
>> Michal
>>
>>
>> ~ # tcpdump &
>> ~ # device eth0 entered promiscuous mode
>> tcpdump: listening on eth0
>>
>> ~ #
>> ~ # ping 192.168.0.102
>> PING 192.168.0.102 (192.168.0.102): 56 data bytes
>> 00:00:34.639430 192.168.0.20 > 192.168.0.102: icmp: echo request (DF)
>> 00:00:34.642714 192.168.0.102 > 192.168.0.20: icmp: echo reply
>> 00:00:35.662135 192.168.0.20 > 192.168.0.102: icmp: echo request (DF)
>> 00:00:35.667248 192.168.0.102 > 192.168.0.20: icmp: echo reply
>> 00:00:36.671424 192.168.0.20 > 192.168.0.102: icmp: echo request (DF)
>> 00:00:36.676416 192.168.0.102 > 192.168.0.20: icmp: echo reply
>> 00:00:37.681470 192.168.0.20 > 192.168.0.102: icmp: echo request (DF)
>> 00:00:37.686573 192.168.0.102 > 192.168.0.20: icmp: echo reply
>> 00:00:38.691440 192.168.0.20 > 192.168.0.102: icmp: echo request (DF)
>> 00:00:38.696452 192.168.0.102 > 192.168.0.20: icmp: echo reply
>> 00:00:39.701454 192.168.0.20 > 192.168.0.102: icmp: echo request (DF)
>> 00:00:39.706520 192.168.0.102 > 192.168.0.20: icmp: echo reply
>> 00:00:40.711422 192.168.0.20 > 192.168.0.102: icmp: echo request (DF)
>> 00:00:40.716429 192.168.0.102 > 192.168.0.20: icmp: echo reply
>> 00:00:41.721460 192.168.0.20 > 192.168.0.102: icmp: echo request (DF)
>> 00:00:41.726542 192.168.0.102 > 192.168.0.20: icmp: echo reply
>> 00:00:42.731478 192.168.0.20 > 192.168.0.102: icmp: echo request (DF)
>> 00:00:42.736476 192.168.0.102 > 192.168.0.20: icmp: echo reply
>> 00:00:43.741444 192.168.0.20 > 192.168.0.102: icmp: echo request (DF)
>> 00:00:43.746525 192.168.0.102 > 192.168.0.20: icmp: echo reply
>> 00:00:44.751429 192.168.0.20 > 192.168.0.102: icmp: echo request (DF)
>> 00:00:44.756441 192.168.0.102 > 192.168.0.20: icmp: echo reply
>> 00:00:45.761449 192.168.0.20 > 192.168.0.102: icmp: echo request (DF)
>> 00:00:45.766528 192.168.0.102 > 192.168.0.20: icmp: echo reply
>> 00:00:46.771434 192.168.0.20 > 192.168.0.102: icmp: echo request (DF)
>> 00:00:46.776438 192.168.0.102 > 192.168.0.20: icmp: echo reply
>>
>> --- 192.168.0.102 ping statistics ---
>> 13 packets transmitted, 0 packets received, 100% packet loss
>> ~ # 00:01:06.468561 192.168.0.102 > 192.168.0.20: icmp: echo request (DF)
>> 00:01:07.477512 192.168.0.102 > 192.168.0.20: icmp: echo request (DF)
>> 00:01:08.477428 192.168.0.102 > 192.168.0.20: icmp: echo request (DF)
>> 00:01:09.477253 192.168.0.102 > 192.168.0.20: icmp: echo request (DF)
>> 00:01:10.477131 192.168.0.102 > 192.168.0.20: icmp: echo request (DF)
>> 00:01:11.466927 arp who-has 192.168.0.20 tell 192.168.0.102
>> 00:01:11.472649 arp reply 192.168.0.20 is-at 0:a:35:0:22:1
>> 00:01:11.477375 192.168.0.102 > 192.168.0.20: icmp: echo request (DF)
>> 00:01:12.476840 192.168.0.102 > 192.168.0.20: icmp: echo request (DF)
>>
>> ~ # ifconfig
>> eth0 Link encap:Ethernet HWaddr 00:0A:35:00:22:01
>> inet addr:192.168.0.20 Bcast:192.168.0.255 Mask:255.255.255.0
>> UP BROADCAST RUNNING MTU:1500 Metric:1
>> RX packets:26 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:1000
>> RX bytes:2434 (2.3 KiB) TX bytes:1694 (1.6 KiB)
>> Interrupt:5
>>
>> lo Link encap:Local Loopback
>> inet addr:127.0.0.1 Mask:255.0.0.0
>> UP LOOPBACK RUNNING MTU:16436 Metric:1
>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:0
>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>>
>> ~ #
>> ~ # ping 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=7.4 ms
>> 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=3.4 ms
>> 64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=3.4 ms
>>
>> --- 127.0.0.1 ping statistics ---
>> 3 packets transmitted, 3 packets received, 0% packet loss
>> round-trip min/avg/max = 3.4/4.7/7.4 ms
>> ~ #
>>
>>
>> --
>> Michal Simek, Ing. (M.Eng)
>> PetaLogix - Linux Solutions for a Reconfigurable World
>> w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
>>
>
>
--
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663
prev parent reply other threads:[~2009-02-12 16:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 14:28 Network driver issue Michal Simek
2009-02-12 14:55 ` Gábor Lénárt
2009-02-12 16:04 ` Michal Simek [this message]
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=4994488C.8030209@petalogix.com \
--to=michal.simek@petalogix.com \
--cc=lgb@lgb.hu \
--cc=linux-kernel@vger.kernel.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.