Re: freebsd-update can't find update.FreeBSD.org
On Wed, Oct 29, 2008 at 3:37 PM, Steven Susbauer [EMAIL PROTECTED] wrote: freebsd-update fetch fails if the default ServerName update.FreeBSD.org is not changed to ServerName update1.FreeBSD.org in /etc/freebsd-update.conf. This happens on at least 6.3, I believe it is also the case in later versions but am unsure (7-RELEASE and later kill my networking card due to a kernel regression). I am wanting input before writing up a PR, to see if in fact I am just some isolated case, or if it has been fixed already in newer versions. uname -a: FreeBSD thinkpad.lan 6.3-RELEASE-p5 FreeBSD 6.3-RELEASE-p5 #0: Wed Oct 1 05:34:19 UTC 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 Nonfunctional: thinkpad# freebsd-update --debug fetch Looking up update.FreeBSD.org mirrors... none found. Fetching metadata signature for 6.3-RELEASE from update.FreeBSD.org... fetch: http://update.FreeBSD.org/6.3-RELEASE/i386/latest.ssl: No address record failed. No mirrors remaining, giving up. With update1: thinkpad# freebsd-update --debug fetch Looking up update1.FreeBSD.org mirrors... none found. Fetching metadata signature for 6.3-RELEASE from update1.FreeBSD.org... latest.ssl100% of 512 B 123 kBps done. Fetching metadata index... 344cfb64472cacb781688b5de744795f140233e84105c4100% of 225 B 52 kBps done. Inspecting system... done. Preparing to download files... done. ___ freebsd-update freebsd-questions@freebsd.org update.freebsd.org should work Considering that update1.freebsd.org is a mirror for update.freebsd.org. it works fine here for update.freebsd.org ever since I updated to 7.x from 6.2(tested freebsd-update on 6.2) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd-update can't find update.FreeBSD.org
matt donovan wrote: On Wed, Oct 29, 2008 at 3:37 PM, Steven Susbauer [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: freebsd-update fetch fails if the default ServerName update.FreeBSD.org http://update.FreeBSD.org is not changed to ServerName update1.FreeBSD.org http://update1.FreeBSD.org in /etc/freebsd-update.conf. This happens on at least 6.3, I believe it is also the case in later versions but am unsure (7-RELEASE and later kill my networking card due to a kernel regression). I am wanting input before writing up a PR, to see if in fact I am just some isolated case, or if it has been fixed already in newer versions. uname -a: FreeBSD thinkpad.lan 6.3-RELEASE-p5 FreeBSD 6.3-RELEASE-p5 #0: Wed Oct 1 05:34:19 UTC 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 Nonfunctional: thinkpad# freebsd-update --debug fetch Looking up update.FreeBSD.org http://update.FreeBSD.org mirrors... none found. Fetching metadata signature for 6.3-RELEASE from update.FreeBSD.org... fetch: http://update.FreeBSD.org/6.3-RELEASE/i386/latest.ssl: No address record failed. No mirrors remaining, giving up. With update1: thinkpad# freebsd-update --debug fetch Looking up update1.FreeBSD.org http://update1.FreeBSD.org mirrors... none found. Fetching metadata signature for 6.3-RELEASE from update1.FreeBSD.org... latest.ssl 100% of 512 B 123 kBps done. Fetching metadata index... 344cfb64472cacb781688b5de744795f140233e84105c4100% of 225 B 52 kBps done. Inspecting system... done. Preparing to download files... done. update.freebsd.org should work Considering that update1.freebsd.org is a mirror for update.freebsd.org. it works fine here for update.freebsd.org ever since I updated to 7.x from 6.2(tested freebsd-update on 6.2) update.freebsd.org does not have a DNS entry associated with it, could that be part of the problem I'm having? (just-ping.com gets Unknown Host from 34 systems around the world) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd-update can't find update.FreeBSD.org
On Wed 2008-10-29 13:37:11 UTC-0600, Steven Susbauer ([EMAIL PROTECTED]) wrote: freebsd-update fetch fails if the default ServerName update.FreeBSD.org is not changed to ServerName update1.FreeBSD.org in /etc/freebsd-update.conf. thinkpad# freebsd-update --debug fetch Looking up update.FreeBSD.org mirrors... none found. May be related to this: http://lists.freebsd.org/pipermail/freebsd-questions/2008-October/183886.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd-update can't find update.FreeBSD.org
andrew clarke wrote: On Wed 2008-10-29 13:37:11 UTC-0600, Steven Susbauer ([EMAIL PROTECTED]) wrote: freebsd-update fetch fails if the default ServerName update.FreeBSD.org is not changed to ServerName update1.FreeBSD.org in /etc/freebsd-update.conf. thinkpad# freebsd-update --debug fetch Looking up update.FreeBSD.org mirrors... none found. May be related to this: http://lists.freebsd.org/pipermail/freebsd-questions/2008-October/183886.html Yes it certainly was, my router dnsmasq.conf included filterwin2k, which apparently blocks SRV requests. Will remember to keep that off in the future. Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd-update can't find update.FreeBSD.org
On Wed, 29 Oct 2008 14:25:06 -0600 Steven Susbauer [EMAIL PROTECTED] wrote: andrew clarke wrote: On Wed 2008-10-29 13:37:11 UTC-0600, Steven Susbauer ([EMAIL PROTECTED]) wrote: freebsd-update fetch fails if the default ServerName update.FreeBSD.org is not changed to ServerName update1.FreeBSD.org in /etc/freebsd-update.conf. thinkpad# freebsd-update --debug fetch Looking up update.FreeBSD.org mirrors... none found. May be related to this: http://lists.freebsd.org/pipermail/freebsd-questions/2008-October/183886.html Yes it certainly was, my router dnsmasq.conf included filterwin2k, which apparently blocks SRV requests. Will remember to keep that off in the future. I think it would still be a good idea to file a PR. With portsnap the default server is itself one of the servers on the SRV list, so portsnap should fall-back to a working server even when DNS is unavailable (behind a proxy) or screwed-up by a router etc. I dont see a reason why update.FreeBSD.org shouldn't have the same A-record as update1.FreeBSD.org, so that it just works. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd-update can't find update.FreeBSD.org
RW wrote: With portsnap the default server is itself one of the servers on the SRV list, so portsnap should fall-back to a working server even when DNS is unavailable (behind a proxy) or screwed-up by a router etc. I dont see a reason why update.FreeBSD.org shouldn't have the same A-record as update1.FreeBSD.org, so that it just works. With portsnap, I asked for the A record to be created not as a fallback for people with broken DNS, but instead as a backwards compatibility mechanism for people who were running old versions of portsnap which didn't do SRV lookups. To be honest, I didn't realize that there were so many people with broken DNS resolution. I'll ask the FreeBSD DNS admins to add an A record for update.freebsd.org. Colin Percival ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd-update can't find update.FreeBSD.org
Colin Percival wrote: RW wrote: With portsnap the default server is itself one of the servers on the SRV list, so portsnap should fall-back to a working server even when DNS is unavailable (behind a proxy) or screwed-up by a router etc. I dont see a reason why update.FreeBSD.org shouldn't have the same A-record as update1.FreeBSD.org, so that it just works. With portsnap, I asked for the A record to be created not as a fallback for people with broken DNS, but instead as a backwards compatibility mechanism for people who were running old versions of portsnap which didn't do SRV lookups. To be honest, I didn't realize that there were so many people with broken DNS resolution. I'll ask the FreeBSD DNS admins to add an A record for update.freebsd.org. Colin Percival I had up until now been transparently benefiting from that non-fallback legacy A record for portsnap as well. Thanks for looking into this. I am personally amazed that an issue caused by a misconfiguration on my end could result in changes on the FreeBSD DNS servers to avoid similar issues for others. Kudos to FreeBSD support! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
