[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ✘ntrip:// and tcp://
From: |
Gary E. Miller |
Subject: |
Re: ✘ntrip:// and tcp:// |
Date: |
Fri, 15 Oct 2021 11:07:25 -0700 |
Yo Paul!
On Fri, 15 Oct 2021 17:06:54 +0300
Paul Fertser <fercerpav@gmail.com> wrote:
> > I need something that will sit there, accepting multiple,
> > consecurtive connects.
>
> For cases like that I suggest "socat". Widely available and can do
> what you ask for and much more.
The man page is over 3,300 lines long. Any idea how I could do
what netcat is doing here:
$ gpspipe -r | nc -l -p 2948
a) read from the pipe
b) listen for tcp on port 2948
c) on tcp connect to 2948, send piped in data to tcp clien
RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
gem@rellim.com Tel:+1 541 382 8588
Veritas liberabit vos. -- Quid est veritas?
"If you can't measure it, you can't improve it." - Lord Kelvin
pgpyCeBVJ1Fmy.pgp
Description: OpenPGP digital signature
- ✘ntrip:// and tcp://, Gary E. Miller, 2021/10/14
- Re: ✘ntrip:// and tcp://, Fred Wright, 2021/10/14
- Re: ✘ntrip:// and tcp://, Hal Murray, 2021/10/15
- Re: ✘ntrip:// and tcp://, Paul Fertser, 2021/10/15
- Re: ✘ntrip:// and tcp://,
Gary E. Miller <=
- Re: ✘ntrip:// and tcp://, Paul Fertser, 2021/10/15
- Re: ✘ntrip:// and tcp://, Gary E. Miller, 2021/10/15
Re: ✘ntrip:// and tcp://, Nick Taylor, 2021/10/15