[Xastir] constant warnings in term after update and ipv6 might be partially broken again

[David Flood]

IPV6 worked for rotate.aprs2.net but not firenet.aprs2.net...so it might
have been something about IPV6 and the firenet pool of addresses...or it
might be related to the interface order patches announced yesterday...I'll
try the old version again and then git pull to update and try again.

I have a real world interruption this AM but should have some ATUs this
afternoon to try things again.  And if I only try to fire up the firenet
interface then any error message shouldn't scroll off since I won't be
getting the character error with each new station received since a failed
connection doesn't receive any data.

Dave
KD7MYC

-----Original Message-----
From: Xastir [mailto:xastir-bounces at lists.xastir.org] On Behalf Of Jason
Godfrey
Sent: Wednesday, November 14, 2018 08:11

Are you still having IPv6 issues? Was it not connecting at all if you have
IPv6 enabled?

- Jason

On Sun, Nov 11, 2018 at 9:24 AM David Flood <davidf4 at mindspring.com> wrote:

> I also tried LOCALE="C"...same errors...
>
> My locale is set to en_US.utf8