[FADCA] Re: OKP switch

[Chuck Hast]

On 1/13/07, bud Thompson <budt at cfl.rr.com> wrote:
> See my bottom posting . . .
>
> ----- Original Message -----
> From: <W4AWP at att.net>
> To: "bud Thompson" <budt at cfl.rr.com>
> Cc: "Ray Cook" <raycook at pobox.com>; "Charles S Schuman"
> <k4gbb at earthlink.net>; "W4AWP" <w4awp at att.net>; "Jim Morrell"
> <jimmor1 at bellsouth.net>; "Russell Oder" <oderr at bellsouth.net>; "Charlie
> N3PPC" <ccrook at cfl.rr.com>
> Sent: Saturday, January 13, 2007 08:32
> Subject: Re: OKP switch
>
>
> > Hi Bud, this is Don, W4AWP in Ray's area.  I easily and quickly connected
> > to N3PPC-8 last night from WD4SEN-8 and then asked N3PPC-8 to connect me
> > to N0IA-10.  All this worked very well.  Is is possible to connect in a
> > way that keyboard to keyboard could be used, if so, how would one do it?
> > Also, is it possible to get a listing of where all the different FPAC
> > switches and users are located?  Thanks for all you guys are doing.  This
> > system should be very helpful if and when needed to be called on.   73,
> > Don, W4AWP, Fleming Island.
>
>
> * * *
> Hi, Don -
>
> When Ray or K4GBB fixes the routing from OPK to 407277 so it will go via the
> RF layer you'll be able to reach the Orlando node from OPK this way from
> 144.93.
>
> C node v wd4sen-9, 407277
> or
> C n4plz-8 v wd4sen-9, 407277
>
> This morning the one-way travel time was about three seconds south to north.
>
> Keyboard to keyboard will work providing:
>
> 1.  Each keyboard packet station is someplace on the network and available
> for a connection
> 2.  The network between them is in tact
> 3.  Both operators are available at the same time to keyboard chat.
>
> To connect to a station anywhere on the network from any LAN on the
> network - the generic command is:
>
> C <target> V <local switch call> <network address where target is listening>
>
> The example from the OPK LAN on 144.93 would be
>
> C w4mco-10 V wd4sen-9 407277
>
> which would connect you to the Orange County ARES Telpac Node in Orlando -
> the furthest link via RF right now from OPK.
>
> (Of course W4MCO-10 is not a keyboard chat node, but you'll be on the telpac
> node in keyboard mode and can play around.)
>
> I'll work on a list of nodes/LANs/network addresses and publish it sometime
> today -I need to bring it up to date.
>
> Right now the RF layer links the following Local Area Networks (LANs) in NE
> and EC Florida.  This table shows the LAN user frequencies, baud rate for
> each, the mycall of the node/switch  (i.e. WD4SEN-8 is the node
> function, WD4SEN-9 is the switch function,) and the network address.
>
> Orange Park    144.93 1200b  WD4SEN-8/9 address 904272
> ST. Augustine  144.99 1200b   KF4MX-7       address 904829
> DAB                  145.05  1200b N4WKQ-5       address 386677
> DeLand             144.91  1200b N3PPC-8/9    address 386335
> DeLand             446,.55  9.6kb  N3PPC-8/9   address 386333
> Orlando             145.07  1200b N4PLZ-8/9     address 407277
>
> You will not find many users so far, but with you there is at least one!
>
> NOTE that the DAB and STA sites are ROSE, not FPAC so they operate slightly
> differently - there is no connection to the NODE on those, per se.  If you
> want to learn the stations that have been on the LAN frequencies of a ROSE
> you need to connect to HEARD <network address>
>
> Example from Orange Park on 144.93 to DAB LAN
>
> c heard v wd4sen-9 386677
>
> To learn what stations have been on an FPAC LAN first connect to the NODE,
> and then use the MH P command where P is the port number for the LAN you
> want.  Note that 2M LANS are port 0 and 9.6kb LANS are port 1.
>
> C node v WD4SEN-9 386335
>
> would put you on the DeLand NODE then
>
> MH 1
>
> would provide the stations heard on the 9.6kb user port.
>
> Hope this helps - won't be long before I'll have some user "how to"
> information developed.

Don, FPAC has a lot of information available in the WP or White Pages
db that it collects and keeps, for example, I just connected to the local
switch and did a wp command on your call:


KP4DJT-8 (Commands = ?) : wp w4awp
FPAC White Pages database : 3876 callsigns
Callsign Ok  Last update      DNIC address type Locator City digis
W4AWP-0   Y 10/11/06 16:13 => 3100 904272  User
W4AWP-1   Y 12/01/07 21:57 => 3100 904272  User
W4AWP-2   Y 21/11/06 13:18 => 3100 904272  User
W4AWP-3   Y 14/12/06 20:25 => 3100 904272  User


I tried to do a connect to your station:


KP4DJT-8 (Commands = ?) : c w4awp-1
Trying (fpac wp) W4AWP-1 @ 3100,904272... Type <RETURN> to abort
*** Failure with W4AWP-1 @ 3100,904272
*** Remote Station cleared connection

And it appears that your end was busy or for some reason your station
did not accept the call as indicated by the last line. Perhaps the CONOK
command is off or whatever.

If WP knows the whereabouts of a keyboarder all you have to do at the
node command prompt is issue a connect command and wp will deal
with the numbrs game.

Indeed if you want to connect to a station, say I wanted to connect to you
I do not even need to know the address you are at, all I need is the local
node call (Bud, you all found out about this one). So if at the TNC command
prompt I do:
c w4awp-1 v kp4djt-8
The node will jump in the middle do a WP lookup and start setting up the
path to you from my switch.

Now if for some reason WP has bad data on the address of you destination
or the user is on a ROSE or a old DOS FPAC switch then you will need to
know the X.121 address of the user and do a connection like Bub indicated.
But as long as they are on the FPAC Linux network and keep their WP info
up to date WP will take care of the routing for you.

I usually will connect to the switch that is local to my area of interest and do
a Mheard to see who is on what port:

WD4SEN-8 (Commands = ?) : m
Last 20 Heard list for all ports :
Callsign  Port   Pkts-rcvd Mode Time ago
KF4MX-5   8      28692     FPAC 00s
N4WKQ-7   8      5970      FPAC 01s
WD4SEN    0      4415      AX25 01m 28s
K4GBB-9   9      52621     FPAC 21m 35s
WD4SEN-3  0      1851      AX25 1h 01m 55s
W4AWP-1   0      3705      AX25 1h 31m 03s
N4PLZ-9   9      66266     FPAC 2h 32m 32s
WD4SEN-9  8      18        FPAC 2h 36m 46s
WD4SEN-2  0      670       AX25 15h 36m 09s
W4AWP-3   0      625       AX25 16h 20m 33s
K5WTA     0      582       AX25 19h 46m 55s
WD4SEN-10 0      152       AX25 41h 06m 33s
N4WKQ     8      4         None 132h 32m 27s
N4WKQ     8      4         None 132h 32m 27s
W4AWP     0      2418      AX25 133h 27m 52s
N5SN-9    8      156       AX25 136h 23m 00s
KP4DJT    8      4         None 205h 55m 08s
N4WKQ-1   9      7         AX25 304h 45m 20s
N4PLZ-8   9      17        AX25 372h 27m 47s
N5SN-9    9      21        AX25 376h 36m 54s


Then I will pick a call of interest out of the list and attempt to
connect to it.


-- 
Chuck Hast  -- KP4DJT --
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."