From: "Riccardo Paolo Bestetti" <pbl@bestov.io>
To: "Zhu Yanjun" <zyjzyj2000@gmail.com>
Cc: "netdev" <netdev@vger.kernel.org>
Subject: Re: Bonding driver unexpected behaviour
Date: Thu, 16 Jul 2020 09:08:38 +0200 [thread overview]
Message-ID: <773f-5f0ffd00-eb-de520b0@96800578> (raw)
In-Reply-To: <CAD=hENcYJwkL-mjgJd5OZ0B4tHz2Q9kuqQ8iHid=9TWgyvR=+Q@mail.gmail.com>
Hello Zhu Yanjun,
On Thursday, July 16, 2020 05:41 CEST, Zhu Yanjun <zyjzyj2000@gmail.com> wrote:
>
> Please check this
> https://developers.redhat.com/blog/2019/05/17/an-introduction-to-linux-virtual-interfaces-tunnels/#gre
>
> Perhaps gretap only forwards ip (with L2 header) packets.
That does not seem to be the case.
E.g.
root@fo-exit:/home/user# tcpdump -i intra16
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on intra16, link-type EN10MB (Ethernet), capture size 262144 bytes
09:05:12.619206 IP 10.88.16.100 > 10.88.16.200: GREv0, length 46: ARP, Request who-has 10.42.42.200 tell 10.42.42.100, length 28
09:05:12.619278 IP 10.88.16.200 > 10.88.16.100: GREv0, length 46: ARP, Reply 10.42.42.200 is-at da:9d:34:64:cb:8d (oui Unknown), length 28
09:05:14.054026 IP 10.88.16.200 > 10.88.16.100: GREv0, length 46: ARP, Request who-has 10.42.42.100 tell 10.42.42.200, length 28
09:05:14.107143 IP 10.88.16.100 > 10.88.16.200: GREv0, length 46: ARP, Reply 10.42.42.100 is-at d6:49:e5:19:52:16 (oui Unknown), length 28
^C
>
> Possibly "arp -s" could help to workaround this.
Riccardo P. Bestetti
next prev parent reply other threads:[~2020-07-16 7:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 12:46 Bonding driver unexpected behaviour pbl
2020-07-16 3:41 ` Zhu Yanjun
2020-07-16 7:08 ` Riccardo Paolo Bestetti [this message]
2020-07-16 7:45 ` Zhu Yanjun
2020-07-16 8:08 ` Riccardo Paolo Bestetti
2020-07-16 9:45 ` Zhu Yanjun
2020-07-16 10:20 ` Riccardo Paolo Bestetti
2020-07-16 14:31 ` Zhu Yanjun
2020-07-16 15:50 ` Jay Vosburgh
2020-07-19 10:07 ` Riccardo Paolo Bestetti
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=773f-5f0ffd00-eb-de520b0@96800578 \
--to=pbl@bestov.io \
--cc=netdev@vger.kernel.org \
--cc=zyjzyj2000@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).