[Xastir-dev] Has the IPV6 stuff been merged into the mainline?

[Tom Russo]

On Fri, Jan 26, 2018 at 06:24:50PM -0600, we recorded a bogon-computron collision of the <godfreja at gmail.com> flavor, containing:
> Sorry about the bug.
> 
> It looks like you are hitting the known bug. I've pushed a quick fix to
> https://github.com/godfreja/Xastir/tree/ipv6fix you can try if you would
> like. This will also fix the "IPv4 preferred over IPv6" issue that was also
> reported.

To do this most easily:

   git checkout master
   git checkout -b godfreja-ipv6fix
   git pull https://github.com/godfreja/Xastir.git ipv6fix

You'll have Jason's quick fix on your godfreja-ipv6fix branch to test out.
(Oh, and yes, I did actually check that my recommended commands actually work
before posting this time.)

> Tom - while testing this fix I saw some odd interaction in error state
> between multiple interfaces. I'm not sure if it is related to my IPv6
> changes or not. I would like to see if I can reproduce what I saw and dig
> into it over the weekend.

Hmmmm.  OK, I won't merge your quick fix just yet.

I wonder why this issue didn't bite me.  It seems that not exiting from that 
loop on success would have a more consistent problem.  I've also pulled down
this fix and am testing it out on an IPv4-only system.

> On Fri, Jan 26, 2018 at 6:03 PM, David Flood <davidf4 at mindspring.com> wrote:
> 
> >
> > alert_display_request
> > alert_display_request
> > alert_display_request
> >
> > shutdown_all_active_or_defined_port: 0
> >
> > Shutting down port 0
> > Delete Device start
> > Close a Network stream
> > Net detach
> > Net detach Start, port 0
> > net_detach():Net Close Returned 0, port 0
> > Net detach stop, port 0
> > port detach OK
> > Cancel threads
> > Port Available 0
> > Opening a Network stream
> > net_connect_thread():Net Shutdown 1 Returned -1, port 0
> > net_connect_thread():Net Close 1 Returned 0, port 0
> > Creating new thread
> > 10
> > net_connect_thread start
> > We have a socket to use
> > after setsockopt
> > calling connect(), port: 14580
> > 10
> > connect result was: 0
> > We have a socket to use
> > after setsockopt
> > calling connect(), port: 14580
> > connect result was: 0
> > We have a socket to use
> > after setsockopt
> > calling connect(), port: 14580
> > 10
> > connect result was: 0
> > We have a socket to use
> > after setsockopt
> > calling connect(), port: 14580
> > 10
> > connect result was: 0
> > We have a socket to use
> > after setsockopt
> > calling connect(), port: 14580
> > 9
> > connect result was: 0
> > We have a socket to use
> > after setsockopt
> > calling connect(), port: 14580
> > 9
> > connect result was: 0
> > We have a socket to use
> > after setsockopt
> > calling connect(), port: 14580
> > 9
> > connect result was: 0
> > We have a socket to use
> > after setsockopt
> > calling connect(), port: 14580
> > 9
> > connect result was: 0
> > We have a socket to use
> > after setsockopt
> > calling connect(), port: 14580
> > connect result was: -1
> > Socket connection for interface 0 type (10, 1, 6) failed: Network is
> > unreachable
> > This is OK since we have more to try.
> > We have a socket to use
> > after setsockopt
> > calling connect(), port: 14580
> > connect result was: -1
> > Socket connection for interface 0 type (10, 1, 6) failed: Network is
> > unreachable
> > This is OK since we have more to try.
> > We have a socket to use
> > after setsockopt
> > calling connect(), port: 14580
> > connect result was: -1
> > Socket connection for interface 0 type (10, 1, 6) failed: Network is
> > unreachable
> > net_connect_thread():net connection failed, port 0, DEVICE_ERROR ***
> > net_connect_thread terminating itself
> > 8
> > Thread exceeded it's time limit or failed to connect! Port 0
> > Killing thread
> > Thread did not return, port 0, DEVICE_ERROR ***
> > Net ok: 0, port 0
> > *** net_init is returning a -1 ***
> > Fri Jan 26 16:01:35 PST 2018:
> >         Interface Error!  Error opening interface 0 Hard Fail
> >
> >
> > On 1/26/2018 3:53 PM, Jason Godfrey wrote:
> >
> >> Actually my guess / hope is the bug is in interface.c. If you ran with a
> >> debug of 2 and saw a "connect result was: 0" followed by further connect
> >> attempts that fail the problem would be the known existing bug.
> >>
> >>
> >>
> > _______________________________________________
> > Xastir-dev mailing list
> > Xastir-dev at lists.xastir.org
> > http://xastir.org/mailman/listinfo/xastir-dev
> >
> 
> 
> 
> -- 
> "The problem with quotes on the Internet is that it is often difficult to
> verify their authenticity." - *Abraham Lincoln*
> _______________________________________________
> Xastir-dev mailing list
> Xastir-dev at lists.xastir.org
> http://xastir.org/mailman/listinfo/xastir-dev

-- 
Tom Russo    KM5VY   SAR502   DM64ux          http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236        http://kevan.org/brain.cgi?DDTNM
 echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m]