From: Richard Brown <richard.e.brown@dartware.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Richard Brown <richard.e.brown@dartware.com>,
"<cerowrt-devel@lists.bufferbloat.net>"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] What version of CeroWrt is running at http://jupiter.lab.bufferbloat.net.
Date: Sat, 17 Mar 2012 03:00:02 +0000 [thread overview]
Message-ID: <80321A9B-105D-4BE3-A002-CBF62E7DDE9A@intermapper.com> (raw)
In-Reply-To: <CAA93jw4r1JPCqS2oOqSbVBFHuw5dU+uGcsz-OvkCVr220H1j3A@mail.gmail.com>
Dave,
> Heh. It's the main router for the lab... it runs dns... it has a vpn
> on it... it's running rc6... it's STABLE.
>
> I've updated 4 (out of 9) of the machines in the lab thus far, and
> basically plan
> to cycle through them all with successive releases before updating jupiter.
OK. It's just my consistency-checkin' nature.
> If you have working ipv6, the external gui is available....
>
> http://[2001:4f8:fff8:600::1]/cerowrt/ as one example
Not yet. I'm going to check out Hurricane Electric's http://tunnelbroker.net this weekend.
> http://europa.lab.bufferbloat.net as another (both ipv6 and ipv4)
>
> I'd appreciate knowing that port 81 (the router's configuration web
> server) and ssh were indeed blocked
> from the outside world.....
Clicking the link on Europa goes to this URL: http://europa.lab.bufferbloat.net/bgi-bin/redir.sh, which tries to go to http://europa.lab.bufferbloat.net:81, which ultimately fails. Same thing with Jupiter.
You can also test this using my favorite web-site testing tool, Rex Swain's HTTP Viewer at: http://www.rexswain.com/httpview.html It shows the complete HTTP transaction along with redirects to see what's actually happening.
re: SSH...
ssh root@jupiter.lab.bufferbloat.net gives 'ssh_exchange_identification: Connection closed by remote host'
ssh root@europa.lab.bufferbloat.net gives 'ssh: connect to host europa.lab.bufferbloat.net port 22: No route to host' (!)
but dig shows europa.lab.bufferbloat.net. 82758 IN A 149.20.63.19, so I'm not sure what that implies.
Rich
next prev parent reply other threads:[~2012-03-17 3:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2.1331924401.3675.cerowrt-devel@lists.bufferbloat.net>
2012-03-17 1:40 ` [Cerowrt-devel] 3.3rc7-5 is out Richard Brown
2012-03-17 1:45 ` Dave Taht
2012-03-17 2:04 ` [Cerowrt-devel] What version of CeroWrt is running at http://jupiter.lab.bufferbloat.net Richard Brown
2012-03-17 2:20 ` Dave Taht
2012-03-17 2:30 ` Sebastian Moeller
2012-03-17 3:00 ` Richard Brown [this message]
2012-03-17 2:32 ` [Cerowrt-devel] 3.3rc7-5 is out Sebastian Moeller
2012-03-17 2:48 ` Dave Taht
2012-03-17 3:03 ` [Cerowrt-devel] Link to SFQRED description? Richard Brown
2012-03-17 3:11 ` Dave Taht
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=80321A9B-105D-4BE3-A002-CBF62E7DDE9A@intermapper.com \
--to=richard.e.brown@dartware.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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