Yeah, it sounds like it. ICMP echo/echo reply was working end-to-end, but
it's possible they were blocking the Type 4 messages somewhere (I didn't
resort to packet captures to get THAT in-depth).
Ken
On Fri, Mar 17, 2017 at 10:15 AM, William Herrin wrote:
> On Fri, Mar 17, 2017 at 11:39 AM, Ken
On Fri, Mar 17, 2017 at 11:39 AM, Ken Matlock wrote:
> I know most of the day yesterday my Centurylink DSL (Denver, CO) I was
> having odd... issues, but only to some sites, and intermittent. I'd
> have issues getting content from a URL (but pinging the host would be fine,
> and manual telnet
Yeah, not sure that was related, as my issues started earlier in the day
(about 8am-9am Mountain time).
Either way it all seems fine today, no hiccups, no issues. so whatever it
was got resolved.
Ken
On Fri, Mar 17, 2017 at 9:02 AM, Pennington, Scott <
scott.penning...@cinbell.com> wrote:
> Th
I know most of the day yesterday my Centurylink DSL (Denver, CO) I was
having odd... issues, but only to some sites, and intermittent. I'd
have issues getting content from a URL (but pinging the host would be fine,
and manual telnet to TCP/443 would work). Latencies were *slightly* higher
than
There may have been other events, but we were notified of a fiber cut in the
Nashville area that impacted a few ckts for us around 6:30PM easter.
-Scott
From: NANOG [nanog-boun...@nanog.org] on behalf of T Kawasaki via NANOG
[nanog@nanog.org]
Sent: Friday
5 matches
Mail list logo
