Re: [Xastir-dev] New release coming up soon, old release "regenerated" on Github, call for discussion

On Fri, Feb 09, 2018 at 01:50:57PM -0800, Curt, WE7U wrote: > On Fri, 9 Feb 2018, Tom Russo wrote: > > > Yesterday I checked and Xastir.org had an IPv6 address returned by DNS > > queries. > > Today it does not. Looks like Curt took care of this. > > Yep. Until I have time to figure out why

Re: [Xastir-dev] New release coming up soon, old release "regenerated" on Github, call for discussion

On Fri, 9 Feb 2018, Tom Russo wrote: Yesterday I checked and Xastir.org had an IPv6 address returned by DNS queries. Today it does not. Looks like Curt took care of this. Yep. Until I have time to figure out why routing to/fro on IPv6 doesn't work it seemed like the best option. -- Curt,

Re: [Xastir-dev] New release coming up soon, old release "regenerated" on Github, call for discussion

I use IPv6 natively. I also used it when I updated the Cygwin content on the wiki and noticed no issues. Fail2ban does currently support IPv6, I am running it. 73 -Original Message- From: Xastir-dev [mailto:xastir-dev-boun...@xastir.org] On Behalf Of Curt, WE7U Sent: Thursday, February

Re: [Xastir-dev] New release coming up soon, old release "regenerated" on Github, call for discussion

Yesterday I checked and Xastir.org had an IPv6 address returned by DNS queries. Today it does not. Looks like Curt took care of this. Does it still seem slow? On Thu, Feb 08, 2018 at 06:39:11PM +, we recorded a bogon-computron collision of the flavor, containing: >