blogs.cisco.com not available via IPv6
richard at pedantictheory.com
Fri Dec 6 01:52:02 UTC 2013
*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?
On Dec 5, 2013, at 6:39 PM, Rogan Schlassa <roganschlassa at gmail.com> wrote:
> 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.
> On Dec 5, 2013 3:56 PM, "John Stuppi (jstuppi)" <jstuppi at cisco.com> wrote:
>> Thanks folks. Blogs.cisco.com should be back up now for both IPv4 and v6.
>> "We can't help everyone, but everyone can help someone."
>> John Stuppi, CISSP
>> Technical Leader
>> Strategic Security Research
>> jstuppi at 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
>> 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:
>> -----Original Message-----
>> From: Jared Mauch [mailto:jared at puck.nether.net]
>> Sent: Wednesday, December 04, 2013 9:23 AM
>> To: Henri Wahl
>> Cc: NANOG list
>> Subject: Re: blogs.cisco.com not available via IPv6
>> 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...
>> - Jared
>> On Dec 4, 2013, at 8:37 AM, Henri Wahl <h.wahl at ifw-dresden.de> wrote:
>>> can anybody from Cisco confirm that blogs.cisco.com
>>> (2001:4800:13c1:10::178) is not available via IPv6?
>>> Henri Wahl
>>> IT Department
>>> Leibniz-Institut fuer Festkoerper- u.
>>> Werkstoffforschung Dresden
>>> tel: (03 51) 46 59 - 797
>>> email: h.wahl at ifw-dresden.de
>>> Nagios status monitor Nagstamon:
>>> DHCPv6 server dhcpy6d:
>>> IFW Dresden e.V., Helmholtzstrasse 20, D-01069 Dresden VR Dresden Nr.
>>> Vorstand: Prof. Dr. Juergen Eckert, Dr. h.c. Dipl.-Finw. Rolf Pfrengle
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
More information about the NANOG