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

[Tom Russo]

On Fri, Jan 26, 2018 at 10:15:39PM -0600, we recorded a bogon-computron 
collision of the  flavor, containing:
> I pushed another small change to the same repo that fixes the interaction
> between interfaces on error I saw. With that change all issues I am aware
> of should (knocks on wood) be fixed.

I'll give this the weekend to be tested out.  If David and Dan could try it 
out and let us know, I'd really appreciate it, especially since I have 
not experienced either of the odd failures they have when I try it on
an IPv4-only system.

If you followed my previous instructions about how to get Jason's first
fix into your "godfreja-ipv6fix" branch, you can just redo the "git pull" 
command in those instructions go get his second fix added to your branch.

If you didn't pull the first set of fixes already, the same three commands
will get you the whole bunch:

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

I'll refrain from merging these fixes until I hear from both David and Dan that
their reported bugs are really gone.  

If you find any further problems with the ipv6 code, please chime in soon.
I'd like to push out a stable release soon, but "soon" probably means "not 
until next weekend, or until it's actually stable, which ever comes last."

-- 
Tom RussoKM5VY   SAR502   DM64ux  http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236http://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]
___
Xastir-dev mailing list
Xastir-dev@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir-dev

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

[Jason Godfrey]

I pushed another small change to the same repo that fixes the interaction
between interfaces on error I saw. With that change all issues I am aware
of should (knocks on wood) be fixed.

73
- Jason
___
Xastir-dev mailing list
Xastir-dev@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir-dev

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

[David Flood]

Ok, I'll give it all another look-see over the Weekendthat is if I 
can get X-win working on my home machines again (one of the problems 
with Gentoo...sometimes something else breaks)...


David


On 1/26/2018 4:24 PM, Jason Godfrey wrote:

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.

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.

- Jason



___
Xastir-dev mailing list
Xastir-dev@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir-dev

