Spectrum technical contact

Sun Dec 23 17:13:46 UTC 2018

I’m glad you got it figured out with the right people at spectrum.  When I was sitting up ddos rtbh with my 3 isp’s , I remember spectrum (fka twc/charter) was difficult to get the right person on the phone to help me understand what I needed to do.  I had to go through layers of phone attendants and groups to get to someone who knew about ddos rtbh.

Btw, I’ve wondered about using sp-neutral(agnostic) forms of ddos rtbh... maybe cymru utrs combined with fastnetmon for immediate mitigation without human intervention.  I’d really like to get there.

Aaron

> On Dec 23, 2018, at 1:28 AM, Josh Luthman <josh at imaginenetworksllc.com> wrote:
> 
> Got a hold of someone, finally!  All you have to do, if it's done through BGP, is set a community to 10796:666
> 
> This was setup as Time Warner Cable but is Spectrum today.  The people I spoke with had been with Time Warner Cable for years before the acquisition/name change.
> 
> Josh Luthman
> Office: 937-552-2340
> Direct: 937-552-2343
> 1100 Wayne St
> Suite 1337
> Troy, OH 45373
> 
> 
>> On Sun, Dec 23, 2018 at 12:53 AM Josh Luthman <josh at imaginenetworksllc.com> wrote:
>> Attack is back on.  If there's anyone out there that works at Spectrum and can do a route change and hopefully share some info on BGP communities I would greatly appreciate hearing from you.
>> 
>> Josh Luthman
>> Office: 937-552-2340
>> Direct: 937-552-2343
>> 1100 Wayne St
>> Suite 1337
>> Troy, OH 45373
>> 
>>> On Sun, Dec 23, 2018, 12:12 AM Tim Warnock <timoid at timoid.org wrote:
>>> > That’s where you confuse me Josh, if you do BGP with them wouldn’t it be
>>> > your advertisement to them that’s causing them to route to you.  In other
>>> > words, aren’t they only routing packets to you for prefixes that you advertise
>>> > via BGP to them?
>>> 
>>> Unless of course the point-to-point between spectrum and Josh is under attack...?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20181223/0f190f97/attachment.html>