From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Julian Anastasov <ja@ssi.bg>
Cc: Simon Horman <horms@verge.net.au>,
lvs-devel@vger.kernel.org, netfilter-devel@vger.kernel.org,
Alex Gartrell <agartrell@fb.com>,
Jacky Hu <hengqing.hu@gmail.com>,
jacky.hu@walmart.com, jason.niesz@walmart.com
Subject: Re: [PATCH net] ipvs: do not schedule icmp errors from tunnels
Date: Sat, 13 Apr 2019 15:00:19 +0200 [thread overview]
Message-ID: <20190413130019.rcdbwedzd4xv5fud@salvia> (raw)
In-Reply-To: <20190331102452.7415-1-ja@ssi.bg>
On Sun, Mar 31, 2019 at 01:24:52PM +0300, Julian Anastasov wrote:
> We can receive ICMP errors from client or from
> tunneling real server. While the former can be
> scheduled to real server, the latter should
> not be scheduled, they are decapsulated only when
> existing connection is found.
Applied, thanks.
prev parent reply other threads:[~2019-04-13 13:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-31 10:24 [PATCH net] ipvs: do not schedule icmp errors from tunnels Julian Anastasov
2019-04-03 7:45 ` Simon Horman
2019-04-03 20:43 ` Julian Anastasov
2019-04-13 13:00 ` Pablo Neira Ayuso [this message]
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=20190413130019.rcdbwedzd4xv5fud@salvia \
--to=pablo@netfilter.org \
--cc=agartrell@fb.com \
--cc=hengqing.hu@gmail.com \
--cc=horms@verge.net.au \
--cc=ja@ssi.bg \
--cc=jacky.hu@walmart.com \
--cc=jason.niesz@walmart.com \
--cc=lvs-devel@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.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).