From: Joe Goforth <joego@mcn.org>
To: folkert <folkert@vanheusden.com>, David Ranch <linux-hams@trinnet.net>
Cc: linux-hams@vger.kernel.org
Subject: Re: Fw: Fw: AX.25
Date: Fri, 14 Feb 2014 13:04:15 -0800 [thread overview]
Message-ID: <52FE84CF.7010407@mcn.org> (raw)
In-Reply-To: <20140214203115.GX30054@belle.intranet.vanheusden.com>
Hi folkert, I'm on the same wavelength as you are. I have two beaglebone
boards with tnc-x packet using linux angstrom. It's been a real battle
to find a simple way to communicate between the two without getting tied
into the various software packages. At this point I realize that I
should have gone to the raspberry-pi board but I have money tied up in
the two boards I have now. To top it off the beaglebone black is the one
all the support is going to now and I have a beaglebone white. This has
caused me to learn a lot more which is good in the end. What I have
finally come down to is this which is kind of a cool experimental
platform to talk between two stations.
Setup the basic ax25d stuff so you have your ax25d daemon running. You
don't need to worry about getting the tcp stuff all routed. Once you
have that going you can setup a port to listen like this
listen MYPORT >> listen.log&
at this point you can log any incoming to the listen.log and to bring it
to the console;
tail -f listen.log
On your other station you can use the program "beacon" to send messages;
beacon -m -d KE6ACW-1 MYPORT2 "my message I want to send"
At this point you have setup a simple communication system and you can
pipe the listen program to a python (or your flavor) script to process
or send the data any way you like.
I'm still looking for a better program than beacon to do the transmit so
that might be a program that needs to be written. There are a lot of
programs with source code out there for reference. Many of the linux
APRS type programs have this code. Maybe someone out there has a better
solution but that is about as simple as I could get it on an embedded
system.
--Joe Goforth
KE6ACW
On 2/14/2014 12:31 PM, folkert wrote:
>> The AMPR group at http://wiki.ampr.org/index.php/Main_Page and it's
>> email list at 44net@hamradio.ucsd.edu will be the best place to
>> follow up on getting Internet forwarding going. The one challenge
>> for you will be that the AMPR group is focused for licensed amateur
>> radio (HAMs) who have built extensive, worldwide ax25ipd enabled
>> overlay network. I don't know if they would give you any IPs unless
>> you and your third party traffic would be coming from licensed HAMs.
>> I leave that to you to investigate.
> Ok. Yeah I'm trying to setup a free for all access for all and do
> whatever you like network.
>
>> Beyond that previous key point, I don't know in your email if you
>> really intend to use the very old Baycom TNCs (require true 16550
>> serial UARTS, not USB-to-serial adapters) or you're referring to
>> Thomas Sailers's excellent but deprecated "soundmodem" that used to
>> be hosted on the Baycom website (now gone). Instead, I encourage
> Both. I have old pcs with real serial ports, I have a raspberry pi with
> a sound module and a couple of rpi-s with tnc-pi hardware.
>
>> you to check out Direwolf which is a vastly superior sound card TNC
>> - http://home.comcast.net/~wb2osz/site/ . Not only does it support
>> superior decoding of 1200 and 9600 packet but also integrated APRS
>> and AGWPE support.
> Ah!
> Will do
> thanks
>
>
> Folkert van Heusden
>
next prev parent reply other threads:[~2014-02-14 21:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 15:19 Fw: Fw: AX.25 folkert
2014-02-14 17:16 ` AX.25 Matt VK2RQ
2014-02-14 20:20 ` AX.25 folkert
2014-02-14 17:21 ` Fw: Fw: AX.25 David Ranch
2014-02-14 17:43 ` AX.25 Matt VK2RQ
2014-02-14 20:33 ` AX.25 folkert
2014-02-14 20:57 ` AX.25 Matt VK2RQ
2014-02-14 21:45 ` AX.25 folkert
2014-02-14 20:31 ` Fw: Fw: AX.25 folkert
2014-02-14 21:04 ` Joe Goforth [this message]
2014-02-14 22:24 ` David Ranch
2014-02-14 23:48 ` Joe Goforth
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=52FE84CF.7010407@mcn.org \
--to=joego@mcn.org \
--cc=folkert@vanheusden.com \
--cc=linux-hams@trinnet.net \
--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.