Re: Bestel/AS18734 Contact

Disregard. Shortly after emailing this out, we received word back. On Wed, Jun 26, 2019 at 3:25 PM Christopher Smalling < christopher.small...@neonova.net> wrote: > Does anyone have a contact for Bestel/AS18734? We've been having peering > issues with them on and off for a while now, and can't

Re: Anyone from AT/AS7018 available?

https://seclists.org/nanog/2019/Jun/ On 27/06/2019 00:32, TJ Trout wrote: And they aren't archived when you post to the list anyway? On Wed, Jun 26, 2019, 3:31 PM Randy Bush > wrote: +20 signature.asc Description: OpenPGP digital signature

Re: Anyone from AT/AS7018 available?

And they aren't archived when you post to the list anyway? On Wed, Jun 26, 2019, 3:31 PM Randy Bush wrote: > > um, blaring someone's personal email address to 10,000 people for a > > work related thing? > > +20 >

Re: Anyone from AT/AS7018 available?

> um, blaring someone's personal email address to 10,000 people for a > work related thing? +20

Re: FCC workshop: Security vulnerabilities within our communications networks

On 6/26/19 2:17 PM, Scott Weeks wrote: > > --- s...@donelan.com wrote: > From: Sean Donelan > > If they come up with a better idea, that's great. I'll > take good ideas from anywere. In my experience, "design by committee" is most successful when one or two people take the bull by the horns

Re: FCC workshop: Security vulnerabilities within our communications networks

--- s...@donelan.com wrote: From: Sean Donelan If they come up with a better idea, that's great. I'll take good ideas from anywere. FCC. gov't. Design by committee. Never seen good design come out of these, but like Chris said, maybe today's the

Re: FCC workshop: Security vulnerabilities within our communications networks

NANOG: Come for the network info! Stay for the dry humor! On Wed, Jun 26, 2019 at 3:28 PM j k wrote: > Not bad, only took 15 years. > > On Wed, Jun 26, 2019, 6:29 PM Christopher Morrow > wrote: > >> On Wed, Jun 26, 2019 at 1:17 PM Sean Donelan wrote: >> > >> > On Tue, 25 Jun 2019,

Bestel/AS18734 Contact

Does anyone have a contact for Bestel/AS18734? We've been having peering issues with them on and off for a while now, and can't seem to get any response through their contacts listed with ARIN or on PeeringDB. Calls to support are fruitless, with nobody knowing where to direct us. -- Chris

Re: Anyone from AT/AS7018 available?

um, blaring someone's personal email address to 10,000 people for a work related thing? Really? Nick TJ Trout wrote on 26/06/2019 19:48: try Jay Borkenhagen On Wed, Jun 26, 2019 at 11:31 AM Christopher Rogers wrote: I'm a customer of 7018 and am currently struggling to get anyone

Re: FCC workshop: Security vulnerabilities within our communications networks

Not bad, only took 15 years. On Wed, Jun 26, 2019, 6:29 PM Christopher Morrow wrote: > On Wed, Jun 26, 2019 at 1:17 PM Sean Donelan wrote: > > > > On Tue, 25 Jun 2019, Christopher Morrow wrote: > > > looks like our best and brightest have the problem resolved, phew! > > > we're all safe now. >

Re: Anyone from AT/AS7018 available?

try Jay Borkenhagen On Wed, Jun 26, 2019 at 11:31 AM Christopher Rogers wrote: > I'm a customer of 7018 and am currently struggling to get anyone to look > at a bgp misconfiguration within 7018- it's like pissing into a hurricane. > If anyone is available could you kindly ping me offlist? > >

Anyone from AT/AS7018 available?

I'm a customer of 7018 and am currently struggling to get anyone to look at a bgp misconfiguration within 7018- it's like pissing into a hurricane. If anyone is available could you kindly ping me offlist? cheers -chris

Re: FCC workshop: Security vulnerabilities within our communications networks

On Wed, Jun 26, 2019 at 1:17 PM Sean Donelan wrote: > > On Tue, 25 Jun 2019, Christopher Morrow wrote: > > looks like our best and brightest have the problem resolved, phew! > > we're all safe now. > > The success rate of most groups has been low in this area, so I' willing > let new groups try.

Re: FCC workshop: Security vulnerabilities within our communications networks

On Tue, 25 Jun 2019, Christopher Morrow wrote: looks like our best and brightest have the problem resolved, phew! we're all safe now. The success rate of most groups has been low in this area, so I' willing let new groups try. I mostly just to keep an eye on new groups in case they do

Re: Issue with point to point VPNs behind NAT and asymmetric traffic

The issue is resolved by tweaking the route validation. Added following my ansible playbook for both ends: - name: Enable Controls source route verification sysctl: name: net.ipv4.conf.default.rp_filter value: '0' sysctl_set: yes - name: Do not