From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/1] net/broken_ip: Rewrite into new API
Date: Thu, 2 May 2019 13:44:59 +0200 [thread overview]
Message-ID: <20190502114459.GA32460@dell5510> (raw)
In-Reply-To: <5cff91e0-c566-27c3-95dd-39dd4e2b6d0e@oracle.com>
Hi Alexey,
> Acked-by: Alexey Kodanev <alexey.kodanev@oracle.com>
...
> > +export ICMPV4_DATA_MAXSIZE=1472
> > +export ICMPV6_DATA_MAXSIZE=1452
> Since these variables are in the library, may be it would be better to tune
> them depending on an MTU of the tests interfaces?
Good idea. 1472 and 1452 are based on MTU = 1500 (IPv4: 1500 - 20 bytes for IPv4 header
- 8 bytes for ICMP header; IPv6: 1500 - 40 bytes for IPv6 header - 8 bytes for ICMP header),
which looks to me as the default for netns NICs and ethernet and wifi NICs,
but we should avoid failures when different MTU used.
I propose merging this version and add MTU detection support later.
I guess we don't need to check -s values passed to tst_icmp() (I guess nobody
set MTU < 1000, although it's not forbidden for IPv4). But I'd add this check
also into ns-icmpv[46]_sender.c.
+ off course other cleanup like merging ns-icmpv[46]_sender.c into single code would be nice,
but first I want to finish route rewriting.
> Also we can send more with fragmentation, but I guess ns-icmpv doesn't
> have proper support...
Do you mean to send packet big enough to have fragmentation on lhost?
+ setsockopt IP_PMTUDISC_DONT?
Kind regards,
Petr
next prev parent reply other threads:[~2019-05-02 11:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-27 5:39 [LTP] [PATCH 1/1] net/broken_ip: Rewrite into new API Petr Vorel
2019-04-30 15:42 ` Alexey Kodanev
2019-05-02 11:44 ` Petr Vorel [this message]
2019-05-06 14:32 ` Alexey Kodanev
2019-05-06 15:32 ` Petr Vorel
2019-05-06 15:42 ` Alexey Kodanev
2019-05-06 19:57 ` Petr Vorel
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=20190502114459.GA32460@dell5510 \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/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