From: Samuel Thibault <samuel.thibault@gnu.org>
To: Chris Heinze <c.heinze@precibake.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] slirp, incoming packets get truncated
Date: Fri, 6 Sep 2019 11:59:05 +0200 [thread overview]
Message-ID: <20190906095905.44hrurx3vlbqidkq@function> (raw)
In-Reply-To: <0115e29c-2254-09c3-13d5-6dfb5307d968@precibake.com>
Hello,
Chris Heinze, le mar. 03 sept. 2019 17:02:15 +0200, a ecrit:
> on the guest:
> root@guest:~# tcpdump -ni eth0 port 19003
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
> 16:49:39.430959 IP 10.0.2.2.33294 > 10.0.2.15.19003: UDP, bad length 9000 > 1472
Just to be sure: did you configure your guest mru to 9000 ? Does the
emulated network hardware card support jumbo frames?
Samuel
next prev parent reply other threads:[~2019-09-06 9:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 15:02 [Qemu-devel] slirp, incoming packets get truncated Chris Heinze
2019-09-06 9:59 ` Samuel Thibault [this message]
2019-09-06 10:54 ` Chris Heinze
2019-09-06 11:14 ` Samuel Thibault
2019-09-07 23:29 ` Samuel Thibault
2019-09-09 10:35 ` Chris Heinze
2019-09-09 10:51 ` Philippe Mathieu-Daudé
2019-09-09 10:59 ` Samuel Thibault
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=20190906095905.44hrurx3vlbqidkq@function \
--to=samuel.thibault@gnu.org \
--cc=c.heinze@precibake.com \
--cc=qemu-devel@nongnu.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 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).