- Test - lists.nanog.org

Traffic visibility tools
by Kenny Taylor 24 Jul '19

24 Jul '19

Good morning, I hate to pull away from the 44/8 fire (KJ6BSQ here, and former AMPRnet user), but I'd like to get some advice from the community on traffic visibility tools.. We use a pair of appliances called Exinda for traffic shaping and visibility. The current appliances are end-of-support and the replacements are hugely expensive after GFI acquired Exinda. Traffic shaping is less of a concern now, as circuit speeds have caught up with our users, but visibility is still a big need. Those boxes do two things very well: 1) identification of FQDNs using SSL cert inspection on HTTPS traffic and 2) categorization of the traffic (i.e. Netflix, Youtube, etc.). We have Netflow monitoring using PRTG, but seeing something like 'ec2-34-214-76-39.us-west-2.compute.amazonaws.com' in Netflow logs isn't very useful. We're looking for something that could sit either inline or hang off a SPAN port, handle 5-10 Gbit of traffic, do the SSL cert FQDN identification, and preferably group results by site/subnet/category. What would you guys recommend? Thanks, Kenny Taylor WAN Engineer Kern Community College District

2 1

Re: 44/8
by Randy Bush 24 Jul '19

24 Jul '19

my deep sympathies go out to those folk with real work to do whose mail user agents do not have a `delete thread` key sequence.

3 2

CenturyLink/Level3 feedback
by Mehmet Akcin 24 Jul '19

24 Jul '19

hi there, Just a general high-level question about Centurylink/Level3 post-merger, how is your overall experience with CenturyLink? if you could be sitting with the CEO of the company what is one thing you would ask him to fix? please keep it high level and general. i intend to pass these to him and his team in an upcoming meeting. Mehmet

20 27

FCC: 2019 CSRIC Working Groups Announced - Volunteers?
by Sean Donelan 23 Jul '19

23 Jul '19

The 2019 FCC Communications Security Reliability and Interoperability Council (CSRIC) has announced their new working groups for the new cycle. CSRIC is seeking volunteers to serve on various working groups. https://docs.fcc.gov/public/attachments/DA-19-689A1.pdf Working Group 1: Alert Originator Standard Operating Procedures Chair: Craig Fugate, America’s Public Television Stations Working Group 2: Managing Security Risk in the Transition to 5G Chair: Lee Thibaudeau, Nsight. Working Group 3: Managing Security Risk in Emerging 5G Implementations Chair: Farrokh Khatibi, Qualcomm Working Group 4: 911 Security Vulnerabilities During the IP Transition Chair: Mary A. Boyd, West Safety Services Working Group 5: Improving Broadcast Resiliency Chair: Pat Roberts, Florida Association of Broadcasters Working Group 6: SIP Security Vulnerabilities Chair: Danny McPherson, Verisign

1 0

Re: 44/8
by Scott Weeks 23 Jul '19

23 Jul '19

> On Mon, Jul 22, 2019 at 4:02 PM Jerry Cloe <jerry(a)jtcloe.net> wrote: > > > There's already widespread use (abuse ?) of DOD /8's. > > T-Mobile commonly assigns 26/8 space (and others) to > > customers and nat's it. > --- cb.list6(a)gmail.com wrote: > From: Ca By <cb.list6(a)gmail.com> > > My understanding is that is not currently commonly the > case > https://www.worldipv6launch.org/apps/ipv6week/measurement/images/graphs/T-M… > --------------------------------------------------- On Mon, Jul 22, 2019 at 4:31 PM Scott Weeks <surfer(a)mauigateway.com> wrote: > Did they renumber (IPv4) out of that space? Or are > they just not continuing to expand into it? --- cb.list6(a)gmail.com wrote: From: Ca By <cb.list6(a)gmail.com> They stopped using ipv4 assigned for handsets for most cases with 464xlat <snip> -------------------------------------- Ah, OK. I didn't realize they were just using it for handsets. I thought the address space was used elsewhere. When orgs do this the ugliness of squatting sticks to the org seemingly forever like stink on sh!+ scott

1 0

Re: 44/8
by Scott Weeks 23 Jul '19

23 Jul '19

On Mon, Jul 22, 2019 at 4:02 PM Jerry Cloe <jerry(a)jtcloe.net> wrote: > There's already widespread use (abuse ?) of DOD /8's. > T-Mobile commonly assigns 26/8 space (and others) to > customers and nat's it. --- cb.list6(a)gmail.com wrote: From: Ca By <cb.list6(a)gmail.com> My understanding is that is not currently commonly the case https://www.worldipv6launch.org/apps/ipv6week/measurement/images/graphs/T-M… --------------------------------------------------- Did they renumber (IPv4) out of that space? Or are they just not continuing to expand into it? scott

2 1

RE: 44/8
by Scott Weeks 22 Jul '19

22 Jul '19

From:Michel Py <michel.py(a)tsisemi.com> As an extension of RFC1918, it would have solved the questionable and nevertheless widespread squatting of 30/8 and other un-announced DoD blocks because 10/8 is not big enough for some folks. --- jerry(a)jtcloe.net wrote: From: Jerry Cloe <jerry(a)jtcloe.net> There's already widespread use (abuse ?) of DOD /8's. T-Mobile commonly assigns 26/8 space (and others) to customers and nat's it. -------------------------------------------------- I participated in cutting Verizon Hawaii's assets into a standalone network for Hawaiian Telcom in 2005. They used 113/8 all over the place. I worked at HT for 5 years after that, left for nine years and am now back and I am STILL dealing with that crap! scott

1 0

AS3549 NOC contacts? Another BGP hijack
by Dmitry A.Deineka 22 Jul '19

22 Jul '19

Greetings, Unfortunately, ncc(a)gblx.net is not accepting emails anymore. Someone from AS3549 announced one of our network (more specific route) 46.28.67.0/24. It's not major impact but it's like that at least RIPE whois has outdated contact information about responsive persons. Can someone kindly share contact email of AS3549 (Centurylink?) NOC or other direct contacts? Regards, Dmitry -- Dmitry A.Deineka ITLDC

3 2

Contact for Crown Media in California
by Mike M 22 Jul '19

22 Jul '19

Hi, Looking for a contact number for Crown Media in Studio City, CA. Need access for a technician into that location. Thanks Mike Mackley Crown Castle Fiber

1 0

Anycast operators
by Mehmet Akcin 21 Jul '19

21 Jul '19

hey there, I am looking to talk to anycast based service operators dns and non-dns service operators to understand how virtualization is used in new generation anycast deployments. if you are running anycast based service (root-servers, tlds, etc.) please contact me offlist. mehmet

1 0