<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sun, May 25, 2014 at 12:10 PM, William H. Magill <span dir="ltr"><<a href="mailto:magill@mac.com" target="_blank">magill@mac.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":113" class="a3s" style="overflow:hidden">Ok, as expected... however, when clicking "Install"<br>
after the EULA<br>
it pauses a moment, pops up "Getting software" and the barber-pole then...<br>
"Can't download the software because of a network problem."<br>
<br>
===<br>
Any guesses on what is happening?<br></div></blockquote></div><br>Lots of guesses, no idea if any of them apply....<br>Some things that come to mind:</div><div class="gmail_extra"><br></div><div class="gmail_extra">- sometimes you get an IPv6 address, and you have local (but not link-local) IPv6 without having an upstream IPv6 connection.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">- Apple's software distribution goes via Akamai, and sometimes a particular Akamai server will be out of date or broken; this can be exacerbated by DNS caching either locally or by an upstream DNS server, so you'll keep getting the broken server until the cache(s) expire. (Note that there is nothing you can do about upstream DNS caches, except try to avoid them by temporarily switching to a different DNS provider such as OpenDNS or Google's public DNS. But this won't help if Akamai gives out servers based on load and the load on the broken server is low because it's broken.)<br clear="all">
<div><br></div><div>- Apple recently redid a bunch of stuff on their network. It's taken a while for the MacPorts services that are hosted by Apple to get fully straightened out, and I have occasionally noticed transient problems with other Apple services including the App Store which may or may not be related. (This, again, could well be compounded by Akamai: if the changes confused Akamai's software enough, it could lead to delays or missed updates on their servers, so they can't serve what they're supposed to. "The more they overthink the plumbing....")</div>
<div><br></div><div>Other possibilities include broken routing inside your ISP or at its border with higher tier networks, broken DNS inside your ISP (again, try one of the other open DNS providers), buggy routes between higher tier providers, etc. Sometimes the reason error messages are inscrutable is because so many things could have gone wrong to produce a particular failure that about all you can say is "it done broke som'ere".</div>
<div><br></div>-- <br><div dir="ltr"><div>brandon s allbery kf8nh sine nomine associates</div><div><a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a> <a href="mailto:ballbery@sinenomine.net" target="_blank">ballbery@sinenomine.net</a></div>
<div>unix, openafs, kerberos, infrastructure, xmonad <a href="http://sinenomine.net" target="_blank">http://sinenomine.net</a></div></div>
</div></div>