Re: [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  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.

H.  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  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@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@lists.xastir.org
> http://xastir.org/mailman/listinfo/xastir-dev

-- 
Tom RussoKM5VY   SAR502   DM64ux  http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236http://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]

 


___
Xastir-dev 

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

[Jason Godfrey]

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.

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.

- Jason

On Fri, Jan 26, 2018 at 6:03 PM, David Flood  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@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@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir-dev

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

[David Flood]

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@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir-dev

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

[Jason Godfrey]

On Fri, Jan 26, 2018 at 5:25 PM, Tom Russo  wrote:
>
>
> Now your undo-ipv6client branch is an exact copy of the code from right
> before
> the ipv6client code was merged, and has none of the later commits, either.
>
> *NOW* you can switch back and forth between master and undo-ipv6client and
> it'll either be the code you're having trouble with (master) or old code
> that
> works for you (undo-ipv6client).  And *this* time I actually tried the
> commands
> I'm recommending, so I know they work.
>
> BTW, it seems clear that this bug involves something that's happening in
> "forked_getaddrinfo."  You might gather useful data for Jason by running
> the
> buggy code with debug level 1024 --- Jason put lots of debug statements in
> there that might help.
>
>
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.

- Jason
___
Xastir-dev mailing list
Xastir-dev@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir-dev

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

[David Flood]

Start Host lookup
Creating pipe
Host fork
Parent closing write end of pipe
Host fork
Child closing read end of pipe
Set alarm
Child closing write end of pipe
Parent closing read end of pipe
Socket connection for interface 0 type (10, 1, 6) failed: Network is 
unreachable

This is OK since we have more to try.
Socket connection for interface 0 type (10, 1, 6) failed: Network is 
unreachable

This is OK since we have more to try.
Socket connection for interface 0 type (10, 1, 6) failed: Network is 
unreachable

Fri Jan 26 15:51:57 PST 2018:
    Interface Error!  Error opening interface 0 Hard Fail



On 1/26/2018 3:49 PM, Tom Russo wrote:

File->Configure->Change Debug Level

Set it to 1024 and click OK, should get a bunch of stuff spewed to the terminal
when you try to connect to the interfaces that are failing.


___
Xastir-dev mailing list
Xastir-dev@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir-dev

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

[Tom Russo]

File->Configure->Change Debug Level

Set it to 1024 and click OK, should get a bunch of stuff spewed to the terminal
when you try to connect to the interfaces that are failing.

On Fri, Jan 26, 2018 at 03:47:08PM -0800, we recorded a bogon-computron 
collision of the  flavor, containing:
> Refresh my memory on how to run with debug levels??? I've always just run 
> the main program.
> 
> 
> On 1/26/2018 3:25 PM, Tom Russo wrote:
> > BTW, it seems clear that this bug involves something that's happening in
> > "forked_getaddrinfo."  You might gather useful data for Jason by running the
> > buggy code with debug level 1024 --- Jason put lots of debug statements in
> > there that might help.
> >
> 
> ___
> Xastir-dev mailing list
> Xastir-dev@lists.xastir.org
> http://xastir.org/mailman/listinfo/xastir-dev

-- 
Tom RussoKM5VY   SAR502   DM64ux  http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236http://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]

 


___
Xastir-dev mailing list
Xastir-dev@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir-dev

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

[David Flood]

Refresh my memory on how to run with debug levels?  I've always just run 
the main program.



On 1/26/2018 3:25 PM, Tom Russo wrote:

BTW, it seems clear that this bug involves something that's happening in
"forked_getaddrinfo."  You might gather useful data for Jason by running the
buggy code with debug level 1024 --- Jason put lots of debug statements in
there that might help.



___
Xastir-dev mailing list
Xastir-dev@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir-dev

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

[Tom Russo]

On Fri, Jan 26, 2018 at 03:07:58PM -0800, we recorded a bogon-computron 
collision of the  flavor, containing:
> I'll probably have to wait until the fix is in:
> 
> 
> dflood@gentoo ~/src/Xastir $ git checkout -b undo-ipv6client
> Switched to a new branch 'undo-ipv6client'
> dflood@gentoo ~/src/Xastir $ git revert d8361698
> error: commit d83616984b34c2c7b7bc0e1e76073931bdf6ef09 is a merge but no 
> -m option was given.
> fatal: revert failed
> dflood@gentoo ~/src/Xastir $
> 

Sorry about that, I should have tested it before recommending it.  
That command would have worked if that commit wasn't a
merge commit.  And adding "-m 1" to the command would have worked normally, 
but isn't right now because of what happened in that merge (some files renamed 
and removed).  So scrub that idea.

Fortunately, all of the changes made since the merge of the IPv6 stuff has
been to documentation and copyrights, so you can just check out code from 
right before the merge and you'll be back to running:

Double check that you're still on undo-ipv6client:

$ git status
On branch undo-ipv6client
nothing to commit, working tree clean

If it doesn't say that, you must have done a "git checkout master" 
Do a git checkout undo-ipv6client (without the -b) again.

Then do this:

git reset --hard 890c2038


Now your undo-ipv6client branch is an exact copy of the code from right before
the ipv6client code was merged, and has none of the later commits, either.

*NOW* you can switch back and forth between master and undo-ipv6client and
it'll either be the code you're having trouble with (master) or old code that
works for you (undo-ipv6client).  And *this* time I actually tried the commands
I'm recommending, so I know they work.

BTW, it seems clear that this bug involves something that's happening in 
"forked_getaddrinfo."  You might gather useful data for Jason by running the
buggy code with debug level 1024 --- Jason put lots of debug statements in
there that might help.

> Also, is there a tag that David can check out from to bypass this one until 
> it gets fixed?
> 
> > No tag, but it's easy to remove the code to bypass the issue temporarily.
> >
> >git checkout -b undo-ipv6client
> >git revert d8361698
> >
> 
> ___
> Xastir-dev mailing list
> Xastir-dev@lists.xastir.org
> http://xastir.org/mailman/listinfo/xastir-dev

-- 
Tom RussoKM5VY   SAR502   DM64ux  http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236http://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]

 


___
Xastir-dev mailing list
Xastir-dev@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir-dev

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

[David Flood]

I'll probably have to wait until the fix is in:


