Yes there is an assumption there. I may be wrong on this occasion
but the industry has a whole and repeated episodes on people reporting
that the NOCs are unreachable and then coming here, nanog, etc. to go in
via the back door.
For NOCs that are known to be responsive other members usually say
Hello all,
Since RPKI support by ROS V7.x was raised recently, with reports on
problems/bugs, I thought it timely to seek some update from MikroTik about
it :-}
First up, it is definitely worth remembering that any beta version should be
used for testing only - it is released as 'beta' because
I completely understand people wanting answers, since Telstra hijacked
our IP block (and others) back in November 2018 and blackholed all traffic.
It's a massively disruptive thing to occur to you, and there's
absolutely nothing you can do to prevent it (while providers don't
enforce RPKI and
That's an assumption Mark. The 'formal channel' for a network operator chasing
a route leak would be to look up PeeringDB and try that contact info. We don't
k now if the OP tried that so we don't know if that failed.
The fact that Telstra has staff (and I assume it's more than just Russell)
Story on Itnews this morning, its seem the problem was far bigger than
just a few ip ranges :)
https://www.itnews.com.au/news/telstra-routing-flub-affects-hundreds-of-networks-worldwide-554097
On 30/09/2020 09:42, Mark Andrews wrote:
> That however does mean that Telstra's formal channels
That however does mean that Telstra’s formal channels aren’t working
properly. If you can’t reach the NOC via formal channels then there
is a problem. No one should have to come here and ask for bad
announcements to be withdrawn. Russell shouldn’t have to do anything
but enjoy his time off when
I'll second this. Having Russell and is peers on the list and in a position to
help resolve problems in a timely manner is fantastic for our industry and our
clients. Telstra is a big beast with lots of moving parts, yet I've lost count
of the number of times issues have been addressed
Job didn’t ask for a RCA, he asked what action was taken at a very specific
time that resolved the impact.
This had major effects on the global Internet routing system, and a lot of
networks have applied some level of traffic engineering against AS1222
originated routes. I don’t think it
Perhaps it is best you take it through official channels then, rather
than pushing for information from a staffer who is
a) on leave
b) has no obligation to provide support through this channel - but
does so for the good of the community
It is amazing that it got fixed this way at all.
Hi Randy
awesome, that's what i wanted to know/confirm. I'm the originator.
Thanks
On Wed, 30 Sep 2020 at 01:18, Randy Cassidy
wrote:
> Hi Alex,
>
> The ROA is something you create/sign via your regional registry (APNIC in
> your case, ARIN for me). There's nothing you configure on your own
Dear 'DaZZa',
On Wed, Sep 30, 2020 at 07:38:24AM +1000, DaZZa wrote:
> What part of "Root cause investigations are underway" is difficult to
> understand?
I didn't ask for a root cause analysis.
> As much as I have an intense dislike for all things Telstra, this got
> fixed at 5:48 am AEST,
What part of "Root cause investigations are underway" is difficult to
understand?
As much as I have an intense dislike for all things Telstra, this got
fixed at 5:48 am AEST, according to Russell - it's now barely 07:40 am
AEST - demanding a root cause analysis in less than 2 hours from an
Dear Russell,
At 20:32 UTC something transpired that remedied the issue, what was that
action?
What assurances do we have that this doesn't happen again in the next 24
hours?
Kind regards,
Job
On Wed, Sep 30, 2020 at 07:06:38AM +1000, Russell Langton wrote:
> Hi job,
> Root cause
Hi job,
Root cause investigations are underway with the teams.
Thanks.
On Wed, 30 Sep 2020, 6:49 am Job Snijders, wrote:
> Dear Russell,
>
> Thank you for this update.
>
> Do you have any information on what transpired?
>
> Kind regards,
>
> Job
>
> On Wed, Sep 30, 2020 at 06:47:00AM +1000,
Dear Russell,
Thank you for this update.
Do you have any information on what transpired?
Kind regards,
Job
On Wed, Sep 30, 2020 at 06:47:00AM +1000, Russell Langton wrote:
> Hi,
> This should be resolved now.
> Please advise if any further issues.
>
>
> On Wed, 30 Sep 2020, 5:48 am Russell
Looks good to me now, thank you again for your assistance!
On Tue, 29 Sep 2020, at 16:47, Russell Langton wrote:
> Hi,
> This should be resolved now.
> Please advise if any further issues.
>
>
> On Wed, 30 Sep 2020, 5:48 am Russell Langton, wrote:
> > Hi,
> > I'm on leave but getting the
Hi,
This should be resolved now.
Please advise if any further issues.
On Wed, 30 Sep 2020, 5:48 am Russell Langton, wrote:
> Hi,
> I'm on leave but getting the right teams to review asap.
>
>
> On Wed, 30 Sep 2020, 4:44 am Sadiq Saif, wrote:
>
>> Can somebody from Telstra's NOC contact me off
Hi,
I'm on leave but getting the right teams to review asap.
On Wed, 30 Sep 2020, 4:44 am Sadiq Saif, wrote:
> Can somebody from Telstra's NOC contact me off list please?
>
> Y'all are leaking the following prefixes:
> 208.100.53.0/24, 67.202.70.0/24, 69.162.134.0/24, 208.117.38.0/24,
>
Hi Alex,
The ROA is something you create/sign via your regional registry (APNIC in
your case, ARIN for me). There's nothing you configure on your own routers
as far as announcing your (signed or unsigned) prefixes to your Transit
providers. The ROA basically says "it is valid for the following
Can somebody from Telstra's NOC contact me off list please?
Y'all are leaking the following prefixes:
208.100.53.0/24, 67.202.70.0/24, 69.162.134.0/24, 208.117.38.0/24,
50.31.98.0/24
Correct origin is AS32748, not AS1221.
I am contacting on behalf of my employer who is a Steadfast customer.
Hi
I'll answer the last.
So if I am the origin and I use multiple transit providers. Don't I have
to sign mine. So I get i have to go to myapnic and setup a ROA. but don't
i have to sign my prefix (sorry, i'm new to this), before send this up
stream. Isn't the verification done by checking the
Hi Alex,
If you are not doing ROV (Route Origin Validation) then you don't have to
do anything on your end. Great to hear that Exetel is planning to do
validation but that means you have to create ROAs (Route Origin
Authorization) on myapnic portal, if you don't have them already.
Regards,
Aftab
You don't need to touch your routers to make your upstream carrier happy
when it comes to RPKI.
All you have to do is create Route Origin Authorisations (ROAs) for your
prefixes in MyAPNIC.
On Tue, 29 Sep 2020, 16:47 Alex Samad, wrote:
> Hi
>
> Wondering how prevalent is RPKI in transit
I can testify to RoS v7 being garbage,
I started configuring our network on it and was pulling hair out at the half
baked BGP options
Our upstream does RPKI filtering so I don't see the need to configure it
directly.
Jett Jackson
Hosting and Automation Lead
E j...@lumity.com.au
T 1300
Hi Alex,
Mikrotik’s RouterOS v7 apparently is supposed to support RPKI, however as you
know Mikrotik has been talking about v7 for years. The current beta version is
severely broken to the point where it is surprising it made it to the beta
stage.
From my understanding (and I’m sure I’ll be
Hi
Wondering how prevalent is RPKI in transit providers in Oz. Just got an
email from exetel to say they are starting a rollout of it.
Seems like my ROS routers don't have it, seems like they have been talking
about back in 2014, still waiting on that feature to be added.
Curious if all of my
Hi Noggers
We have an issue with getting in contact with anyone from the optus
infrastructure team (seems like some redundancies /job changes recently).
does anyone have a potential contact or on this list from optus?
Thanks
Simon
___
AusNOG mailing
27 matches
Mail list logo
