Date: Wed, 14 Apr 2021 15:40:14 +0800 From: Simon Wright <simon.wright@gmx.net> To: freebsd-ports@freebsd.org Subject: Re: Access to detailed status info on package build servers Message-ID: <47ad14eb-b193-ff8b-e006-b1b0b820643c@gmx.net> In-Reply-To: <1793324630.19.1618382819491@localhost> References: <1793324630.19.1618382819491@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
On 14/04/2021 2:46 pm, Ronald Klop wrote: > Van: Kevin Oberman <rkoberman@gmail.com> > Datum: 14 april 2021 08:31 > Aan: Simon Wright <simon.wright@gmx.net> > CC: FreeBSD Ports ML <freebsd-ports@freebsd.org> > Onderwerp: Re: Access to detailed status info on package build servers > >> >> >> On Tue, Apr 13, 2021 at 11:02 PM Simon Wright <simon.wright@gmx.net> >> wrote: >> >> > Hi all, >> > >> > >> > I use a script to pull down this file: >> > >> > http://beefy6.nyi.freebsd.org/data/122amd64-default/.data.json >> > >> > and extract the builds.latest field from it for the jail. Since the >> move >> > to git I can no longer access this file. Curl fails with an error 7 >> > which is a permission denied error. >> > >> > Simon Wright. >> > >> This is likely not your problem, but Is it possible that you have an IP= v6 >> issue? As of a few days ago, beefy6 is IPv6 only. For me, it means no >> access unless I bring up a tunnel as Frontier does not support IPv6. Ne= xt >> week I'll be moving to Comcast and that will fix the problem. Since it >> appears that Frontier has no plans to ever support IPv6 on fiber, or at >> least not for several years, I guess an HE tunnel is the only fix if I >> want >> 500 Mbps FIOS. > > If it is because of ipv6 you can also wrap the url in a service like > http://www.ipv6proxy.net/ > I use that sometimes to access the pkg servers. > > > Regards, > Ronald Thanks Kevin and Roland, this is an ipv6 issue, wrapping the URL in the proxy that Ronald suggested works fine. I know that Globe in Philippines has only just been dragged screaming into the 20th century so I imagine that the 21st century is still some way off :). Thanks again for the guidance. I will escalate this with Globe and see whether there is a real solution in the offing, otherwise I'd better get used to more work-arounds in the future.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47ad14eb-b193-ff8b-e006-b1b0b820643c>