bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vincent Li <vincent.mc.li@gmail.com>
To: Martin KaFai Lau <kafai@fb.com>
Cc: bpf@vger.kernel.org, Daniel Borkmann <daniel@iogearbox.net>
Subject: Re: [PATCH bpf-next] selftests, bpf: test_tc_tunnel.sh nc: cannot use -p and -l
Date: Tue, 20 Jul 2021 12:38:06 -0700	[thread overview]
Message-ID: <CAK3+h2ygPYPkqusDBrYwGPtDga+XNug-Jh-NE8V_kbWMM7-WBw@mail.gmail.com> (raw)
In-Reply-To: <20210720181913.ps2qj7ttxszijv5i@kafai-mbp.dhcp.thefacebook.com>

On Tue, Jul 20, 2021 at 11:19 AM Martin KaFai Lau <kafai@fb.com> wrote:
>
> On Mon, Jul 19, 2021 at 03:30:22PM -0700, Vincent Li wrote:
> > When run test_tc_tunnel.sh, it complains following error
> >
> > ipip
> > encap 192.168.1.1 to 192.168.1.2, type ipip, mac none len 100
> > test basic connectivity
> > nc: cannot use -p and -l
> >
> > nc man page has:
> >
> >      -l  Listen for an incoming connection rather than initiating
> >          a connection to a remote host.Cannot be used together with
> >          any of the options -psxz. Additionally, any timeouts specified
> >          with the -w option are ignored.
> >
> > Correct nc in server_listen().
> I have two distros and both work with -p in listen.
> However, they also work the same without -p, so it makes sense to remove it.
>

Thanks Martin, I use Centos 8 distro.

> Acked-by: Martin KaFai Lau <kafai@fb.com>

  reply	other threads:[~2021-07-20 19:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19 22:30 [PATCH bpf-next] selftests, bpf: test_tc_tunnel.sh nc: cannot use -p and -l Vincent Li
2021-07-20 18:19 ` Martin KaFai Lau
2021-07-20 19:38   ` Vincent Li [this message]
2021-07-20 20:50 ` patchwork-bot+netdevbpf

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=CAK3+h2ygPYPkqusDBrYwGPtDga+XNug-Jh-NE8V_kbWMM7-WBw@mail.gmail.com \
    --to=vincent.mc.li@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kafai@fb.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).