From: Andrew Lunn <andrew@lunn.ch>
To: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: [Query]: DSA Understanding
Date: Thu, 9 Aug 2018 17:35:43 +0200 [thread overview]
Message-ID: <20180809153543.GD20006@lunn.ch> (raw)
In-Reply-To: <CA+V-a8sEKfe+vRkxM7EKwH9h3HwLcW_k1Ygso2K3h5jY3TtaiA@mail.gmail.com>
> > > The received packets captured on the PC are MDNS and DHPC, these MDNS
> > > are causing the rx
> > > packet counter go up:
> >
> > And where are these packets coming from? The target device? Or some
> > other device on your network?
> >
> AFIK, MDNS is also kind of a bcast its sending MDNS requests and
> receiving itself,
> that’s the reason rx packets are incrementing (correct me if I am wrong)
Your Ethernet device should not be receiving its own
transmissions. Looping back for broadcast and multicast packets
happens higher up in the network stack.
Look at the source MAC address for these packets. Where are the coming
from?
> ~$ ethtool -S lan4
> NIC statistics:
...
> tx_hi: 0
> tx_late_col: 0
> tx_pause: 0
> tx_bcast: 749
> tx_mcast: 212
This suggest the switch is putting packets onto the wire.
> Only weird thing I notice on target, when its replying for ping
> requests ( (oui Unknown) is that something which is causing issues ?
These are not ping requests. These are ARP requests/replies.
> 08:11:20.230704 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has
> VB4-SN00000000 tell tango-charlie.local, length 46
> 08:11:20.230749 ARP, Ethernet (len 6), IPv4 (len 4), Reply
> VB4-SN00000000 is-at c4:f3:12:08:fe:7f (oui Unknown), length 28
> 08:11:21.230629 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has
> VB4-SN00000000 tell tango-charlie.local, length 46
> 08:11:21.230657 ARP, Ethernet (len 6), IPv4 (len 4), Reply
> VB4-SN00000000 is-at c4:f3:12:08:fe:7f (oui Unknown), length 28
> 08:11:22.247831 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has
> VB4-SN00000000 tell tango-charlie.local, length 46
> 08:11:22.247857 ARP, Ethernet (len 6), IPv4 (len 4), Reply
> VB4-SN00000000 is-at c4:f3:12:08:fe:7f (oui Unknown), length 28
c4:f3:12 is the OUI. It is actually registers to TI:
https://aruljohn.com/mac/C4F312
But tcpdump probably does not know this, or the build you have has the
oui table removed to keep the binary small.
Andrew
next prev parent reply other threads:[~2018-08-09 18:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 8:39 [Query]: DSA Understanding Lad, Prabhakar
2018-07-25 16:19 ` Andrew Lunn
2018-07-26 7:38 ` Lad, Prabhakar
2018-07-26 14:08 ` Andrew Lunn
2018-07-26 15:20 ` Lad, Prabhakar
2018-07-26 15:39 ` Andrew Lunn
2018-08-02 8:13 ` Lad, Prabhakar
2018-08-02 14:45 ` Andrew Lunn
2018-08-02 14:58 ` Lad, Prabhakar
2018-08-02 16:05 ` Andrew Lunn
2018-08-02 16:24 ` Florian Fainelli
2018-08-09 11:33 ` Lad, Prabhakar
2018-08-09 12:08 ` Andrew Lunn
2018-08-09 11:31 ` Lad, Prabhakar
2018-08-09 12:01 ` Andrew Lunn
2018-08-09 12:45 ` Lad, Prabhakar
2018-08-09 12:56 ` Andrew Lunn
2018-08-09 15:07 ` Lad, Prabhakar
2018-08-09 15:35 ` Andrew Lunn [this message]
2018-08-09 16:03 ` Lad, Prabhakar
2018-08-09 17:23 ` Andrew Lunn
2018-08-10 11:26 ` Lad, Prabhakar
2018-08-10 17:36 ` Florian Fainelli
2018-08-13 11:06 ` Lad, Prabhakar
2018-08-13 13:38 ` Andrew Lunn
2018-08-13 15:58 ` Lad, Prabhakar
2018-08-13 18:57 ` Florian Fainelli
2018-08-14 11:49 ` Lad, Prabhakar
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=20180809153543.GD20006@lunn.ch \
--to=andrew@lunn.ch \
--cc=netdev@vger.kernel.org \
--cc=prabhakar.csengg@gmail.com \
/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.