Am 02/11/13 23:19, schrieb Mark Felder:
On Nov 2, 2013, at 3:27 PM, Adrian Chadd adr...@freebsd.org wrote:
A lot of HTTP infrastructure lives on anycast DNS, HTTP redirects and
geoip records. Saying it's broken and not feasible is nonsense.
More specifically what I was referring to was the
On Sat, 02 Nov 2013 12:28:06 +
Matthew Seaman wrote:
Which is not always true, especially in heavily firewalled
environments.
I feel no obligation to do anything to encourage people that
deliberately break the DNS. They've made their bed, and now they have
to lie in it.
In other
On 02/11/2013 01:55, Eric van Gyzen wrote:
This kind of proxy configuration is not uncommon. It would be awesome
if this would Just Work. It would remove an impediment to adoption,
which is especially important in the kind of environments that have this
kind of proxy configuration.
Simply
Matthew Seaman matt...@freebsd.org schrieb:
On 02/11/2013 01:55, Eric van Gyzen wrote:
This kind of proxy configuration is not uncommon. It would be
awesome
if this would Just Work. It would remove an impediment to adoption,
which is especially important in the kind of environments that
On 02/11/2013 10:15, Matthias Andree wrote:
I understand from Eric's pist that the issue is that through his
limiting proxies, the SRV are not available at all so he does not even
get to the point where he could get the pkgN.nyi.freebsd.org
http://pkgN.nyi.freebsd.org name back.
That doesn't
On 02/11/2013 11:37, Kurt Jaeger wrote:
Hi!
On 02/11/2013 10:15, Matthias Andree wrote:
I understand from Eric's pist that the issue is that through his
limiting proxies, the SRV are not available at all so he does not even
get to the point where he could get the pkgN.nyi.freebsd.org
On 11/02/2013 07:28 AM, Matthew Seaman wrote:
On 02/11/2013 11:37, Kurt Jaeger wrote:
Hi!
On 02/11/2013 10:15, Matthias Andree wrote:
I understand from Eric's pist that the issue is that through his
limiting proxies, the SRV are not available at all so he does not even
get to the point where
Hi!
On 02/11/2013 10:15, Matthias Andree wrote:
I understand from Eric's pist that the issue is that through his
limiting proxies, the SRV are not available at all so he does not even
get to the point where he could get the pkgN.nyi.freebsd.org
http://pkgN.nyi.freebsd.org name back.
Am 02.11.2013 11:51 schrieb Matthew Seaman matt...@freebsd.org:
On 02/11/2013 10:15, Matthias Andree wrote:
I understand from Eric's pist that the issue is that through his
limiting proxies, the SRV are not available at all so he does not even
get to the point where he could get the
On Sat, 02 Nov 2013 09:01:56 -0500, Eric van Gyzen wrote:
On 11/02/2013 07:28 AM, Matthew Seaman wrote:
I feel no obligation to do anything to encourage people that
deliberately break the DNS. They've made their bed, and now they have
to lie in it.
Eric Camachat didn't break the DNS:
On 2 November 2013 05:28, Matthew Seaman matt...@freebsd.org wrote:
I feel no obligation to do anything to encourage people that
deliberately break the DNS. They've made their bed, and now they have
to lie in it.
Holy, holy crap.
* We (as FreeBSD) are not big enough to dictate the
On Nov 2, 2013, at 11:54 AM, Adrian Chadd adr...@freebsd.org wrote:
You're using a DNS feature which
isn't well adopted/supported and you haven't provided a fallback
legacy, well tested path.
But SRV has been widely deployed since… before 2000? It’s literally the
backbone of Active
Am 02.11.2013 11:50, schrieb Matthew Seaman:
On 02/11/2013 10:15, Matthias Andree wrote:
I understand from Eric's pist that the issue is that through his
limiting proxies, the SRV are not available at all so he does not even
get to the point where he could get the pkgN.nyi.freebsd.org
On 2 November 2013 10:44, Mark Felder f...@freebsd.org wrote:
But SRV has been widely deployed since… before 2000? It’s literally the
backbone of Active Directory deployments. Here’s a list of things that his
company’s network design probably breaks:
* Office 365 (cloud Exchange hosting by
On Nov 2, 2013, at 3:27 PM, Adrian Chadd adr...@freebsd.org wrote:
A lot of HTTP infrastructure lives on anycast DNS, HTTP redirects and
geoip records. Saying it's broken and not feasible is nonsense.
More specifically what I was referring to was the fact that traditionally HTTP
failover
On 10/31/2013 05:21 PM, Freddie Cash wrote:
tried pkg.freebsd.org it got below.
Our DNS server can resolve proxy server only.
Only proxy server can resolve internet sites, this is how our company force
all traffic went through proxy server.
Eric
Network Error (dns_server_failure)
Your
It doesn't work with our (microsoft) proxy server, see below.
root@basay:/usr/local/etc/pkg/repos # pkg update -f
Updating repository catalogue
pkg: http://pkg.FreeBSD.org/freebsd:10:x86:64/latest/digests.txz: Service
Unavailable
pkg: No digest falling back on legacy catalog format
pkg:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-10-31 16:47, Eric Camachat wrote:
It doesn't work with our (microsoft) proxy server, see below.
root@basay:/usr/local/etc/pkg/repos # pkg update -f
Updating repository catalogue
pkg:
... I still think the SRV record stuff is a bad idea.
Well, I think it's a great idea - because I plan on supporting it in
the next HTTP thing I write - but not having an A record is going to
continue to bite things.
Also, http+pkg:// isn't a defined protocol either and some strict
proxies may
On 10/31/2013 4:06 PM, Adrian Chadd wrote:
... I still think the SRV record stuff is a bad idea.
Well, I think it's a great idea - because I plan on supporting it in
the next HTTP thing I write - but not having an A record is going to
continue to bite things.
I don't like it either, it's
Same result, neither pkg+http:// nor http+pkg:// worked with proxy server.
Eric
On Thu, Oct 31, 2013 at 2:09 PM, Bryan Drewery bdrew...@freebsd.org wrote:
On 10/31/2013 4:06 PM, Adrian Chadd wrote:
... I still think the SRV record stuff is a bad idea.
Well, I think it's a great idea -
On 10/31/2013 4:25 PM, Eric Camachat wrote:
Same result, neither pkg+http:// nor http+pkg:// worked with proxy server.
Top-posting kills babies
pkg+http is NOT supported in 1.1 and as I said, changes nothing.
Eric
On Thu, Oct 31, 2013 at 2:09 PM, Bryan Drewery bdrew...@freebsd.org
On 31/10/2013 21:04, Allan Jude wrote:
I wonder if the http+pkg:// protocol can solve this, likely will require
a patch to fetch to implement the logic to do the dns lookup and make
the proxies request for the real hostname
It's pkg+http:// or pkg+https:// or pkg+ssh:// or -- well, you get the
On 10/31/2013 3:47 PM, Eric Camachat wrote:
It doesn't work with our (microsoft) proxy server, see below.
root@basay:/usr/local/etc/pkg/repos # pkg update -f
Updating repository catalogue
pkg: http://pkg.FreeBSD.org/freebsd:10:x86:64/latest/digests.txz: Service
Unavailable
pkg: No digest
On 31/10/2013 21:38, Bryan Drewery wrote:
On 10/31/2013 4:25 PM, Eric Camachat wrote:
Same result, neither pkg+http:// nor http+pkg:// worked with proxy server.
Top-posting kills babies
pkg+http is NOT supported in 1.1 and as I said, changes nothing.
Also the request that pkg(8) makes
browsing www.freebsd.org worked fine.
tried pkg.freebsd.org it got below.
Our DNS server can resolve proxy server only.
Only proxy server can resolve internet sites, this is how our company force
all traffic went through proxy server.
Eric
Network Error (dns_server_failure)
Your request could
On Thu, Oct 31, 2013 at 3:15 PM, Eric Camachat eric.camac...@gmail.comwrote:
browsing www.freebsd.org worked fine.
tried pkg.freebsd.org it got below.
Our DNS server can resolve proxy server only.
Only proxy server can resolve internet sites, this is how our company force
all traffic went
We are pleased to announce that official binary packages are now
available for pkg, the next generation package management tool for FreeBSD.
Pkg allows you to either use ports with portmaster/portupgrade or to
have binary remote packages without ports.
We have binary packages available for i386
28 matches
Mail list logo
