IPV6 is once again working for firenet so it must have been a temporary fluke..
Now the only issue is that lovely repeating character message. And I can confirm that doing a LANG="" xastir Does not produce the error message... -----Original Message----- From: David Flood [mailto:[email protected]] Sent: Wednesday, November 14, 2018 08:46 To: 'Xastir - APRS client software discussion' Subject: RE: [Xastir] constant warnings in term after update and ipv6 might be partially broken again 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:[email protected]] 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 <[email protected]> wrote: > I also tried LOCALE="C"...same errors... > > My locale is set to en_US.utf8 _______________________________________________ Xastir mailing list [email protected] http://xastir.org/mailman/listinfo/xastir
