[Xastir] IPV6 connections to firenet aren't working again this AM

Tom Russo russo at bogodyn.org
Sat Apr 6 09:59:02 PDT 2019


I do not believe this should be related to the merge of the download manager
(which should only impact online map loading --- which is a very nice impact, 
too), but you can easily check the hypothesis by rolling back your git repo to 
the commit prior to that merge:

   git checkout 64dcb206

and a rebootstrap/rebuild should do it.  If the problem goes away, the merge
broke IPV6, and if not, the problem is elsewhere.  When you've tested that,
you can get back to the current state of the repo with

   git checkout master

and another rebootstrap/rebuild.

On Sat, Apr 06, 2019 at 09:11:56AM -0700, we recorded a bogon-computron collision of the <davidf4 at mindspring.com> flavor, containing:
> I'm not sure if this is the transient condition that sometimes shows up or
> if it's the latest code that I pulled with "git pull".
> 
> I can ping the IPV6 addresses by name successfully but Xastir fails to
> connect to them.  And this time it's a very quiet fail, nothing at all
> logged in the launching terminal window.  The interface just goes into
> ERROR.
> 
> So for now I've changed the VM its running on from direct to NAT and that
> forces IPV4...which is working just fine.
> 
> Dave
> KD7MYC
> 
> 
> 
> _______________________________________________
> Xastir mailing list
> Xastir at lists.xastir.org
> http://xastir.org/mailman/listinfo/xastir

-- 
Tom Russo    KM5VY
Tijeras, NM  

 echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m]



More information about the Xastir mailing list