APRSGo是我基于Golang开发的跨平台APRS-IS服务器，目前还在开发中项目地址：[GitHub APRSGo](https://github.com/APRSCN/aprsgo) 附属项目：[GitHub APRSutils](https://github.com/APRSCN/aprsutils) 其中APRSGo为服务器主项目，APRSutils则是一个开源的APRS工具包，提供了APRS报文解析、Q构造算法、呼号验算、Vincenty Inverse距离公式、 Haversine距离公式、Base91编解码、APRS TCP客户端的支持。 APRSGo的类似项目有广泛使用的aprsc和最早的javAPRSSrvr，一开始想开发APRSGo是希望利用Golang的跨平台的特性，来让现代化的APRS服务器运行在更多平台上，尤其是Loong64（LoongArch64，龙架构）上，目前能够支持的平台有： AIX-PPC64 Darwin(macOS)-amd64 Darwin(macOS)-arm64 Dragonfly-amd64 FreeBSD-386 FreeBSD-amd64 FreeBSD-arm(32) FreeBSD-arm64(aarch64) Illumos-amd64 Linux-(i)386 Linux-amd64 **Linux-loong64** Linux-mips Linux-mips64 Linux-mips64le Linux-mipsle Linux-ppc64 Linux-ppc64le Linux-riscv64 NetBSD-amd64 NetBSD-arm(32) NetBSD-arm64(aarch64) OpenBSD-(i)386 OpenBSD-amd64 OpenBSD-arm(32) OpenBSD-arm64(aarch64) OpenBSD-riscv64 Solaris-amd64 Windows-(i)386 Windows-amd64 Windows-arm64(aarch64) 其余架构例如Plan9等，主要由于上游依赖库的兼容性问题，后期可能考虑向上游贡献代码来做兼容，目前来看，主要目的已经达成，经测试龙芯2K0300处理器已经正常运行，大家手持龙芯的也可以去构建服务器来测试，需要注意的是，由于采用Golang官方源，不支持龙芯旧世界，请注意一定要使用新世界方案。目前项目自身主要还存在的问题有APRS解析器有少数不规范数据包无法正常解析， filter过滤器算法不完善（写的比较急），如果有能力的火腿也可以向仓库贡献代码。最终极的目标是搭建一台APRS Tier2节点，并运行在龙架构上，让 status.aprs2.net 展示 loong64 的名字。整活意义更大一些吧，如果有这方面能力的，欢迎联系我。 Demo站点：[APRSCN-S0](http://s0.aprs.cn:14501) 仅供演示作用，2K0300性能不高，请高抬贵手不要折腾！发现Bug欢迎贡献代码或者在GitHub发起Issues向我报告。

是不是发到技术分区更好🤔

@"Bigsk"#p86695 APRS Tier2 节点好像因为某些原因不允许存在于大陆境内望楼主咨询好政策

@"BG2EFX"#p86707 目前我所知道的大陆有三台服务器 T2CS长沙，BH7DAO搭建，阿里云 T2FZ福州，BD5RV搭建，阿里云 T2YANTAI烟台，BI4MPH搭建，腾讯云这三台服务器都已经运行了很久了，似乎并没有太大问题

@"[未知用户]"#p86707 目前我所知道的大陆有三台服务器 T2CS长沙，BH7DAO搭建，阿里云 T2FZ福州，BD5RV搭建，阿里云 T2YANTAI烟台，BI4MPH搭建，腾讯云这三台服务器都已经运行了很久了，似乎并没有太大问题

@"Bigsk"#p86709 那是迁移了还好我之前看过之前的国内服务器IP是在HK的

大佬nb 我之前也有过类似的想法，甚至想把前端地图展示一并做出来，像aprs.tv那样，尤其是想添加专门的过滤器，为自己或者其他朋友过滤掉一定地理范围内的数据包，但是想到工程量巨大最终放弃此想法

@"FengziLeo"#p86713 过滤器就是设置filter就好了

aprs.cn 之前554不是挂到了一个应急的追踪系统上了么我记得

APRSGo - A new APRS-IS server solution

Bigsk

BI7ALG Very few people actually use the internet to radio functionality, and it's likely not an issue on my end. The BS software is also quite incomplete; I haven't been able to activate internet-to-radio forwarding using APRS either, which indicates that the problem is most likely with BS itself rather than my setup.

BG5BQB

Has been seriously established.
https://aprs.cqradio.cn
😆

Bigsk

APRSGo version 1.3.2 (by Ampere)
APRSGo v1.3.2 (Ampere) - Download

APRSGo version 1.3.2 (by Ampere)

Improved

Traffic levels remain constant. Each rate in APRSGo is now the average over the
last-minute – on the status page, in the listener and client tables, and in
the charts. The numbers were previously taken as a one-second sample, which was suitable for ordinary
APRS traffic consists of integer counts that fluctuate between zero and a small number.
The page never agreed with the chart. Rates are reported as fractional values, so
a link carrying 25 packets per minute reads 0.42/s, rather than being rounded down to zero.
A newly connected client displays its rate within seconds, rather than after a
one full minute.
Charts should no longer misrepresent missing data. A sample that the server was unable to retrieve.
measurement – the uplink was unavailable for the entire minute, a counter was reset, the
The sampler was lagging – it is now being sent as null and the chart crosses the line
There. Previously, all of these resulted in a score of zero, which was indistinguishable from a healthy
Link with no traffic. Reloading the configuration using SIGHUP no longer works.
It silently dropped the moment the reload occurred.
Changes to the clock will not affect the historical data. The samples are time-stamped on the
The system uses a monotonic clock and converts it to wall-clock time upon serving, so an
The NTP step no longer causes data to shift or be reordered after it has been initially recorded.
Reduced storage requirements for statistical data. The time series transitioned from a map that was
scan for expired keys every minute to a fixed-size ring buffer sized to the
72-hour retention: expiration is implied; there is no periodic cleanup, and reads are allowed.
No sorting required.
The processor is always identifiable. When the CPU model cannot be detected
(commonly found in Loongson, MIPS, and certain embedded systems) and no server.model
Once configured, the dashboard displays a generic name derived from the build.
architecture — "Loong64 Processor", "AMD64 Processor", "RISC-V 64 Processor"
and so on – instead of leaving the field blank. The detected models should be listed first.
then server.model...then, this default.

Notes for API users

The * rate fields in /api/status and /api/clients are now expressed as fractions
numbers (they were integers) and mean "average per second over the last
one minute".
/api/stats The series may include null values, indicating "not measured". Charts
They should instead deviate from their current course rather than simply plotting a zero.
server.model remains unchanged: it is consulted only when detection fails, and it
It still takes precedence over the default based on the architecture.

« 上一页

闽ICP备2021006864号-7

闽公网安备35020602002794号互联网举报中心

用户协议隐私政策社区规范积分规则中继规则转载须知
更新日志联系我们常见问题友情链接运营报告赞助

浩奇科技（厦门）有限公司

是无线电，把我们联系在一起