On Sun, Jul 21, 2024, 18:31 J. Hellenthal via NANOG wrote:
>
>
> On Jul 21, 2024, at 19:28, Randy Bush wrote:
>
>
>
> I think the hipster thing to do now, though, is --auto-locate-key with
>
> the Web Key Distribution or the DNSSEC Key Distribution mechanism.
>
>
> i have done wkd for a fair w
This entirely discounts the fact that bcp-38 and bcp-84 which, more or
less, eliminate this "problem space" entirely.
I find it hard to believe ntp reflection is actually a problem in the year
2023, assuming you're not running a ridiculously old ntp client and have
taken really simple steps to pro
where I've tried it, and
after some time, the same thing happens.
-mel beckman
On Jul 14, 2023, at 8:05 AM, Neil Hanlon wrote:
Hi all - I apoligize for the not-necessarily-on-topic post, but I've been
struggling with this issue for the past two
weeks and am about out of ideas an
really appreciate any and all
help. Please contact me off list if you need
additional details--I can provide ticket numbers/conversation IDs/etc, as well
as graphs/logs/etc.
Best,
Neil Hanlon
signature.asc
Description: PGP signature
scammers and attackers aren't well known for their eloquent prose...
As soon as you decide to not take one thing seriously, how do you draw the
line? three spelling mistakes and the wrong tense of a verb means its fake?
I'd rather not play chicken with peoples' lives.
On Tue, Oct 19, 2021, 14:11
and I need more coffee... PacketFenCe
*sigh*
https://www.packetfence.org/
On Fri, Sep 17, 2021, 13:22 Neil Hanlon wrote:
> it's a bit more than just freeradius, but PacketFense is no-bs GPL
> software to do this, among much more.
>
> I think it'd definitely do wha
it's a bit more than just freeradius, but PacketFense is no-bs GPL software
to do this, among much more.
I think it'd definitely do what you're looking to do
--Neil
On Fri, Sep 17, 2021, 12:30 Mark Tinka wrote:
> Hi all.
>
> I haven't been in the space in yonks, but I'm having to look into it
Yeah, had several test nodes transiting to me fail via Comcast it seems.
On Wed, Feb 24, 2021, 23:31 Jason Kuehl wrote:
> Anyone else with Comcast have a small outage? About 5-7 minutes?
>
> --
> Sincerely,
>
> Jason W Kuehl
> Cell 920-419-8983
> jason.w.ku...@gmail.com
>
I think the Galago Pro from System 76 probably fits the bill. It's a 14",
but has everything else you wanted, I believe.
They do have their own open (not sure of license) boot... Firmware? Called
core boot... So no bios (uefi or otherwise). Plus side is its all open
(free) drivers and firmware and
Surely they can just put them in an array.
;)
On Mon, Nov 16, 2020, 21:54 Valdis Klētnieks
wrote:
> On Mon, 16 Nov 2020 17:36:58 -0800, Sabri Berisha said:
>
> > Also, in the case that I described it wasn't a Junos device. Makes me
> wonder how bugs
> > like that get introduced. One would expe
While I agree it is objectively irresponsible to abandon a project without
passing it to another, I think that possibly in this situation we don't
know all the details?
2020 has been a difficult year for everyone. Perhaps Paul (and whomever
else may be responsible for Phoenix-IX) were subject to t
And if so, can you set up your own service to remove their iptables rule
after it's been added or otherwise counteract it.
At least temporarily, anyways.
-Neil
On Wed, Oct 28, 2020 at 4:26 PM Ryan Hamel wrote:
> I'm curious to know why they would add such a thing, and how you got the
> iptable
Happy Monday, folks
Having some trouble with some customer traffic taking a seemingly-'scenic'
route on its way to/from us. Customer is in Massachusetts, we're in
Massachusetts.. But if I'm reading these traceroutes correctly, the traffic
is going down to NYIIX and meeting between AS6079 and our t
According to peering db, their noc email is at peering AT
disneystreaming.com. They may be able to assist. Probably you could try
some variation of 'noc@', too.
Good luck!
On Sun, Oct 25, 2020, 06:50 Sander Steffann wrote:
> Hi,
>
> Anybody around from Disney+? my main customer (Solcon) is an
I will be there tomorrow afternoon & will see what I can do.
On Wed, Aug 19, 2020 at 4:35 PM Jason Kuehl wrote:
> One Summer is overdue for its annual fire.
>
> On Wed, Aug 19, 2020 at 4:14 PM Rod Beck
> wrote:
>
>> Does everyone agree that the 4 most important data centers are 1 Summer,
>> Cor
Respectfully:
How can something be deployed if it doesn't even exist?
I think we'd all be better off focusing on deploying real things with real
implementations--you know, like IPv6... And not debating the merits of a
protocol that doesn't exist except in.. Umm.. "theory".
And I'll save you so
More of an "ideas guy" I guess
On Wed, May 13, 2020 at 3:33 PM Töma Gavrichenkov wrote:
> Peace,
>
> On Wed, May 13, 2020, 10:07 PM Elad Cohen wrote:
>
>> "As a matter of fact" - if you created an implementation please send me
>> the sourcecode.
>>
>
> Wait, so you're coming up publicly with a
I really love that the entire premise of this stems from that people doing
'software upgrades' to IPv4-2 - Electric Boogaloo would be any faster than
those same people just migrating to IPv6. Seriously hilarious.
If they won't move to something already supported on their software, why
would operat
I think you just need to let scripts run in your browser for nanog.org.
It uses Javascript to add the emails in after the fact, it appears.
On Apr 21, 2020, 17:15, at 17:15, William Herrin wrote:
>Howdy,,
>
>How do we contact the nanog mail admins? I looked at
>https://archive.nanog.org/list and
Having a bit of a weird issue where traffic from one of our data centers
looks to be getting a response for googleapis.com which is in Malaysia,
despite the data center being in northeast USA--assuming I'm reading the
reverse DNS on the IP addresses right (228.27.217.172.in-addr.arpa domain
name po
RCN here in the greater Boston area does CGNAT inside 10.0.0.0/8. This doesn't
surprise me.
On Oct 10, 2019, 11:27, at 11:27, Javier J wrote:
>Very strange ATT would put end users on an RFC 1918 block unless they
>were
>doing NAT to the end user.
>If they were doing NAT, I would expect CGNAT in
I've got a whole bunch running with no issues.. Mostly MM/850nm though, so
maybe a bit different than their SM stuff. Also have a handful (literally)
of the SM ones, and haven't had any issues (yet).
Only "problem" I've had is a copper SFP from them which may have burned out
and fried a switchport
22 matches
Mail list logo
