AX25 to Telnet to CONV

AX25 to Telnet to CONV

[Bill Vodall WA7NWP]

I think I saw some examples on how to do this, but I can't find them now.

Does anybody have notes on how to connect an AX25 connection
to a telnet command with ax25d.conf in Linux?

I'd like a Connect Request to WA7NWP-17 to run the command 'telnet 
wetnet.net 3600' to hook up to the CONVER server.

Thanks,
Bill - WA7NWP

Re: AX25 to Telnet to CONV

[Dennis Boone]

 > I think I saw some examples on how to do this, but I can't find
 > them now.
 > 
 > Does anybody have notes on how to connect an AX25 connection to a
 > telnet command with ax25d.conf in Linux?
 > 
 > I'd like a Connect Request to WA7NWP-17 to run the command 'telnet
 > wetnet.net 3600' to hook up to the CONVER server.

You can use ax25d to invoke a command and hook its std{in,out} up
to the AX25 socket.  You could use telnet, but I use a shim called
axconv to create the socket connection to the convers server; it does
line ending fixup, will auto-sign the caller into convers, etc.

	http://he.fi/pub/ham/unix/linux/ax25/axconv.c.gz

The AX.25 howto has stuff on ax25d configuration:

	http://www.tldp.org/HOWTO/AX25-HOWTO/x1474.html

De

Re: AX25 to Telnet to CONV

[Bill Vodall WA7NWP]

Dennis Boone wrote:
>  > I think I saw some examples on how to do this, but I can't find
>  > them now.
>  > 
>  > Does anybody have notes on how to connect an AX25 connection to a
>  > telnet command with ax25d.conf in Linux?
>  > 
>  > I'd like a Connect Request to WA7NWP-17 to run the command 'telnet
>  > wetnet.net 3600' to hook up to the CONVER server.
> 
> You can use ax25d to invoke a command and hook its std{in,out} up
> to the AX25 socket.  You could use telnet, but I use a shim called
> axconv to create the socket connection to the convers server; it does
> line ending fixup, will auto-sign the caller into convers, etc.
> 
> 	http://he.fi/pub/ham/unix/linux/ax25/axconv.c.gz
> 
> The AX.25 howto has stuff on ax25d configuration:
> 
> 	http://www.tldp.org/HOWTO/AX25-HOWTO/x1474.html
> 
> De

It works.  Thank you very much.  I knew there had to be something like
this out there.

73,
Bill


++ W7EOC-9 AEA Gateway.  Type ? for help.
de MINOT (B,C,D,J,L,N,S,?) > C YYCONV
++ CONNECTED to YYCONV at MINOT
*** Connecting to wetnet.net, port 3600
*** Logging in as wa7nwp
*
* Access to channel 0 has been removed from this server.
* You will automatically be connected to channel 4424
conversd @ Wetnet Hessu's Tampa Ping-Pong conversd htpp-1.22
* Type /HELP for help.
*
* Enjoy the convers. Comments to n7ipb@wetnet.ampr.org.
* Set your /personal text if you haven't already done so. /? gives help.
*
*** There are 48 users online
*** There are 12 topics available
*** You created a new channel 4424.
*** Personal data set from file: Bill in Redmond Wa
*** ( 0:13) conversd made you a channel operator for channel 4424

User      Host       Via      Channel   Idle
wa7nwp    Wetnet                 4424    98s Bill in Redmond Wa
w7fqq     Wetnet                 4424    10m
*** Total of 2 users ***

Re: AX25 to Telnet to CONV

[Bill WA7NWP]

>  > I'd like a Connect Request to WA7NWP-17 to run the command 'telnet
>  > wetnet.net 3600' to hook up to the CONVER server.
> 
> You can use ax25d to invoke a command and hook its std{in,out} up
> to the AX25 socket.  You could use telnet, but I use a shim called
> axconv to create the socket connection to the convers server; it does
> line ending fixup, will auto-sign the caller into convers, etc.
> 
> 	http://he.fi/pub/ham/unix/linux/ax25/axconv.c.gz


This is working great and I'm currently putting it in place at the 2nd 
and 3rd system.   The problem is, like with all great little tools, one 
improvement on the system like this and an obsessive individual, like me 
, want's more more more...

Time now to take the next step and hook our "community packet servers" 
up to the local DXCluster box using the same AX25 connect and launch scheme.

Is anybody already doing this?  I think the axconv.c program might work 
directly or with a little tweaking.   Also I saw once, but can't find 
now, instructions on how to launch a telnet connection from ax25d.conf. 
  It would be much appreciated if somebody could point me at that info. 
  Any other hints and suggestions would also be appreciated.

73,
Bill - WA7NWP (making lots of packets...)

Re: AX25 to Telnet to CONV

[ronnie]

Hi Bill,

This is what we have in the ax25d.conf for incoming requests.
We have the spider dx cluster however.

#
<nr8>
NOCALL  * * * * * *  L
default         4 100  * *  *   * - sysop /spider/src/client client %s ax25
#



