From: Rick Jones <rick.jones2@hpe.com>
To: lartc@vger.kernel.org
Subject: Re: NAT, ICMP filtered, congestion troubles?
Date: Mon, 14 Dec 2015 17:36:21 +0000 [thread overview]
Message-ID: <566EFE15.8010509@hpe.com> (raw)
In-Reply-To: <20151204093758.GD3204@sv.lnf.it>
On 12/14/2015 03:29 AM, Marco Gaiarin wrote:
> So, practically speaking, at least for TCP connection, it is better
> to ALWAYS ''open'' ICMP packets alongside TCP packets.
>
> Right?
Well, that is my opinion. To leverage the phrase, that, and a couple
euros will get you an espresso.
There are others who hold a different opinion.
rick jones
speaking for myself alone
prev parent reply other threads:[~2015-12-14 17:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 9:37 NAT, ICMP filtered, congestion troubles? Marco Gaiarin
2015-12-04 18:46 ` Rick Jones
2015-12-14 11:29 ` Marco Gaiarin
2015-12-14 17:36 ` Rick Jones [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=566EFE15.8010509@hpe.com \
--to=rick.jones2@hpe.com \
--cc=lartc@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 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.