On Fri, Apr 17, 2020 at 04:51:01PM -0600, Tom Russo wrote:
> I just pushed out a point release of Xastir 2.1.6.
Thanks, CRUX port updated.
David G6GZH
___
Xastir-dev mailing list
Xastir-dev@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir-dev
I had at one time considered, but never got around to, putting together
a KISS TNC with LoRa air interface (instead of the HDLC/Bell 202 tones)
and I think this would be the easiest way to go.
KISS is essentially a framing protocol for the serial interface, see
http://www.ax25.net/kiss.aspx
David
On Sat, Jul 24, 2021 at 10:06:52PM +0200, Kristoff wrote:
> The APRS message is sent in as plain text inside a LoRa message. You do need
> add ['>',0x00,0xff] in front of the message. (no idea why this is)
OK, my idea had in mind to still use AX.25 (in order to allow not just
APRS but e.g. the Lin
On Wed, Feb 07, 2018 at 11:52:48AM -0700, Tom Russo wrote:
>
> If you're a package maintainer for any OS, you might start looking into how
> you have to change your package build process to access the Github release
> tarballs instead of SourceForge.
I've made the necessary changes for CRUX.
htt
With the mention of the wiki I was just having a look at it and it
seemed slow - looks like IPv6 routing is broken from me at least
traceroute to xastir.org (2001:1868:205::1001) from
2001:8b0:3d7:1:c9ac:a899:bdcb:1d59, 30 hops max, 24 byte packets
1 rb-lan.dbrooke.me.uk (2001:8b0:3d7:1::1) 0.
On Thu, Feb 08, 2018 at 10:12:34AM -0800, Curt, WE7U wrote:
>
> Is IPv6 truly needed?
I guess that's a matter for debate; having used IPv6 for over 10 years I
kind of regard it as standard but I'm not aware of many sites that don't
also have IPv4.
However the presence of an record in DNS me
On Fri, Feb 09, 2018 at 01:50:57PM -0800, Curt, WE7U wrote:
> On Fri, 9 Feb 2018, Tom Russo wrote:
>
> > Yesterday I checked and Xastir.org had an IPv6 address returned by DNS
> > queries.
> > Today it does not. Looks like Curt took care of this.
>
> Yep. Until I have time to figure out why rou
On Sat, Feb 10, 2018 at 06:33:15PM -0700, Tom Russo wrote:
>
> For the few of you package maintainers who have already adjusted your package
> build scripts to deal with the quirks of the technique I sent a couple of days
> ago, "Thank you." But also, "Sorry, you have to do it again."
No problem,
On Fri, Feb 16, 2018 at 12:27:11PM -0700, Tom Russo wrote:
>
> So this is a good way of encapsulating all the discussion and code change
> in a single spot for posterity's sake. Connecting code changes to discussions
> in a simple way is worth the added hassle of having two places to think
> abou
On Mon, Feb 19, 2018 at 02:35:51PM -0700, Tom Russo wrote:
> On Mon, Feb 19, 2018 at 08:16:31PM +, we recorded a bogon-computron
> collision of the flavor, containing:
> > I could see a slight use case for the date when running with uncommitted
> > code,
>
> Agreed, this has occurred to me,
10 matches
Mail list logo
