From: Bill Vodall WA7NWP <wa7nwp@jnos.org>
To: linux-hams@vger.kernel.org
Subject: Re: ax25 Listen as a service
Date: Fri, 16 Dec 2005 10:40:50 -0800 [thread overview]
Message-ID: <43A30A32.9020900@jnos.org> (raw)
In-Reply-To: <620c90570512151944n1bc95c58w9c1e0a0a4bcdcc1@mail.gmail.com>
>>>Then I sent a -HUP to xinetd and tried it.
>>>
>>> telnet localhost 3695
>>>
>>>Wow? I see packets scrolling by. Pretty cool!
>>Went to try that port and found this in my services file
>>bmc-data-coll 3695/tcp # BMC Data Collection
>>bmc-data-coll 3695/udp # BMC Data Collection
>>
>>Not sure what it is but it is used by something.
I'm sure there are some Internet guru's on here to correct me if I'm
wrong... My assumption is that these incoming ports are assigned to
this BMC process - but unless you actually install and use the BMC
program, there's no real reason not to re-use the ports.
I picked 3695 for my Listen experiment simply because it's one more then
the 3694 used by UroNode.
.. I have a machine
>>set up that I ssh to listen and get a listen screen but no one else has
>>been able to do it on other machines, indeed I have not either, so not
>>sure what I did that made it work on one machine...???
Are you trying the listen as a service? Or are you running it as an
application from ssh? Hmmm. I have to try that as it might be a
better way yet to do what I want.
> Bill, our FPAC Linux boxes use port 10093 UDP to link boxes over the
> intenet, I was looking and see that the following block is not used:
> # 10081-10099 Unassigned
> Wonder if we could get that whole block assigned for amateur radio
> applications?
I know Scott has at least one port officially assigned for his OpenTrac
project. I'm sure others could be requested for various ham
applications but I personally don't think it's worth the effort. There
are so few of us and it's so easy to move ports around..
Bill - WA7NWP
prev parent reply other threads:[~2005-12-16 18:40 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 ` ax25 Listen as a service Bill Vodall WA7NWP
2005-12-16 3:18 ` Chuck Hast
2005-12-16 3:44 ` Chuck Hast
2005-12-16 18:40 ` Bill Vodall WA7NWP [this message]
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=43A30A32.9020900@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.