[FADCA] Interesting Observation

Tue, 17 Dec 2002 15:53:29 -0500

Rick,
If we could come up with a new AX.25 piece for the
RF end of it, you could also use a neat part of FPAC
that is little known, that being the 'M' or more bit.
Then if you have to go across the FPAC network you will
not be sending a lot of fragmented IP frames just one
IP frame which gets fragged down at the AX.25 level, the
M bit is set until the final one goes by at which time
it gets reset telling the far end that the last fragment
of a larger IP frame has gone through.

We used to use it on a path between Tampa and the Texas
ROSE/FPAc network with TNOS it worked great and let you
send IP frames larger than 256 bytes minus the IP overhead.

There is also a mechanisim to send larger frames than 256
bytes under FPAC, but not sure how it is used on the user
end.

What is needed is a replacement for BPQ that will take
advantage of this.

It would also work at a point where you were just doing
last mile stuff, you would still be able to send the IP
data and either frag at the AX.25 entre point and rebuild
at the exit point or send frames larger than 256 bytes.

Under KISS using UI frames it is already done, and indeed
that would be the best fix of all, FPAC Linux is already
supposed to handle that format, and of course if you had
a LINUX box running native IP with the AX.25 stack on it 
you already have the ability to run  both.

It is on the windows/dos end where things need to be fixed.
A new AX.25 piece is really needed.

The AGW packet engine goes a long way in this sense but I
can not get his code to talk to a FPAC switch using the X.121
addressing. It blows up when you try to do a connect.

I think it would work as a access point using UI frames,
he does not support IP in connected mode which is being a
bit narrow minded because there are situations where connected
mode works much better than UI mode.

> -----Original Message-----
> From: Rick Muething [mailto:[email protected]]
> Sent: Tuesday, December 17, 2002 10:41 AM
> To: [email protected]
> Subject: RE: [FADCA] Interesting Observation
> 
> 
> Dave,
>  This is an interesting question. It is good timing since I 
> am just now
> working on expanding the WL2K SMS concept. It would work 
> something like the
> following explanation.
> 
> I think it could easily be expanded to tie into BPQ node or a 
> FBB Telnet
> port.  If this looks at all interesting to you we should work up some
> additional details on how to tie in a BPQ node or a FBB Telnet port.
> 
> BASIC WL2K TELPAC concept:
> The current SMS node would be expanded to a new Node (lets 
> call it TELPAC,
> short for  ...TELnet via PACket).  It would be a virtually 
> stateless,  no
> data base node.  It would work like this:
> 
>  WL2K CMBO<>WL2K PMBO---WL2KTelnet server<>TELPAC 
> node<>User(e.g. W4ABC)
>         TCP/IP                         TELNET      AX.25 packet
> 
> 1) When TELPAC receives a connect request from a packet user 
> ...lets say
> W4ABC It acknowledges the AX.25 connect to the user. The 
> packet connect can
> be either in BBS<>BBS mode or in keyboard mode just like it 
> was a normal
> WL2K packet port. TELPAC then starts a Telnet session with a 
> WL2K Telnet
> server under the call of W4ABC.  (This could be over a dial 
> up but of course
> a full time IP connection is preferred)
> 
> 2) The WL2K Telnet server replies as normal and works either in BBS or
> Keyboard mode as it does now.
> 
> 3) From then on the TELPAC simply acts like a bridge 
> connecting the AX.25
> packet to the Telnet protocol.  It has no local storage other 
> than buffering
> and what ever state info is necessary to make the bridge 
> work.  The Telnet
> protocol and the AX.25 can both support multiple simultaneous 
> connections
> and handle the inherent delays associated with packet 
> including digipeating
> and retries.
> 
> This would give any packet user in range of a TELPAC node:
> Full access to the WL2K System including NPMBOs known to WL2K.
> Full "on demand" access to weather and info bulletin
> Email to any internet email address.
> Mixed radio and email addresses with attachments
> Custom Weather and News via email subscription services.
> Standard WL2K Spam and virus blocking.
> + additional options if the TELPAC node had BPQ or FBB Telnet 
> connectivity.
> 
> If there were sufficient interest the TELPAC node could be written for
> Windows and Linux machines.
> 
> Comments welcome.
> 
> Rick KN6KB
> 
> 
> 
> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]]On
> Behalf Of Dave Calder
> Sent: Tuesday, December 17, 2002 0831 AM
> To: [email protected]
> Subject: RE: [FADCA] Interesting Observation
> 
> 
> Can you make SMS talk to BPQ. I could then use it right beside FBB.
> Someone
> Could pick SMS instead of BBS in the node.
> 
> Dave
> n4zkf
> 
> 
> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> On Behalf Of Rick Muething
> Sent: Monday, December 16, 2002 8:55 PM
> To: [email protected]
> Subject: RE: [FADCA] Interesting Observation
> 
> All,
> 
> I have been working on a concept for linking very simple 
> Packet nodes (a
> TNC, Radio, Internet connection and minimal Win 9X or Linux CPU)with
> WL2K's
> Telnet servers.  This could offer the wide coverage, standard 
> email with
> attachments, and rapid forwarding of the internet with the wireless
> "last
> mile" performance of packet.  Will let you know when this 
> gets closer to
> reality. We have to do something like this to keep packet alive!
> 
> Rick KN6KB
> Winlink Development Team
> 
> -----Original Message-----
> From: [email protected] 
[mailto:[email protected]]On
Behalf Of bud Thompson
Sent: Monday, December 16, 2002 2028 PM
To: [email protected]
Cc: W5ZIT
Subject: [FADCA] Interesting Observation

One of my ham friends who lives in his motor home and travels around the
country ....

"Regular packet is all but dead here in Tucson, the birthplace of
packet.  I
hear one station beaconing on 01, and he is beaconing an APRS location.
It
is a TCP/IP station that I can't connect to and I see him over on 144.39
with the same beacon.  I guess he can't set the beacons different on
different ports."

So, we have a lot of work to do.

73,
bud N0IA

--- StripMime Report -- processed MIME parts ---
multipart/alternative
  text/plain (text body -- kept)
  text/html
The reason this message is shown is because the post was in HTML
or had an attachment. Attachments are not allowed.
Please post in Plain-Text only.---
_______________________________________________
FADCA mailing list
[email protected]
http://mailman.qth.net/mailman/listinfo/fadca

_______________________________________________
FADCA mailing list
[email protected]
http://mailman.qth.net/mailman/listinfo/fadca

_______________________________________________
FADCA mailing list
[email protected]
http://mailman.qth.net/mailman/listinfo/fadca

_______________________________________________
FADCA mailing list
[email protected]
http://mailman.qth.net/mailman/listinfo/fadca

*****************************************************************
This e-mail and any files transmitted with it are confidential and are
intended solely for the use of the individual or entity to whom it is
addressed. If you have received this transmission in error, please notify
the sender immediately and destroy any hard copies you may have printed and
remove all copies of the e-mail from your hard drive. Opinions, conclusions
and other information in this message that do not relate to the official
business of Utility Partners, Inc shall be understood as neither given nor
endorsed by it.

Visit us on the web at http://www.utilpart.com 
*****************************************************************