From: Bill Vodall WA7NWP <wa7nwp@jnos.org>
To: linux-hams@vger.kernel.org
Subject: ax25 Listen as a service
Date: Thu, 15 Dec 2005 14:23:32 -0800 [thread overview]
Message-ID: <43A1ECE4.1020406@jnos.org> (raw)
In-Reply-To: <43A1BAE9.4000009@jnos.org>
Attention deficit? Easily distracted. Couldn't be me....
While playing with the UroNode as a program launched from a socket, it
dawned on me that it might be possible to do the very same with
''listen.'' Often I SSH in to a remote system simply to watch the
packet activity in the area. I don't need the shell for that, just the
listen.
So I gave it a try:
--- in /etc/services ---
axlisten 3695/tcp # Linux ax25 listening
--- in /etc/xinetd.conf I added ---
service axlisten
{
socket_type = stream
protocol = tcp
wait = no
user = root
server = /usr/bin/listen
server_args = -act
}
---
Then I sent a -HUP to xinetd and tried it.
telnet localhost 3695
Wow? I see packets scrolling by. Pretty cool!
Now the question for the group. Is there a better way to do this? Is
there anything inherently dangerous with doing this where I'm leaving
the systems wide open to some exploit?
Thanks,
Bill - WA7NWP
next prev parent reply other threads:[~2005-12-15 22:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0006$01c12a35$017630fc@arti>
2005-12-08 21:43 ` AX25 to Telnet to CONV Bill Vodall WA7NWP
2005-12-08 22:02 ` Dennis Boone
2005-12-09 0:40 ` Bill Vodall WA7NWP
2005-12-11 21:54 ` Bill WA7NWP
2005-12-12 7:55 ` ronnie
2005-12-12 21:00 ` Bill Vodall
2005-12-14 16:17 ` Bill Vodall
2005-12-14 16:44 ` Dennis Boone
2005-12-14 17:24 ` Bill Vodall
2005-12-15 18:50 ` AX25 now to dump a text file Bill Vodall WA7NWP
2005-12-15 22:23 ` Bill Vodall WA7NWP [this message]
2005-12-16 3:18 ` ax25 Listen as a service Chuck Hast
2005-12-16 3:44 ` Chuck Hast
2005-12-16 18:40 ` Bill Vodall WA7NWP
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=43A1ECE4.1020406@jnos.org \
--to=wa7nwp@jnos.org \
--cc=linux-hams@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.