dflood@gentoo ~/src/Xastir $ git checkout -b undo-ipv6client
Switched to a new branch 'undo-ipv6client'
dflood@gentoo ~/src/Xastir $ git revert d8361698
error: commit d83616984b34c2c7b7bc0e1e76073931bdf6ef09 is a merge but no 
-m option was given.

fatal: revert failed
dflood@gentoo ~/src/Xastir $


Also, is there a tag that David can check out from to bypass this one until it 
gets fixed?


No tag, but it's easy to remove the code to bypass the issue temporarily.

   git checkout -b undo-ipv6client
   git revert d8361698



___
Xastir-dev mailing list
Xastir-dev@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir-dev

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

[Tom Russo]

On Fri, Jan 26, 2018 at 02:53:58PM -0800, we recorded a bogon-computron 
collision of the  flavor, containing:
> On Fri, 26 Jan 2018, Jason Godfrey wrote:
> 
> > It is in mainline. There is a bug I plan on fixing this weekend that might
> > be causing this.
> >
> > Is there any output in the window you run xastir from that seems relevant?
> 
> Also, is there a tag that David can check out from to bypass this one until 
> it gets fixed?

No tag, but it's easy to remove the code to bypass the issue temporarily.

  git checkout -b undo-ipv6client
  git revert d8361698

This will create a temporary branch with all the ipv6client changes undone.
That way one can always switch back to master (git checkout master) to help 
gather info for Jason to work through the bug, and git checkout undo-ipv6client 
to have working code.

-- 
Tom RussoKM5VY   SAR502   DM64ux  http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236http://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]

 


___
Xastir-dev mailing list
Xastir-dev@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir-dev

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

[David Flood]

As much as I hate bottom posting, it made sense to paste the window text right 
after your question below. The only other behavior that seems related is the 
"looking up " text that appears in the lower right corner of Xastir stays 
there for a long time before the failure.

KD7MYC

-Original Message-
>From: Jason Godfrey 
>Sent: Jan 26, 2018 2:49 PM
>
>Is there any output in the window you run xastir from that seems relevant?

Indexing maps...
Finished indexing maps
*** Reading WX Alert log files
*** Done with WX Alert log files
Socket connection for interface 0 type (10, 1, 6) failed: Network is unreachable
This is OK since we have more to try.
Socket connection for interface 0 type (10, 1, 6) failed: Network is unreachable
This is OK since we have more to try.
Socket connection for interface 0 type (10, 1, 6) failed: Network is unreachable
Fri Jan 26 14:51:04 PST 2018:
Interface Error!  Error opening interface 0 Hard Fail

Socket connection for interface 1 type (10, 1, 6) failed: Network is unreachable
Fri Jan 26 14:51:05 PST 2018:
Interface Error!  Error opening interface 1 Hard Fail

___
Xastir-dev mailing list
Xastir-dev@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir-dev

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

[Curt, WE7U]

On Fri, 26 Jan 2018, Jason Godfrey wrote:


It is in mainline. There is a bug I plan on fixing this weekend that might
be causing this.

Is there any output in the window you run xastir from that seems relevant?


Also, is there a tag that David can check out from to bypass this one until it 
gets fixed?

--
Curt, WE7U.http://we7u.wetnet.net
"Debating an anti-gunner is like debating an arachnophobe about the importance of 
spiders in the ecosystem." -Stephen Wright
Coordinate Converter (Android): http://www.sarguydigital.com
___
Xastir-dev mailing list
Xastir-dev@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir-dev

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

[David Flood]

When I get downtime at work I have a Gentoo VM that I fire up on my laptop.

Until today's "git pull" it worked just fine.

As of today's pull, bootstrap, configure, make, install the IPV4 
interfaces that I have defined are now giving a Hard Error.


I can ping those IPV4 names from another term so I know they're 
resolving correctly but something inside of Xastir doesn't like them.  I 
can't use IPV6 since my cell modem doesn't route IPV6.


If I set up a new interface with a specific IPV4 address hardcoded, that 
works.  but that's not a long term fix because I'm using rotates 
(rotate.aprs2.net and firenet.aprs2.net).


Any suggestion where to go from here for tshoot?

David Flood

KD7MYC


___
Xastir-dev mailing list
Xastir-dev@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir-dev