Yes, spiped is trying to bind the /tmp/blah socket, yet the file /tmp/blah
already exists. Please delete that file, then run your spiped -e command, and
then run the other program which you want to send data to /tmp/blah.
(if that other program is also trying to bind /tmp/blah, then it probably needs
to be re-thought. The "server" program is the one which binds the socket; the
"client" program merely connects to it.)
On Wed, Jun 07, 2017 at 10:14:11PM +0800, JunglHilt wrote:
> ok so I have the following :
> A process which created a unix domain socket (/tmp/blah) on my local
> machine that I want to send to a remote machine 184.108.40.206:9999 and end
> up as /tmp/blah on which side has another process that wants to read
> from the socket.
> On the sending side I have :
> spiped -e -F -s /tmp/blah -t 220.127.116.11:9999 -k key.key
> yet it complains that the address is already in use...I thought that
> the intent of the source directive is to read from given source but
> perhaps it is trying to bind to that socket?
> I'm not that familiar with sockets so please excuse any paradigms that
> I have gotten wrong.
> On 7 June 2017 at 20:07, Colin Percival <email@example.com>
> On 06/07/17 01:17, JunglHilt wrote:
> > I'm trying to forward a unix domain socket securely over the
> internet and was
> > wondering if this is possible with spiped?
> > I have tried specifying a socket as the source(on one side) and
> target on the
> > other yet the target socket doesn't get created, so not sure if
> this is
> > possible..?
> spiped doesn't create the target socket. spiped connects to the target
> socket, which should have been created by whatever process you want to
> connect to.
> Colin Percival
> Security Officer Emeritus, FreeBSD | The power to serve
> Founder, Tarsnap | www.tarsnap.com | Online backups for the truly
> 1. http://18.104.22.168:9999/
> 2. http://22.214.171.124:9999/
> 3. mailto:firstname.lastname@example.org
> 4. http://www.tarsnap.com/