blogs.cisco.com not available via IPv6

Mailman List Mirror (Read Only)
1

Hi,
can anybody from Cisco confirm that blogs.cisco.com
(2001:4800:13c1:10::178) is not available via IPv6?
Regards

2

I'm seeing it down via IPv6:

* Trying 2600:1407:9:295::90...
* Connected to www.cisco.com (2600:1407:9:295::90) port 80 (#0)

GET / HTTP/1.1
User-Agent: curl/7.30.0
Host: www.cisco.com
Accept: */*

< HTTP/1.1 200 OK
* Server Apache is not blacklisted

* About to connect() to blogs.cisco.com port 80 (#0)
* Trying 2001:4800:13c1:10::178...
^C

- Jared

3

My Cisco IPv6 contacts confirmed that they were made aware of this 12 hours
ago and it's being worked on.

Frank

4

And if anyone from rackspace is on this list, please feel free to help out as that is where blogs.cisco.com is hosted (it's a wordpress site, not directly under Cisco's control operationally).

Thanks,

- Mark

5

Thanks folks. Blogs.cisco.com should be back up now for both IPv4 and v6.

Thanks,
John

"We can't help everyone, but everyone can help someone."

John Stuppi, CISSP
Technical Leader
Strategic Security Research
jstuppi@cisco.com
Phone: +1 732 516 5994
Mobile: 732 319 3886

CCIE, Security - 11154
Cisco Systems
Mail Stop INJ01/2/
111 Wood Avenue South
Iselin, New Jersey 08830
United States
Cisco.com

Think before you print.
This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/index.html

6

Please dont reply back with such legal disclaimers. It is basically SPAM
and of course nonsense.

The thought that you can send a email and force your companies terms on us
is rediculous.

If CISCO forces that in your sig then for one tell them to fuck off and two
use a different email.

7

*Sarcasm* but lawyers seem to think it is REALLY important to add that load to email servers, backup servers and storage :). I wonder how much extra storage those simple extra bits/bytes have taken over the years?

~Richard

8

Its the reason deduplication makes the storage savings it does :slight_smile:

9

(A little late but) it's reachable for me -- Funny tho that something at
cisco is IPv6 via a v4<->v6 (2001::slight_smile: :slight_smile:

jamie

10

Huh?

2001:4800::/29 is owned by Rackspace. It's native all the way from "here" anyway.

Mike

11

Jamie, methinks you are confusing 2002 with 2001....

Jared Mauch

12

*Has a Rick Perry "Oops." moment*.

Thanks, Jared.

..Again. :slight_smile:

-j

13

These typically get one of the following from me:

NOTICE: This communication may contain confidential and/or privileged
information. If you are not the intended recipient or believe that you
have received this communication in error you are obligated to kill
yourself and anyone else who may have read it, not necessarily in that
order. So there. My disclaimer is scarier than yours. Nyaah. You
started this silly nonsense. Knock it off and I will too, ok? It's
worthless from a legal standpoint and is responsible for the needless
suffering of billions of innocent electrons. Nobody reads it anyway.
You're not actually reading this, are you? I didn't think so.

NOTICE:
By sending email to any of my addresses you are agreeing that:
   1. I am by definition, "the intended recipient".
   2. All information in the email is mine to do with as I see fit and
make such financial profit, political mileage, or good joke as it lends
itself to. In particular, I may quote it on newsgroups, forums, and
mailing lists.
   3. I may take the contents as representing the views of your company.
   4. This overrides any disclaimer or statement of confidentiality that
may be included on your message.