RE: Nitel peering contact

[Christopher Trudeau]

Seth,

I'll contact you off-list and get you in touch with the right folks here.

Thanks,
Chris Trudeau

-Original Message-
From: NANOG  On Behalf Of Seth 
Mattinen
Sent: Thursday, April 9, 2020 3:28 PM
To: nanog@nanog.org
Subject: Nitel peering contact

Anyone from Nitel peering on here? The peer...@nitelusa.com address listed in 
peeringdb just returns an O365 "The group peering only accepts messages from 
people in its organization or on its allowed senders list"
error.



CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files or 
previous e-mail messages attached to it may contain confidential information 
that is legally privileged. If you are not the intended recipient, or a person 
responsible for delivering it to the intended recipient, you are hereby 
notified that any disclosure, copying, distribution or use of any of the 
information contained in or attached to this transmission is STRICTLY 
PROHIBITED. If you have received this transmission in error please notify the 
sender immediately by replying to this e-mail. You must destroy the original 
transmission and its attachments without reading or saving in any manner. Thank 
you.

Nitel peering contact

[Seth Mattinen]

Anyone from Nitel peering on here? The peer...@nitelusa.com address 
listed in peeringdb just returns an O365 "The group peering only accepts 
messages from people in its organization or on its allowed senders list" 
error.

South Africa Lockdown Extended

[Mark Tinka]

So the South African president has just extended our lockdown by another
2 weeks, to run until the end of April.

We expect network operations to remain an essential service, so if any
of you have any infrastructure down here, keep doing what you're doing.

Mark.

Re: Allstream Contact

[Forrest Christian (List Account)]

Replying on list...as others may be seeing something similar.

We had a problem which started over the weekend involving Allstream.  One
of their customers were announcing our prefixes, resulting in broken
connectivity.

I ended up calling the Zayo NOC, since Allstream seems to be part of zayo.
I also figured their NOC could earn some of the money we're paying them for
transit.  If you're not a zayo customer,  YMMV.

The report we got back was that some customer of Allstream was announcing
our prefixes "illegaly" and filters had been applied.  They also implied a
bit of clue would be dispensed.   Not sure if this is your issue or not.

On Thu, Apr 9, 2020, 12:59 PM David Pieper  wrote:

> Seeing some strange routing with Allstream and need to get it resolved.
> Please contact off list.
>
> Thanks,
> AS46276
>

Re: Traffic destined for 100.114.128.0/24

[Mark Tinka]

On 9/Apr/20 19:27, Randy Bush wrote:

>
> i think i will add those last prefixes to my filters.  will shut some of
> the mailing list noise down. :)

:-).

Mark.

Allstream Contact

[David Pieper]

Seeing some strange routing with Allstream and need to get it resolved. Please 
contact off list.

Thanks,
AS46276

Oracle Certification Exams...

[Michael Bullut via NANOG]

Greetings Team,

Are there any Oracle Certified Professionals in the group? Currently, I am
undertaking several Oracle certifications during this month and would to
inquire which materials did you use to prepare for the aforementioned?

Warm regards,

Michael Bullut.

---

*Cell:*
*+254 723 393 114.**Skype Name:* *Michael Bullut.*
*Blog: http://www.kipsang.com/ *
*E-mail:* *m...@kipsang.com *

*---*

Re: Calling Crown Castle Fibre sales

[Jason Lixfeld]

Thanks for all the replies.  I’m in contact with them now, thanks to the 
support here.

> On Apr 9, 2020, at 11:01 AM, Jason Lixfeld  wrote:
> 
> Can someone from Crown Castle Fibre sales ping me?  I haven’t heard back 
> after submitting on your contact form.
> 
> Thanks.

Re: Traffic destined for 100.114.128.0/24

[Randy Bush]

>     from {
>     source-address {
>     10.0.0.0/8;
>     100.64.0.0/10;
>     127.0.0.0/8;
>     169.254.0.0/16;
>     172.16.0.0/12;
>     192.0.2.0/24;
>     192.42.172.0/24;
>     192.168.0.0/16;
>     198.18.0.0/15;
>     198.51.100.0/24;
>     203.0.113.0/24;
>     41.87.96.0/19;
>     41.206.96.0/19;
>     41.217.212.0/22;
>     105.16.0.0/12;
>     }
>     destination-address {
>     0.0.0.0/0;
>     }
>     }
>     then {
>     count filter-incoming-anti-spoofing-counter;
>     syslog;
>     discard;
>     }
> }

i think i will add those last prefixes to my filters.  will shut some of
the mailing list noise down. :)

randy

RE: Calling Crown Castle Fibre sales

[Jordan Medlen]

Hit me off list. I will give you the contact information for whom I deal with, 
and even if he cannot help you directly, he can probably provide a push 
internally.

Thanks,

Jordan Medlen
Director, Technology Services

P 813.612.6207



-Original Message-
From: NANOG  On Behalf Of Jason Lixfeld
Sent: Thursday, April 9, 2020 11:02 AM
To: NANOG mailing list 
Subject: Calling Crown Castle Fibre sales

Can someone from Crown Castle Fibre sales ping me?  I haven’t heard back after 
submitting on your contact form.

Thanks.

Calling Crown Castle Fibre sales

[Jason Lixfeld]

Can someone from Crown Castle Fibre sales ping me?  I haven’t heard back after 
submitting on your contact form.

Thanks.

Re: Traffic destined for 100.114.128.0/24

[Mark Tinka]

On 9/Apr/20 15:24, Tom Hill wrote:

> Short answer: filter 100.64.0.0/10 from your upstreams, as you would
> 192.168.0.0/16 or 10.0.0.0/8.

I was trying to remind myself what we did back in the day. Looks like
that's been in on our end for yonks:

tinka@all.boxes-re0# show firewall family inet filter filter-incoming
term 10 {
    from {
    source-address {
    10.0.0.0/8;
    100.64.0.0/10;
    127.0.0.0/8;
    169.254.0.0/16;
    172.16.0.0/12;
    192.0.2.0/24;
    192.42.172.0/24;
    192.168.0.0/16;
    198.18.0.0/15;
    198.51.100.0/24;
    203.0.113.0/24;
    41.87.96.0/19;
    41.206.96.0/19;
    41.217.212.0/22;
    105.16.0.0/12;
    }
    destination-address {
    0.0.0.0/0;
    }
    }
    then {
    count filter-incoming-anti-spoofing-counter;
    syslog;
    discard;
    }
}
term 65535 {
    then {
    policy-map UPSTREAM-TRAFFIC-INBOUND;
    forwarding-class best-effort;
    accept;
    }
}

{master}[edit]
tinka@all.boxes-re0#


>
> Longer answers will no doubt be available. :)

As the Afrikaaners say, "Finish & Klaar" :-).

Mark.

Re: Traffic destined for 100.114.128.0/24

[Tom Hill]

On 08/04/2020 19:42, Drew Weaver wrote:
> I’ve noticed over the past couple of weeks that some hosts on a network
> I manage appear to be trying to reach hosts in this network 100.114.128.0/24
> 

Short answer: filter 100.64.0.0/10 from your upstreams, as you would
192.168.0.0/16 or 10.0.0.0/8.

Longer answers will no doubt be available. :)

-- 
Tom