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, 2 Aug 2018 16:45:50 +0200 [thread overview]
Message-ID: <20180802144550.GE7462@lunn.ch> (raw)
In-Reply-To: <CA+V-a8uiaO3Z9fLeXvkfrm0Fvp=h7eBu3d9kQEuOQY7xwzAZHg@mail.gmail.com>
> I have PC connected to lan4(ip = 169.254..126.126) and the PC ip is
> 169.254.78.251,
> but when I ping from PC to lan4 I get Destination Host Unreachable,
> but where as I can see
> that in the tcpdump log for lan4 it does reply back, but it doesn’t
> reach the PC, Is there I am missing
> something here ?
>
> ~$ tcpdump -i lan4 -v
> [ 661.057166] device lan4 entered promiscuous mode
> [ 661.061814] device eth1 entered promiscuous mode
> 07:40:21.254161 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has
> VB4-SN00000000 tell tango-charlie.local, length 46
> 07:40:21.254181 ARP, Ethernet (len 6), IPv4 (len 4), Reply
> VB4-SN00000000 is-at c4:f3:12:08:fe:7f (oui Unknown), length 28
Having names here does not help when you gave IP addresses above.
Am i reading this correct? The PC is ARPing the switch device. The
switch device is replying?
What does tcpdump on the PC show? Are the ARP replies getting to it?
Is the PC dropping the ARP replies?
If the PC is dropping the ARP replies, take a look at the
checksums. Wireshark is good at that.
If the ARP replies are not making it to the PC, look at the switch
statistics. ethtool -S lan4. Are the TX counts going up? Any error
counts going up?
Andrew
next prev parent reply other threads:[~2018-08-02 16:37 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 [this message]
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
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=20180802144550.GE7462@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.