LACNOG2021 - Call for Presentations (Last 72 hours)

LACNOG 2021 - Call for Presentations     LACNOG, the Latin American and Caribbean Network Operators Group, will hold its LACNOG 2021 conference from 11 to 15 October 2021 together with the LACNIC 36 event.   The LACNOG 2021 Program Committee invites the Internet community to submit their pres

AS 3356 (Level 3) -- Community 3356:666

There is an old NANOG thread from 2005 that said AS 3356 (Level 3) were applying 3356:666 to indicate Peer route: https://archive.nanog.org/mailinglist/mailarchives/old_archive/2005-12/msg00280.html Also, see: https://onestep.net/communities/as3356/ Now network operators commonly use ASN:666 for

Re: AS 3356 (Level 3) -- Community 3356:666

$ whois AS3356 -h rr.level3.net | grep -E 'blackhol|666' remarks:   3356:666 - Peer route remarks:   3356: - blackhole (discard) traffic -- Patrick Am 04.08.2021 um 15:28 schrieb Sriram, Kotikalapudi (Fed) via NANOG: There is an old NANOG thread from 2005 that said AS 3356 (Level 3)

Re: AS 3356 (Level 3) -- Community 3356:666

Hello, there's exactly *one* blackhole well-known community, which should be used for this purpose - 65535:666 (standardised in RFC 7999). There's no reason to use even "ASN:666" format these days... - Daniel On 8/4/21 3:28 PM, Sriram, Kotikalapudi (Fed) via NANOG wrote: There is an old NANO

Re: AS 3356 (Level 3) -- Community 3356:666

Unless, of course, your BGP policy was written long before that RFC was established and you didn't think it was worth the config upgrade to support something that had been in use since around 1998 or so :) -Steve On Wed, Aug 4, 2021 at 10:27 AM Daniel Suchy via NANOG wrote: > Hello, > there's

Re: AS 3356 (Level 3) -- Community 3356:666

And it's also nice not to yank the old community in case your customers still depend on it, even if you do also support the RFC version as an alias of that one. Best regards, Martijn From: NANOG on behalf of Steve Meuse Sent: 04 August 2021 17:55 To: Daniel Su

Re: AS 3356 (Level 3) -- Community 3356:666

* Martijn Schmidt [Wed 04 Aug 2021, 18:01 CEST]: And it's also nice not to yank the old community in case your customers still depend on it, even if you do also support the RFC version as an alias of that one. Note that 3356:666 is applied on ingress to routes received from peers. They could

Re: AS 3356 (Level 3) -- Community 3356:666

>And it's also nice not to yank the old community in case your customers still >depend on it, even if you do also support the RFC version as an alias of that >one. That seems to be the case. Also, possibly the use of WKC 65535:666 has not picked up much. We observe that out of a total of 264,55

NANOG 83 Registration + 2020 Annual Report 👉

*NANOG 83 Registration Opens! * NANOG 83 will be our first hybrid meeting and will take place, November 1-3 in Minneapolis, MN. We are pleased to announce that meeting registration for NANOG 83 is now open! Your in-person conference registration includes fu

Where to get IPv4 block these day

hey everyone, Been a while since I had to deal with NetOps stuff. Was wondering, where do you go these days to get IPv4 blocks? It seems like getting assignments is hard due to exhaustion. I have found some "Auction" sites but it all feels very scammy. Any info would be appreciated. -James

Re: Where to get IPv4 block these day

It depends on the urgency and application of the block. You can get on the ARIN waitlist for a /24 block - current wait time is around 2-3 months; we waited around 3 for ours to be fulfilled. They distribute them in timed blocks from when old customers churn or get suspended. https://www.arin.net/

Re: Where to get IPv4 block these day

Ipv4.global is very reliable. I’ve sold blocks there On Thu, Aug 5, 2021 at 1:28 AM james jones wrote: > hey everyone, > > Been a while since I had to deal with NetOps stuff. Was wondering, where > do you go these days to get IPv4 blocks? It seems like getting assignments > is hard due to exhaus