>
>>  > I'd like a Connect Request to WA7NWP-17 to run the command 'telnet
>>  > wetnet.net 3600' to hook up to the CONVER server.
>>
>> You can use ax25d to invoke a command and hook its std{in,out} up
>> to the AX25 socket.  You could use telnet, but I use a shim called
>> axconv to create the socket connection to the convers server; it does
>> line ending fixup, will auto-sign the caller into convers, etc.
>>
>> 	http://he.fi/pub/ham/unix/linux/ax25/axconv.c.gz
>
>
> This is working great and I'm currently putting it in place at the 2nd
> and 3rd system.   The problem is, like with all great little tools, one
> improvement on the system like this and an obsessive individual, like me
> , want's more more more...
>
> Time now to take the next step and hook our "community packet servers"
> up to the local DXCluster box using the same AX25 connect and launch
> scheme.
>
> Is anybody already doing this?  I think the axconv.c program might work
> directly or with a little tweaking.   Also I saw once, but can't find
> now, instructions on how to launch a telnet connection from ax25d.conf.
>   It would be much appreciated if somebody could point me at that info.
>   Any other hints and suggestions would also be appreciated.
>
> 73,
> Bill - WA7NWP (making lots of packets...)
> -
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Re: AX25 to Telnet to CONV

[Bill Vodall]

On Mon, 12 Dec 2005, ronnie wrote:

> Hi Bill,
> 
> This is what we have in the ax25d.conf for incoming requests.
> We have the spider dx cluster however.
> 
> default         4 100  * *  *   * - sysop /spider/src/client client %s ax25

Right.  That launches the dxcluster locally.   I'm looking for the magic
incantation to connect from packet on the local machine to a remote dxcluser
by telnet.  It'll be something like:

[NWPDX at *]
 default         * *  * *  *   * - root telnet w7xy:7373 %u


I'll figure it out shortly if nobody has it handy in their notes.


Thanks,
Bill - WA7NWP

Re: AX25 to Telnet to CONV

[Bill Vodall]

On Mon, 12 Dec 2005, Bill Vodall wrote:

> Right.  That launches the dxcluster locally.   I'm looking for the magic
> incantation to connect from packet on the local machine to a remote dxcluser
> by telnet.  It'll be something like:
> 
> [NWPDX at *]
>  default         * *  * *  *   * - root telnet w7xy:7373 %u

Is "axwrapper" the magic ingredient I'm missing?   The examples
show it being used with a "finger" implementation.

Hmmm.  I bet something like:

  axwrapper lynx --dump cool.web.site

would work.

73,
Bill

Re: AX25 to Telnet to CONV

[Dennis Boone]

 >  > Right.  That launches the dxcluster locally.  I'm looking for the
 >  > magic incantation to connect from packet on the local machine to a
 >  > remote dxcluser by telnet.  It'll be something like:
 >  > 
 >  > [NWPDX at *]
 >  > default         * *  * *  *   * - root telnet w7xy:7373 %u
 > 
 > Is "axwrapper" the magic ingredient I'm missing?   The examples
 > show it being used with a "finger" implementation.

Skip telnet, use axconv:

	http://he.fi/pub/ham/unix/linux/ax25/axconv.c.gz

I'd think long and hard about running such things as root.  Telnet,
in particular, might be used to get a local shell.

De

Re: AX25 to Telnet to CONV

[Bill Vodall]

On Wed, 14 Dec 2005, Dennis Boone wrote:

>  >  > [NWPDX at *]
>  >  > default         * *  * *  *   * - root telnet w7xy:7373 %u
>  > 
> 
> Skip telnet, use axconv:
> 
> 	http://he.fi/pub/ham/unix/linux/ax25/axconv.c.gz
> 

Thanks Dennis...

It's working right now.   I didn't realize that axconv had a [services]
option that allowed using different ports.


[NWPDX at *]
default         * *  * *  *   * - root /usr/local/bin/axconv axconv w7xy.net 7300

Now to add this to the five boxes I'm supporting...

73,
Bill - WA7NWP

AX25 now to dump a text file

[Bill Vodall WA7NWP]

>>
>>Skip telnet, use axconv:
>>
>>	http://he.fi/pub/ham/unix/linux/ax25/axconv.c.gz

That's working great at the systems I'm maintaining.  Now for the next 
little step.

I'd like to have a "axhelp" ax25 alias.  So connect to "axhelp" and it 
will dump a file of information and disconnect.

I think that's what this was doing:

 > root  /usr/local/sbin/axwrapper	axwrapper /usr/bin/finger finger

but I don't want to install the finger program on all the systems.

How about something like:

[AXHELP VIA *]
default  * * * * * *  - root  /bin/cat axhelp /etc/ax25/axports

(that's displaying the axports file as a test case.)


Suggestions or hints?

Thanks,
Bill - WA7NWP

ax25 Listen as a service

[Bill Vodall WA7NWP]

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

Re: ax25 Listen as a service

[Chuck Hast]

On 12/15/05, Bill Vodall WA7NWP <wa7nwp@jnos.org> wrote:
>
> 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?
>

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 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...???

--
Chuck Hast
To paraphrase my flight instructor;
"the only dumb question is the one you DID NOT ask resulting in my going
out and having to identify your bits and pieces in the midst of torn
and twisted metal."

Re: ax25 Listen as a service

[Chuck Hast]

On 12/15/05, Chuck Hast <wchast@gmail.com> wrote:
> On 12/15/05, Bill Vodall WA7NWP <wa7nwp@jnos.org> wrote:
> >
> > 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?
> >
>
> 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 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...???
>

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?

--
Chuck Hast
To paraphrase my flight instructor;
"the only dumb question is the one you DID NOT ask resulting in my going
out and having to identify your bits and pieces in the midst of torn
and twisted metal."

Re: ax25 Listen as a service

[Bill Vodall WA7NWP]

>>>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