Generally widely available and supported by all the major vendors, although
to the best of my knowledge only on specific hardware. Linux implementation
is pretty robust at this point as well.
Like anything else, different vendors have some implementation quirks , but
by and large the spec has been
>
> On the DWDM side, expect to add between 0.3W of energy @ 100G, and 0.6W
> @ 400G, when encryption is enabled.
>
> Something to keep in mind if power and/or thermal management are crucial
> for you.
Are you talking about L1OE here, not MACSEC?
On Thu, Dec 19, 2024 at 9:42 AM Mark Tinka wrote
I've noticed that the whitebox hardware vendors are pushing distributed router
fabrics, where you can keep buying pizza boxes and hooking them into a larger
and larger fabric. Obviously, at some point, buying a big chassis makes more
sense. Does it make sense building up to that point? What are
It's not a new vector, but it's not super common either. I wrote about it back
in August of 2022, Hetzner's automated abuse system was being used as a denial
of service vector, as the malicious actor just spoofed the victim IP(s) toward
their network, and the abuse reports were automatically sen
This is an automated weekly mailing describing the state of the Global
IPv4 Routing Table as seen from APNIC's router in Japan.
The posting is sent to APOPS, NANOG, AfNOG, SANOG, PacNOG, SAFNOG
UKNOF, TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG and the RIPE Routing WG.
Daily listings are sent to bg
That seems about right -- $70k per mile for main-line in a relatively rural
area is what we're looking at right now. Depends on a lot of things
(directional boring vs direct plow, etc).
-Original Message-
From: "Justin Streiner"
Sent: Friday, December 20, 2024 4:45pm
To:
Cc: nanog@
Send that builder a fruit basket. That's behavior we need to encourage.
--TimH
On Fri, 20 Dec 2024 16:45:15 -0500
Justin Streiner wrote:
> We were also very fortunate that the builder provided two 2" Schedule 40
> conduits from the side of our house out to the utility hand-holes in the
> right
I just realized that in my previous message I flipped 2 numbers in the AS.
I'm looking for a contact for AS36351 (not 35361).
Kind Regards,
Richard
From: Richard Desjardine
Sent: December 20, 2024 09:22
To: nanog@nanog.org
Subject: AS36351 - IBM Cloud Conta
On Thu, 19 Dec 2024, Karl Auer wrote:
A friend was involved in a development project in a regional town. They
specified conduits everywhere. When the network people showed up at
some random later date, they mostly just had to pull stuff through
existing conduits. Not sure of the details beyond th
Good day,
We have 45.59.96.0/22 that can not reach destinations on the IBM Cloud -
AS35361.
I have shifted our routing around to validate that regardless of which of our
upsteam transit providers we send the traffic on it always fails when it
reaches their edge which is through Torix for us du
You may try the contacts in Whois. I had a similar issue a month or two ago and
got a swift response that way… ended up being related to some stale
blacklisting.
On Dec 20, 2024, at 08:25, Richard Desjardine via NANOG wrote:
Good day,
We have 45.59.96.0/22 that can not reach destinations on
When my wife and I were preparing to build our house a few years ago, solid
terrestrial connectivity was one of the top things on my must-have list,
because we both work from home the vast majority of the time.
It took some tenacity with the local FTTH provider to determine if they
served this are
12 matches
Mail list logo
