From: Michael S. Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot 2012.02-rc3 released
Date: Sun, 4 Mar 2012 10:50:55 -0600 [thread overview]
Message-ID: <201203041050.57184.minimod@morethan.org> (raw)
In-Reply-To: <CAJJ6jxtaJwjGSrn5GUH29bu+=gu3UyM2p+a3W2Onk6Gg=N9_OA@mail.gmail.com>
On Sun March 4 2012, Steve Calfee wrote:
> Hi all,
>
> Something is seriously messed up with DNS. After the osuosl guys
> "fixed" it, I can no longer access wget
> 'http://git.buildroot.net/buildroot/plain/CHANGES?id=2012.02_rc3' at
> work, which was working, briefly before that.
>
> So now I cannot access git.buildroot.net from 3 separate isps. All
> three local networks are NATed, two have a wireless router as the
> gateway. I don't think this is a rare configuration. I have not had
> this problem accessing any http server or of several git servers.
>
> It would really be nice to git fetch the latest release!
>
Still works here, but....
Do these systems have IPv6 connectivity?
The IPv4 DNS is a CNAME chain of domains that ends with an IPv4 address.
The IPv6 DNS is a CNAME chain of domains that ends in /net/dev/null. ;-)
Any chance that your installation of git is trying to use IPv6?
- - - -
Second question -
You write that all three local networks are NATed.
Did the same person write the NAT rules? ;-)
That might be a common failure point.
Mike
> Regards, Steve
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
>
>
next prev parent reply other threads:[~2012-03-04 16:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <RT-Ticket-20368@osuosl.org>
2012-02-27 16:10 ` [Buildroot] Buildroot 2012.02-rc3 released Peter Korsgaard
2012-02-28 19:27 ` Steve Calfee
2012-02-29 7:22 ` Peter Korsgaard
2012-02-29 7:43 ` Thomas De Schampheleire
2012-02-29 15:54 ` Steve Calfee
2012-02-29 16:01 ` Peter Korsgaard
2012-02-29 16:04 ` Michael S. Zick
2012-02-29 16:22 ` Steve Calfee
2012-02-29 22:24 ` Chris Kerios
2012-02-29 23:37 ` Yann E. MORIN
2012-02-29 23:48 ` Steve Calfee
2012-02-29 23:57 ` Chris Kerios
2012-03-01 0:17 ` Arnout Vandecappelle
2012-03-01 0:40 ` Chris Kerios
2012-03-01 0:52 ` Steve Calfee
2012-03-01 1:00 ` Arnout Vandecappelle
2012-03-01 1:47 ` Steve Calfee
2012-03-01 3:44 ` Steve Calfee
2012-03-04 16:01 ` Steve Calfee
2012-03-04 16:50 ` Michael S. Zick [this message]
2012-03-04 17:06 ` Steve Calfee
[not found] ` <87mx7wwb4u.fsf@macbook.be.48ers.dk>
[not found] ` <rt-3.6.3-2614-1330988102-1965.20368-6-0@osuosl.org>
2012-03-06 17:16 ` [Buildroot] [support.osuosl.org #20368] " Steve Calfee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201203041050.57184.minimod@morethan.org \
--to=minimod@morethan.org \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox