[App_rpt-users] aprs password for app_gps

Bogdan Diaconescu yo3iiu at yo3iiu.ro
Sun Jan 23 17:27:16 EST 2011


The protocol is quite simple and the source for callpass is included in
the xastir source. Though, reverse engineering it seems a lot more fun :)

Regards,
Bogdan - YO3IIU

>
> The heck with all this confusion regarding APRS passwords!!
>
> I just reverse engineered the password algorithm and will make
> a password generator (and will also automatically generate a password
> for Portal-generate configurations).
>
> JIM
>
>> Date: Sun, 23 Jan 2011 15:49:55 +0200
>> From: yo3iiu at yo3iiu.ro
>> To: rpt2 at chuck.midlandsnetworking.com
>> CC: app_rpt-users at ohnosec.org
>> Subject: Re: [App_rpt-users] aprs password for app_gps
>>
>> The APRS-IS password could be generated using the callpass utility that
>> comes with xastir.
>>
>> Bogdan - YO3IIU
>>
>> > I would like to set up my allstarlink system to report position
>> > information
>> > to the aprs system.
>> >
>> > Can someone tell me how to set up this password?  Also, are the
>> default
>> > server and port listed in the example below what should be used?
>> > I have searched the aprs site and couldn't find who to request this
>> > information from.
>> >
>> > Chuck Henderson,  WB9UUS
>> >
>> >
>> >>
>> >> ; Configuration for app_gps
>> >> ;
>> >> [general]
>> >>
>> >> call = wb9uus-2   ; callsign (including SSID) for APRS
>> purposes*password
>> >> = 12345 ; Password for APRS-IS server for above callsign*
>> >> comment = AllStar Node 27468 ; Text to be displayed associated with
>> this
>> >> station*server = second.aprs.net  ; APRS-IS server to report
>> information
>> >> to**port = 10151 ; port on server to send data*
>> >> icon = r  ; A CAR (default)   Icon do be displayed for station on
>> APRS
>> >> display (see below)
>> >> comport = /dev/ttyS0  ; Serial port for GPS receiver (specify this
>> only
>> >> if using GPS receiver)
>> >> baudrate = 4800  ; Baud rate for GPS receiver (specify this only if
>> >> using GPS receiver)
>> >> ;debug = y ; set this for debug output
>> >> freq=442.700  ; Display Frequency of station
>> >> tone=107.2    ; CTCSS tone of station (0.0 for none)
>> >> lat=40.508    ; Fixed (default) latitude in decimal degrees
>> >> lon=-88.988   ; Fixed (default) longitude in decimal degrees
>> >> elev=123.4    ; Elevation of Antenna in Meters (*NOT* HAAT)
>> >> power=9       ; Power level (see below)
>> >> height=5      ; Antenna Height in HAAT (see below)
>> >> gain=8        ; Antenna Gain (see below)
>> >> dir=0         ; Antenna Direction (see below)
>> >>
>> >> On Sat, Jan 22, 2011 at 10:30 PM, Jim Duuuude
>> >> <telesistant at hotmail.com>wrote:
>> >>
>> >>>  There have (obviously) been some changes/improvements made to the
>> >>> Echolink and APRS/GPS subsystems within app_rpt.
>> >>>
>> >>> Included in these is the ability for a node to report its "fixed"
>> GPS
>> >>> coordinates
>> >>> to the APRS network, even if it does not have a GPS receiver
>> connected.
>> >>>
>> >>> Please see the following:
>> >>>
>> >>> Setting up Echolink Connectivity
>> >>> http://209.159.155.200/drupal/node/56
>> >>>
>> >>> Setting Up APRS and GPS Configuration
>> >>> http://209.159.155.200/drupal/node/179
>> >>>
>> >>> Of course, the latest copies of app_gps and chan_echolink need to be
>> >>> downloaded from the SVN.
>> >>>
>> >>> JIM WB6NIL
>> >>>
>> >>>
>> >>>
>> >>
>> > _______________________________________________
>> > App_rpt-users mailing list
>> > App_rpt-users at ohnosec.org
>> > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>> >
>>
>>
>> _______________________________________________
>> App_rpt-users mailing list
>> App_rpt-users at ohnosec.org
>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>





More information about the App_rpt-users mailing list