From: Miroslav Skoric <skoric@uns.ac.rs>
To: David Ranch <linux-hams@trinnet.net>,
Linux Hams <linux-hams@vger.kernel.org>
Subject: Re: Linpac 0.21 (AX.25 packet radio application) posted
Date: Fri, 29 May 2015 20:01:22 +0200 [thread overview]
Message-ID: <5568A972.5010104@uns.ac.rs> (raw)
In-Reply-To: <55669E84.2020500@trinnet.net>
On 05/28/2015 06:50 AM, David Ranch wrote:
>
>> In fact, what I want to do is to mimic real client-to-server
>> communication as if a real packet network is present. Any idea?
>
> Well, I'm still not quiet following you here but it's worth mentioning
> that the Linpac 1.x proto code is designed to be a client/server design.
> It's server communicates to the Linux AX.25 stack and can fully
> operate with remote users. For local users, the Linpac clients (Ncurses
> or Java) connects to the Linpac backend via a TCP connection. This code
> isn't completely functional at the moment.
>
Hi David,
Maybe I was not clear about what I wanted to have: I meant, let us
suppose that there is an operational Linux AX.25 stack + a node software
(such as FPAC or Uronode, etc.) + FBB bbs on a computer. Now I wonder if
it would be possible to add Linpac to that machine so that Linpac could
access FBB mails in a way as if uses another computer and ham radio to
access the bbs computer by air? Or in the other words: Could Linpac be
installed to access a simulated packet network (a node + fbb) in the
same computer, so to handle mails within the fbb?
I suppose that something like that might be achieved by some tcpip
operation (such as telnet localhost, or something similar), but I'd like
to rather see it by axip or axudp connection that better mimics real ham
radio traffic. (If you ask me for reasons why I asked for that, well I
am just not satisfied with FBB's client applications xfbbC and similar
solutions.)
Misko
next prev parent reply other threads:[~2015-05-29 18:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-25 17:51 Linpac 0.21 (AX.25 packet radio application) posted David Ranch
2015-05-27 16:11 ` Miroslav Skoric
2015-05-28 4:50 ` David Ranch
2015-05-29 18:01 ` Miroslav Skoric [this message]
2015-05-29 20:47 ` David Ranch
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=5568A972.5010104@uns.ac.rs \
--to=skoric@uns.ac.rs \
--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.