From: BERTRAND Joel <joel.bertrand@systella.fr>
To: sparclinux@vger.kernel.org
Subject: Strange network promiscuous mode...
Date: Mon, 23 Mar 2009 13:00:23 +0000 [thread overview]
Message-ID: <49C787E7.9060700@systella.fr> (raw)
Hello,
I have build a 2.6.28.7 kernel on sparc64 (libc6 2.9). On all my
sparc64 (U60 with 3Com and HME NIC's, U1, U420 with HME), tcpdump
doesn't return any information (but it can count packets !) :
Root rayleigh:[~] > tcpdump -i eth1
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes
^C
0 packets captured
635 packets received by filter
0 packets dropped by kernel
Root rayleigh:[/proc/net] > cat dev
Inter-| Receive | Transmit
face |bytes packets errs drop fifo frame compressed multicast|bytes
packets errs drop fifo colls carrier compressed
lo:759580471 897007 0 0 0 0 0 0
759580471 897007 0 0 0 0 0 0
eth0:2081060383 3955569 0 0 0 0 0 0
4222746354 4419280 0 0 0 0 0 0
eth1:6655662953 5877440 0 0 0 0 0 0
1002520280 3856332 0 0 0 0 0 0
eth2:27035148 352686 0 0 1 0 0 0
658938822 545289 0 0 0 0 0 0
Root rayleigh:[/proc/net] >
With the same configuration (kernel and libc), I cannot reproduce this
bug on i386 or amd64. With 2.6.27/sparc64, tcpdump and others worked fine.
Problem : all programs that try to catch packets in promiscuous mode do
not work anymore. Is there any issue ?
Regards,
JKB
next reply other threads:[~2009-03-23 13:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 13:00 BERTRAND Joel [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-05-07 22:09 Strange network promiscuous mode David Miller
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=49C787E7.9060700@systella.fr \
--to=joel.bertrand@systella.fr \
--cc=sparclinux@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.