From: Christian Franke <Christian.Franke@t-online.de>
To: cygwin@cygwin.com
Subject: Re: After installing nc (netcat), nc.exe is not found
Date: Thu, 12 Jul 2018 13:38:00 -0000 [thread overview]
Message-ID: <969fa9e7-898f-37fc-2a60-b3d298bdc9c1@t-online.de> (raw)
In-Reply-To: <493a1f10-c8e3-44d8-d10a-e5ddcb08b4a3@SystematicSw.ab.ca>
Brian Inglis wrote:
> On 2018-07-11 14:10, Mark Hansen wrote:
>> ... and I know better than to ask my corporate IT folks to make an exception for
>> me :(
> Perhaps you could use other packages to get your work done, ...
>
Busybox provides a tiny version of nc:
$ busybox nc
BusyBox v1.23.2 (2015-07-05 18:51:40 CEST) multi-call binary.
Usage: nc [OPTIONS] HOST PORT - connect
nc [OPTIONS] -l -p PORT [HOST] [PORT] - listen
-e PROG Run PROG after connect (must be last)
-l Listen mode, for inbound connects
-lk With -e, provides persistent server
-p PORT Local port
-s ADDR Local address
-w SEC Timeout for connects and final net reads
-i SEC Delay interval for lines sent
-n Don't do DNS resolution
-u UDP mode
-v Verbose
-o FILE Hex dump traffic
-z Zero-I/O mode (scanning)
--
Christian
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-07-12 12:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 17:10 Mark Hansen
2018-07-11 17:35 ` Heavenly Avenger
2018-07-11 19:34 ` Mark Hansen
2018-07-11 19:46 ` Mark Hansen
2018-07-11 19:50 ` Mark Hansen
2018-07-11 20:00 ` Mark Hansen
2018-07-12 2:37 ` Heavenly Avenger
2018-07-11 20:10 ` Andrey Repin
2018-07-11 20:10 ` Gary Johnson
2018-07-11 20:35 ` Mark Hansen
2018-07-12 1:30 ` Mark Hansen
2018-07-12 3:36 ` Gary Johnson
2018-07-12 7:46 ` Brian Inglis
2018-07-12 13:38 ` Christian Franke [this message]
2018-07-12 9:14 ` Erik Soderquist
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=969fa9e7-898f-37fc-2a60-b3d298bdc9c1@t-online.de \
--to=christian.franke@t-online.de \
--cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).