On Jul 17, 2019, at 20:54, Randy Bush wrote:
>
> do folk use `netstat -s` to help diagnose on routers/switches?
I have used netstat -s on hosts to look at error counters if a switch or router
was suspect.
But that was a while ago (anyone remember when NFS corrupted all your files if
one of
On Thu, Jul 18, 2019 at 12:44 PM Hank Nussbacher wrote:
> On 18/07/2019 08:44, Töma Gavrichenkov wrote:
> > Qrator guy there.
> > Real-time notifications are there but are only available on a
> > commercial basis, because basically real time is expensive to compute.
> > The rest is free.
>
> What
I think there is a key misconception here.
The original IANA delegation to “Amateur Radio Digital Communication” was not
to any organization with such a name, but was a statement of the purpose of the
delegation. An individual who initiated the process took on the administration
of the block
On Fri, Jul 19, 2019 at 6:02 PM Owen DeLong wrote:
> I honestly don’t know who is behind ARDC (the organization), but some of
> the names bandied about are people I know and believe to be deserving of
> the benefit of the doubt. As such, I’m still trying to learn more before I
> go full tilt
Worthwhile noting however that they’re not reliably pushing notifications to
people on their notifications list.
Worthwhile checking fundamentals you do depend on with your own low level
monitoring.
-George
Sent from my iPhone
> On Jul 18, 2019, at 10:30 PM, Mikael Abrahamsson wrote:
>
>>
On 18 Jul 2019, at 11:40 PM, Majdi S. Abbas
mailto:m...@latt.net>> wrote:
...
There are some potential legal title questions around this,
and if ARIN is facilitating transactions with questionable history,
that is something the Internet community might be concerned about.
Majdi -
If you believe
On Wed, Jul 17, 2019 at 05:54:49PM -0700, Randy Bush wrote:
> do folk use `netstat -s` to help diagnose on routers/switches?
I (mostly) use it on firewalls, but yes, it's something I turn
to fairly often (along with other incantations of netstat, plus
lsof and other tools).
---rsk
On Thu, Jul 18, 2019 at 11:13:24PM -0400,
Majdi S. Abbas wrote
a message of 26 lines which said:
> Amusingly, they still seem to be advertising the covering
> aggregate,
Are you sure? RIPE stat shows it stopped one month ago
On 11 Jul 2019, at 3:23 PM, Michael Thomas wrote:
>
> I used to think that email spam was a law enforcement problem too, but it's
> become very clear that law enforcement has little to no interest in solving
> geeks' problems.
Law enforcement deals with legal entities (persons, organizations)
On 07/18/2019 at 23:08, Job Snijders wrote:
> A potential upside is that hamnet operators maybe have access to some RPKI
> services now!
OK, I'll bitehow do you mean?
--Adam
I've been testing out thousandeyes for the past 1,5-2 month(s) and I'm very
happy with it.
Depending on what you want to do with it, it can be expensive but for my
current employer it's worth the investment due to the extra visibility it
provides.
-- Kostas (Konstantinos) Koutalis
Sent from my
On 19/07/18 11:02, Christopher Morrow wrote:
> So.. this is/was a legacy allocation, right? with some 'not great'
> contact/etc info...
> the ARIN folk could have said: "Well sure! if the current folk who
> control access can positively show they do AND they don't mind parting
> with a /10...
On Thu, Jul 18, 2019 at 10:45 PM William Waites wrote:
>
> Then we can decide, openly and transparently, if, for example, some piece
> of
> 44/8 should be returned to IANA for allocation to the RIRs.
>
This sounds like the more correct answer with regard to what should be done
with space that
> On Jul 19, 2019, at 6:03 AM, John Curran wrote:
> Be specific in your report regarding what change you believe was in error and
> why – we investigate all such reports and will correct any changes made in
> error.
Actually, I’d love to hear an official statement from ARIN about the state
On 7/19/19 6:33 AM, Matt Harris wrote:
After reading the analogy above regarding spectrum space, I shudder to
think what the community response would be if the FCC were to tacitly
allow the ARRL to receive several million (or billion in this case)
dollars from, say, Verizon in exchange for
On 19 Jul 2019, at 10:37 AM, Brielle mailto:br...@2mbit.com>>
wrote:
On Jul 19, 2019, at 6:03 AM, John Curran
mailto:jcur...@arin.net>> wrote:
Be specific in your report regarding what change you believe was in error and
why – we investigate all such reports and will correct any changes made
On Fri, Jul 19, 2019 at 9:38 AM Brielle wrote:
>
> > On Jul 19, 2019, at 6:03 AM, John Curran wrote:
> > Be specific in your report regarding what change you believe was in
> error and why – we investigate all such reports and will correct any
> changes made in error.
>
> Actually, I’d love to
I suspect the Vatican was involved :)
-mel
> On Jul 19, 2019, at 12:20 AM, George Herbert wrote:
>
> Worthwhile noting however that they’re not reliably pushing notifications to
> people on their notifications list.
>
> Worthwhile checking fundamentals you do depend on with your own low
Because questions have arisen here that are well answered by
a short series of postings from the 44net mailing list, at the
request of the author [Phil Karn] and others, I am reposting
them here.
- Brian
From: Phil Karn
Subject: [44net] 44.192.0.0/10 sale
Hello all,
I've not been
>
> Was ARIN not involved? If not, why not? 44/8 isn’t like a normal
> assignment. It’s a legacy assignment likely with stipulations from when it
> was originally assigned to the HAM group(s).
>
My recollection from some years ago was that the IANA assignments done
before the RIR system were
On Fri, Jul 19, 2019 at 9:54 AM John Curran wrote:
>
> As stated before, ARIN did receive and process a request from the 44/8
> registrant to transfer a portion of the block to another party.
>
> For all transfer requests, we review and confirm:
>
> - That the source of the transfer is the legal
On 19 Jul 2019, at 11:06 AM, Matt Harris wrote:
>
> Hey John,
> I think perhaps the relevant questions for ARIN here are:
> ...
Matt -
ARIN doesn’t publicly discuss details of any specific registration requests;
you would need to refer any of those questions to the registrant.
Thanks,
On Fri, Jul 19, 2019 at 10:58 AM Matt Harris wrote:
>Hence it's no longer "legacy" space that isn't covered by an RIR RSA but is
>instead now covered by an ARIN RSA.
>
'RIR RSA" is not a thing.
Legacy blocks are basically drifting in the winds... there's no
requirement on the holders to do
Hi Guys
Today there are over 200 networks announced on big internet on 44/8.
It's normal ?
Ciao,
Il giorno ven 19 lug 2019 alle ore 17:17 John Curran ha
scritto:
> On 19 Jul 2019, at 11:06 AM, Matt Harris wrote:
> >
> > Hey John,
> > I think perhaps the relevant questions for ARIN here are:
On 19 Jul 2019, at 11:12 AM, Christopher Morrow wrote:
>
> On Fri, Jul 19, 2019 at 10:58 AM Matt Harris wrote:
>
>> Hence it's no longer "legacy" space that isn't covered by an RIR RSA but is
>> instead now covered by an ARIN RSA.
>
> 'RIR RSA" is not a thing.
> Legacy blocks are basically
Personaly I think that circumstance weighs the benifits of the utilities
used to diagnose a problem. Given any instance, you use the utilities
available to you to see that problem through to completion of a proper
result.
The question in hand is very broad but particular to an instance that is
>
> If they choose to they could have (in the ARIN region) signed a LRSA,
> but that's even been removed, in favor
> of the now much more watered down RSA.
>
I believe ARCD would have been required to sign an LRSA (if they had not
previously) in order to transfer the block to Amazon.
Also, a
On Fri, Jul 19, 2019 at 10:29 AM John Curran wrote:
>
> Matt -
>
> Chris is correct. Those who received IPv4 address blocks by InterNIC (or
> its predecessors) prior to the inception of ARIN on 22 December 1997 are
> legacy resource holders, and continue to receive those same registry
>
On 19 Jul 2019, at 11:34 AM, Matt Harris
mailto:m...@netfire.net>> wrote:
On Fri, Jul 19, 2019 at 10:29 AM John Curran
mailto:jcur...@arin.net>> wrote:
Matt -
Chris is correct. Those who received IPv4 address blocks by InterNIC (or its
predecessors) prior to the inception of ARIN on 22
On 19 Jul 2019, at 11:33 AM, Tom Beecher
mailto:beec...@beecher.cc>> wrote:
If they choose to they could have (in the ARIN region) signed a LRSA,
but that's even been removed, in favor
of the now much more watered down RSA.
I believe ARCD would have been required to sign an LRSA (if they had
Understood on specifics. But can you comment on the general ARIN policy on
the topic? My understanding was that once a legacy resource was transferred
, it was permanently removed as a legacy resource.
On Fri, Jul 19, 2019 at 11:42 AM John Curran wrote:
> On 19 Jul 2019, at 11:33 AM, Tom
On Fri, Jul 19, 2019 at 10:41 AM John Curran wrote:
> On 19 Jul 2019, at 11:34 AM, Matt Harris wrote:
>
> Hey John, I understand that, however my understanding is that the
> establishment of an ARIN RSA is required prior to the transfer of a block
> or a portion or a block via ARIN (such as the
On 19 Jul 2019, at 11:46 AM, Tom Beecher
mailto:beec...@beecher.cc>> wrote:
Understood on specifics. But can you comment on the general ARIN policy on the
topic? My understanding was that once a legacy resource was transferred , it
was permanently removed as a legacy resource.
As noted
Good deal. Thanks John, have a great weekend!
On Fri, Jul 19, 2019 at 11:52 AM John Curran wrote:
> On 19 Jul 2019, at 11:46 AM, Tom Beecher wrote:
>
>
> Understood on specifics. But can you comment on the general ARIN policy on
> the topic? My understanding was that once a legacy resource was
On 19 Jul 2019, at 11:50 AM, Matt Harris
mailto:m...@netfire.net>> wrote:
On Fri, Jul 19, 2019 at 10:41 AM John Curran
mailto:jcur...@arin.net>> wrote:
On 19 Jul 2019, at 11:34 AM, Matt Harris
mailto:m...@netfire.net>> wrote:
Hey John, I understand that, however my understanding is that the
On 7/19/19 11:02 AM, Brian Kantor wrote:
> Because questions have arisen here that are well answered by
> a short series of postings from the 44net mailing list, at the
> request of the author [Phil Karn] and others, I am reposting
> them here.
> - Brian
Brian,
You've done fuck all for
Well there is a very limited view
On Fri, Jul 19, 2019 at 12:13:24PM -0400, Bryan Fields wrote:
> On 7/19/19 11:02 AM, Brian Kantor wrote:
> > Because questions have arisen here that are well answered by
> > a short series of postings from the 44net mailing list, at the
> > request of the
Bryan,
I appreciate you passing on information about technical background regarding
the 44/10 sale, but before this discussion goes any further down a rathole, let
me point out tour vitriol is off-topic and doesn’t belong on this list. I for
one don’t appreciate you airing amateur radio
This might be an off topic since this is a confirmed issue with Microsoft
but I'm just wondering how vast are the affected users on this issue.
west coast user here.
-nathan
What's the issue?
On Fri, Jul 19, 2019 at 12:35 PM Nathanael Catangay Cariaga <
ncari...@gmail.com> wrote:
> This might be an off topic since this is a confirmed issue with Microsoft
> but I'm just wondering how vast are the affected users on this issue.
>
> west coast user here.
>
>
>
This discussion has been long, and I believe I've skimmed it -- but if
this was already discussed and answered I apologize...
The 44/8 block was assigned, if I'm not mistaken, specifically for
Amateur Radio use and Brian and all made sure that happened that way.
Does not the sale of the
I got this from the O365 Health Status Page:
[image: image.png]
On Sat, Jul 20, 2019 at 12:38 AM Ross Tajvar wrote:
> What's the issue?
>
> On Fri, Jul 19, 2019 at 12:35 PM Nathanael Catangay Cariaga <
> ncari...@gmail.com> wrote:
>
>> This might be an off topic since this is a confirmed
Taken from MS O365 Health Portal:
*Title: Can't access email User Impact: Users may be unable to connect to
the Exchange Online service. More info: Other services with dependencies on
Exchange Online, such as calendar access through Microsoft Teams, could
also be intermittently unavailable.
Good to know, but this is probably better suited for the Outages mailing
list.
On Fri, Jul 19, 2019 at 12:51 PM Nathanael Catangay Cariaga <
ncari...@gmail.com> wrote:
> Taken from MS O365 Health Portal:
>
> *Title: Can't access email User Impact: Users may be unable to connect to
> the Exchange
> And one of the principal people in the network telescope project was
> KC, who
> also weaseled herself onto the ARDC board without even holding an amateur
> radio license. Conflict of interest here, holy carp.
You are not in possession of all the facts.
KC (Kim Claffy) is KC6KCC.
--Phil
On Fri, 19 Jul 2019, Phil Karn wrote:
And one of the principal people in the network telescope project was
KC, who also weaseled herself onto the ARDC board without even holding
an amateur radio license. Conflict of interest here, holy carp.
You are not in possession of all the facts.
KC
Please take this off-topic argument off the Nanog list.
-mel via cell
> On Jul 19, 2019, at 11:17 AM, Mikael Abrahamsson wrote:
>
> On Fri, 19 Jul 2019, Phil Karn wrote:
>
>>> And one of the principal people in the network telescope project was KC,
>>> who also weaseled herself onto the ARDC
On Fri, 19 Jul 2019, Mikael Abrahamsson wrote:
On Fri, 19 Jul 2019, Phil Karn wrote:
And one of the principal people in the network telescope project was KC,
who also weaseled herself onto the ARDC board without even holding an
amateur radio license. Conflict of interest here, holy carp.
On 7/19/19 2:17 PM, Mikael Abrahamsson wrote:
> On Fri, 19 Jul 2019, Phil Karn wrote:
>
>>> And one of the principal people in the network telescope project was
>>> KC, who also weaseled herself onto the ARDC board without even holding
>>> an amateur radio license. Conflict of interest here,
Greetings,
Unfortunately, n...@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
NOC is 877-453-8353. That will get you the legacy Global Crossing (Level 3)
teams.
On Fri, Jul 19, 2019, 2:12 PM Dmitry A.Deineka wrote:
> Greetings,
>
> Unfortunately, n...@gblx.net is not accepting emails anymore. Someone from
> AS3549 announced one of our network (more specific route)
51 matches
Mail list logo
