Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.os.linux.networking > #1907

Re: Need a method to prove incoming connection.

From Bit Twister <BitTwister@mouse-potato.com>
Newsgroups comp.os.linux.networking
Subject Re: Need a method to prove incoming connection.
Date 2013-01-17 16:26 +0000
Organization A noiseless patient Spider
Message-ID <slrnkfg9if.9k8.BitTwister@wb.home.test> (permalink)
References <slrnkfevcu.44v.BitTwister@wb.home.test> <kd9115$qi3$1@dont-email.me>

Show all headers | View raw


On Thu, 17 Jan 2013 14:15:01 +0000 (UTC), Joe Beanfish wrote:

> Perhaps "nc" aka "netcat" is what you want.

Yes, looks like just what I needed.

Frap. I am impressed.  :(
using first example at
  http://www.thegeekstuff.com/2012/04/nc-command-examples/


server xterm
[root@wb ~]#  nc -l 5060

client xterm
[root@wb ~]# nc -u localhost 5060

Status xterm
$ netstat | grep 5060
$

Alright, in the client xterm
helo
[root@wb ~]# 

and nothing in the server xterm.

I know 5060 works because ekiga fixed their server(s) and I can
run the callback test, and hear my voice echoed back from their
test connection.

Back to comp.os.linux.networking | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Need a method to prove incoming connection. Bit Twister <BitTwister@mouse-potato.com> - 2013-01-17 04:27 +0000
  Re: Need a method to prove incoming connection. Joe Beanfish <joebeanfish@nospam.duh> - 2013-01-17 14:15 +0000
    Re: Need a method to prove incoming connection. Bit Twister <BitTwister@mouse-potato.com> - 2013-01-17 16:26 +0000
      Re: Need a method to prove incoming connection. Bit Twister <BitTwister@mouse-potato.com> - 2013-01-17 16:46 +0000

csiph-web