- Test - lists.nanog.org

Re: NANOG Digest, Vol 145, Issue 25
by Jason Pope 26 Feb '20

26 Feb '20

Would it be possible to deploy one switch for every three floors? So each switch would service the floor that they are on, along with the floor below and the floor above? That would reduce your switch count to ten and you should be able to use an the vendors ethernet ring protocol. If you use bidirectional optics, you should be able to set up two ethernet rings of five switches. Jason K Pope Greater love has no one than this, that one lay down his life for his friends. John 15:13 > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 25 Feb 2020 13:40:20 +0100 > From: Alex Band <alex(a)nlnetlabs.nl> > To: NANOG list <nanog(a)nanog.org> > Subject: Re: Has Anyone managed to get Delegated RPKI working with > ARIN > Message-ID: <7A5ABDFB-56EA-46C5-B553-94346A52EEEA(a)nlnetlabs.nl> > Content-Type: text/plain; charset=utf-8 > > An update: > > The setup process with ARIN has now been fixed in Krill 0.5.0, which was > just released: > https://www.nlnetlabs.nl/news/2020/Feb/25/krill.0.5.0-released/ > > We have worked around the issue by transforming the child request XML file > in the user interface using a toggle: > https://rpki.readthedocs.io/en/latest/krill/parent-interactions.html#arin > > The ensured that Krill is compatible with both the old and new response > file format. Once ARIN conforms to RFC 8183, this toggle will be removed in > a future version. We have also fixed two blocking issues with APNIC, > ensuring Krill now works with every RIR implementation. > > Looking forward to your feedback on this release. > > Cheers, > > Alex > > > On 13 Feb 2020, at 09:48, Alex Band <alex(a)nlnetlabs.nl> wrote: > > > > Hi there! > > > > There is also this somewhat hacky SED command to transform the Request > XML into the format that ARIN accepts, in case you’d like to use something > other than the XSL: > > > > https://sed.js.org/?gist=3f08fb293c8825855bb26f2865161575 > > > > –– Looping in John Curran > > > > John, I appreciate ARIN has accepted RFC 8183 compatibility as an ACSP > suggestion: > > > > https://www.arin.net/participate/community/acsp/suggestions/2020-3/ > > > > Looking at the XML though, the changes needed to make this work are one > tag, a URL and a version number. Could this please be tracked as a simple > bug instead of a "feature to include in our future RPKI improvements”? > > > > In the mean time I have added a warning to the documentation: > > > https://rpki.readthedocs.io/en/latest/krill/manage-cas.html#step-1-get-the-… > > > > Thanks! > > > > -Alex > > > >> On 5 Feb 2020, at 16:48, Tim Bruijnzeels <tim(a)nlnetlabs.nl> wrote: > >> > >> Hi, > >> > >> Everyone is welcome to read that list of course, but the TL;DR is: > >> > >> ARIN currently uses a pre RFC 8183 format for the identity exchange. It > would be good if this were updated. New versions of rpkid as well as Krill > have issues with the old format. > >> > >> In the meantime this XSL provided by rpki.net can be of help: > >> > https://raw.githubusercontent.com/dragonresearch/rpki.net/master/potpourri/… > >> > >> Note: if you are planning to give Krill a try we recommend that you > wait for version 0.5. We expect to have this version ready in 1-2 weeks. It > will include usability improvements, better monitoring and a UI. > >> > >> Kind regards, > >> > >> Tim > >> > >> > >> > >>> On 5 Feb 2020, at 16:03, Christopher Munz-Michielin < > christopher(a)ve7alb.ca> wrote: > >>> > >>> Brilliant! Thanks for the write up Cynthia, I'll have a read through! > >>> > >>> Chris > >>> > >>> On 2020-02-05 1:56 a.m., Cynthia Revström wrote: > >>>> (Re-sent as I forgot to include the ML the first time, oops) > >>>> Hi Chris, > >>>> > >>>> I recently figured it out and posted it on the NLNetLabs RPKI mailing > list. https://lists.nlnetlabs.nl/pipermail/rpki/2020-February/000124.html > <https://lists.nlnetlabs.nl/pipermail/rpki/2020-February/000124.html> > >>>> I hope it helps :) > >>>> > >>>> - Cynthia > >>>> > >>>> On Wed, Jan 29, 2020 at 6:31 PM Christopher Munz-Michielin < > christopher(a)ve7alb.ca <mailto:christopher@ve7alb.ca>> wrote: > >>>> > >>>> Hi Nanog, > >>>> > >>>> Posting here since my Google-fu is coming up short. I'm trying to > setup delegated RPKI in ARIN using rpki.net <http://rpki.net>'s rpkid > Python daemon and am running into an issue submitting the identity file to > ARIN's control panel. The same file submitted to RIPE's test environment > at https://localcert.ripe.net/#/rpki works without issue, while > submitting to ARIN results in "Invalid Identity.xml file." > >>>> > >>>> The guide I'm following is this one: > https://github.com/dragonresearch/rpki.net/blob/master/doc/quickstart/xenia… > and I'm able to get as far as generating the identity file. > >>>> > >>>> Wondering if anyone has gone down this road before and has any > helpful hints to make this work? > >>>> > >>>> Cheers, > >>>> Chris > >>>> > >> > > > > > > ------------------------------ > > Message: 2 > Date: Tue, 25 Feb 2020 18:32:02 -0800 > From: Norman Jester <nj(a)jester.mx> > To: nanog(a)nanog.org > Subject: Hi-Rise Building Fiber Suggestions > Message-ID: <44DA61E8-1023-466D-A8A7-8CA6369BBD0C(a)jester.mx> > Content-Type: text/plain; charset=utf-8 > > I’m in the process of choosing hardware > for a 30 story building. If anyone has experience with this I’d appreciate > any tips. > > There are two fiber pairs running up the building riser. I need to put a > POE switch on each floor using this fiber. > > The idea is to cut the fiber at each floor and insert a switch and daisy > chain the switches together using one pair, and using the other pair as the > failover side of the ring going back to the source so if one device fails > it doesn’t take the whole string down. > > The problem here is how many switches can be strung together and I would > not try more than 3 to 5. This is not something I typically do (stacking > switches). I have fears of STP and/or RSTP issue stacking past Ethernet > switch to switch limits (if they still exist??) > > Is there a device with a similar protocol as the old 3com (now HP IDF) > stacking capability via fiber? > > I’d like to use something inexpensive as its to power ubiquiti wifi on > each floor. Ideally if you know something I don’t about ubiquiti switches > that can do this I’d appreciate knowing. > > Norman > > > > ------------------------------ > > Message: 3 > Date: Tue, 25 Feb 2020 23:21:27 -0500 > From: Bradley Burch <bradley(a)wifastnetworks.com> > To: Norman Jester <nj(a)jester.mx> > Cc: nanog(a)nanog.org > Subject: Re: Hi-Rise Building Fiber Suggestions > Message-ID: <4F4AD665-71ED-4423-A591-E737088E014B(a)wifastnetworks.com> > Content-Type: text/plain; charset=utf-8 > > Should consider DWDM or GPON and in those look at passive optical > technologies that can benefit the project. > > > On Feb 25, 2020, at 9:33 PM, Norman Jester <nj(a)jester.mx> wrote: > > > > I’m in the process of choosing hardware > > for a 30 story building. If anyone has experience with this I’d > appreciate any tips. > > > > There are two fiber pairs running up the building riser. I need to put a > POE switch on each floor using this fiber. > > > > The idea is to cut the fiber at each floor and insert a switch and daisy > chain the switches together using one pair, and using the other pair as the > failover side of the ring going back to the source so if one device fails > it doesn’t take the whole string down. > > > > The problem here is how many switches can be strung together and I would > not try more than 3 to 5. This is not something I typically do (stacking > switches). I have fears of STP and/or RSTP issue stacking past Ethernet > switch to switch limits (if they still exist??) > > > > Is there a device with a similar protocol as the old 3com (now HP IDF) > stacking capability via fiber? > > > > I’d like to use something inexpensive as its to power ubiquiti wifi on > each floor. Ideally if you know something I don’t about ubiquiti switches > that can do this I’d appreciate knowing. > > > > Norman > > > > > ------------------------------ > > Message: 4 > Date: Tue, 25 Feb 2020 20:42:04 -0800 > From: Ryan Hamel <ryan(a)rkhtech.org> > To: Norman Jester <nj(a)jester.mx> > Cc: "=?utf-8?Q?nanog=40nanog.org?=" <nanog(a)nanog.org> > Subject: Re: Hi-Rise Building Fiber Suggestions > Message-ID: > <1582691775.local-b755fc33-4b8b-v1.2.1-5f094887(a)getmailspring.com> > Content-Type: text/plain; charset="utf-8" > > I'd say a pair of Juniper switches on each floor, with their > virtual-chassis capability. Terminate the top/bottom floor of fiber 1 into > switch 1, and the other into switch two. Create an LACP bond between each > floors switches, tag the necessary VLANs, and put the VLAN SVIs onto the > first pair of switches at the building electrical/telecom room. > > The same thing can be done with MLAG across many switch vendors, but that > will require additional configuration. > On Feb 25 2020, at 6:32 pm, Norman Jester <nj(a)jester.mx> wrote: > > > > I’m in the process of choosing hardware > > for a 30 story building. If anyone has experience with this I’d > appreciate any tips. > > > > There are two fiber pairs running up the building riser. I need to put a > POE switch on each floor using this fiber. > > The idea is to cut the fiber at each floor and insert a switch and daisy > chain the switches together using one pair, and using the other pair as the > failover side of the ring going back to the source so if one device fails > it doesn’t take the whole string down. > > The problem here is how many switches can be strung together and I would > not try more than 3 to 5. This is not something I typically do (stacking > switches). I have fears of STP and/or RSTP issue stacking past Ethernet > switch to switch limits (if they still exist??) > > Is there a device with a similar protocol as the old 3com (now HP IDF) > stacking capability via fiber? > > I’d like to use something inexpensive as its to power ubiquiti wifi on > each floor. Ideally if you know something I don’t about ubiquiti switches > that can do this I’d appreciate knowing. > > Norman >

1 0

Help with survey on enterprise network challenges? (updated)
by Joseph Severini 25 Feb '20

25 Feb '20

Hi, My name is Joseph Severini, and I am a PhD student in the Computer Science Department at Carnegie Mellon University. I’m working on a research project to identify common operational challenges in modern enterprise computer networks. I’ve put together a survey to identify these challenges by analyzing some operational problems found in the Network Engineering Stack Exchange open-source dataset. You’ll be given a problem from the dataset and asked some questions about it. I would appreciate it if you would consider taking this survey, which can be found at the link below: http://cmu.ca1.qualtrics.com/jfe/form/SV_dm6i9znuPWlLDN3 The survey should take ~15 minutes. Participation is voluntary, with no compensation, and all responses are anonymous. You must be at least 18 years old to complete the survey. I advertised my survey here before, but I wanted to advertise it one final time. I tweaked the question selection algorithm after feedback I received last time (people thought the "pain-points" were not painful enough). If you didn't submit the survey last time, please consider taking it this time. Thanks, Joseph Severini PhD Student CMU Computer Science Department

1 0

Hearing on "Strengthening Communications Networks To Help Americans In Crisis"
by Sean Donelan 25 Feb '20

25 Feb '20

Date: Thursday, February 27, 2020 - 10:30am Location: 2322 Rayburn House Office Building Subcommittees: Communications & Technology (116th Congress) https://energycommerce.house.gov/committee-activity/hearings/hearing-on-str… Legislation H.R. 451, the "Don't Break Up the T-Band Act of 2019" H.R. 1289, the "Preserving Home and Office Numbers in Emergencies Act of 2019" H.R. 3836, the "Wireless Infrastructure Resiliency during Emergencies and Disasters Act" or the "WIRED Act" H.R. 4194, the "National Suicide Hotline Designation Act of 2019" H.R. 4856, the "Reliable Emergency Alert Distribution Improvement Act of 2019" or the "READI Act" H.R. 5918, a bill to direct the Federal Communicatoins Commission to issue reports after activation of the Disaster Information Reporting System and to make improvement to network outage reporting H.R. 5926, the "Reinforcing and Evaluating Service Integrity, Local Infrastructure, and Emergency Notification for Today's Networks Act" or the "RESILIENT Networks Act" H.R. 5928, the "Fee Integrity and Responsibilities and To Regain Essential Spectrum for Public-safety Operators Needed to Deploy Equipment Reliably Act of 2020" or the "FIRST RESPONDER Act of 2020"

1 0

Network configurations survey
by Usama Naseer 24 Feb '20

24 Feb '20

Hi NANOG, We have often read that CDNs/CSPs optimize their networking stack configurations (e.g., TCP, HTTP etc.) to meet their performance/service requirements. Please help us in exploring the configurations used in the wild by filling us this short survey (<10 minutes): CDN network configuration survey <https://forms.gle/vaGNC3gHxps3Esqs9> (https://forms.gle/vaGNC3gHxps3Esqs9) *Background:* There’s a plethora of protocols and configuration options (TCP congestion control, initial congestion windows, HTTP version, HTTP options etc.) available for networking stack to address a variety of realistic network conditions and devices. Content providers mostly hand-tune the network stack configurations to suit the needs of underlying networks and users. We aim to improve the tuning by building a dynamic network stack that delegates the choice of tuning configurations to a data-driven model and uses the optimal set of configurations for individual networks. *Purpose of Survey:* This survey aims to understand the networking configurations used in-the-wild by network operators and the extent of configuration tuning used to curate the networking stack according to the needs of underlying networks. We also aim to understand the rationale that goes behind tuning the stack to a certain configuration. We expect the survey to be filled by anyone involved with content delivery, protocol designing, next-gen protocols or network infrastructure. The survey and collected data are anonymous and the aggregate results will be used as part of a scientific study/NANOG presentation. Thanks in advance and we look forward to your responses. Usama Naseer (usama_naseer(a)brown.edu) PS: We would appreciate if you could forward the email to other operators who might not be a part of NANOG.

1 0

Ubiquiti EdgeRouter Infinity and IS-IS
by Randy Bush 24 Feb '20

24 Feb '20

am i correct that the only option to drop a ubiquiti infinity into an IS-IS LAN and have RPKI-based ROV too is FRR? if so, would someone who has been to the movie care to share some clue off-list? thanks. randy

1 0

TCP-AMP DDoS Attack - Fake abuse reports problem
by Octolus Development 21 Feb '20

21 Feb '20

A very old attack method called TCP-AMP ( https://pastebin.com/jYhWdgHn [https://pastebin.com/jYhWdgHn] ) has been getting really popular recently. I've been a victim of it multiple times on many of my IP's and every time it happens - My IP's end up getting blacklisted in major big databases. We also receive tons of abuse reports for "Port Scanning". Example of the reports we're getting: tcp: 51.81.XX.XX:19342 -> 209.208.XX.XX:80 (SYN_RECV) tcp: 51.81.XX.XX:14066 -> 209.208.XX.XX:80 (SYN_RECV) OVH are threatening to kick us off their network, because we are victims of this attack. And requesting us to do something about it, despite the fact that there is nothing you can do when you are being victim of an DDoS Attack. Anyone else had any problems with these kind of attacks? The attack basically works like this; - The attacker scans the internet for TCP Services, i.e port 80. - The attacker then sends spoofed requests from our IP to these TCP Services, which makes the remote service attempt to connect to us to initiate the handshake.. This clearly fails. ... Which ends up with hundreds of request to these services, reporting us for "port flood".

10 12

NANOG PC Selection
by L Sean Kennedy 21 Feb '20

21 Feb '20

NANOG Community, Thank you for joining us in San Francisco, and online <https://www.youtube.com/playlist?list=PLO8DR5ZGla8jSzWlrWt_cz13LLAz44rHY>, for NANOG 78! I am excited to announce that 13 NANOG members accepted appointments to the Program Committee. 27 highly-qualified volunteers from the NANOG membership were nominated for this year’s committee selection, so we personally thank each NANOG member who offered their time and hope they participate in future committee solicitations. As an organization, NANOG was founded by volunteers who developed a quality forum for North America’s operator community. Despite the growth in NANOG’s programs, volunteers greatly outnumber professional staff, and the volunteer-only Program Committee (PC) is wholly responsible for soliciting, developing, and selecting all program content presented at NANOG meetings and other events. Please join me in congratulating the appointed PC members: Aaron Ali Atac, Jason Bothe, Vincent Celindro, Michael Costello, Elizabeth Culley, Cat Gurinsky, Tom Kacprzynski, John Kristoff, Ognian Mitev, Rekha Rawat, Michael Voity, Eddy Winstead, and Chris Woodfield. Please also join me in thanking and recognizing the many contributions of PC alumni Michaela Clifford, Nagendra Kumar Nainar, Chris Pennisi, and Steven Schecter. The PC met and elected the following leaders: Chair - Vincent Celindro Vice Chair - Steve Feldman Secretary - Cat Gurinsky We are truly excited to see what the community will submit to the PC for NANOG 79 so please submit talk ideas at https://nanog.org/meetings/submit-presentation/. And please join us in June for our first full meeting in Boston if you can! Thanks, Sean (for the NANOG Board of Directors)

1 0

NANOG 78 Webcasts
by Ana Tomasović 21 Feb '20

21 Feb '20

Hi all, Is anyone able to access NANOG 78 playlist on YouTube or the webcast URL? YouTube videos/playlist appear as private. Thank you.

7 8

Weekly Routing Table Report
by cscora＠apnic.net 21 Feb '20

21 Feb '20

This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. The posting is sent to APOPS, NANOG, AfNOG, SANOG, PacNOG, SAFNOG TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG and the RIPE Routing WG. Daily listings are sent to bgp-stats(a)lists.apnic.net For historical data, please see http://thyme.rand.apnic.net. If you have any comments please contact Philip Smith <pfsinoz(a)gmail.com>. Routing Table Report 04:00 +10GMT Sat 22 Feb, 2020 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 797399 Prefixes after maximum aggregation (per Origin AS): 303488 Deaggregation factor: 2.63 Unique aggregates announced (without unneeded subnets): 389804 Total ASes present in the Internet Routing Table: 67104 Prefixes per ASN: 11.88 Origin-only ASes present in the Internet Routing Table: 57658 Origin ASes announcing only one prefix: 24213 Transit ASes present in the Internet Routing Table: 9446 Transit-only ASes present in the Internet Routing Table: 284 Average AS path length visible in the Internet Routing Table: 4.5 Max AS path length visible: 34 Max AS path prepend of ASN (206156) 26 Prefixes from unregistered ASNs in the Routing Table: 1181 Number of instances of unregistered ASNs: 1186 Number of 32-bit ASNs allocated by the RIRs: 30632 Number of 32-bit ASNs visible in the Routing Table: 25219 Prefixes from 32-bit ASNs in the Routing Table: 115818 Number of bogon 32-bit ASNs visible in the Routing Table: 22 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 1138 Number of addresses announced to Internet: 2853607040 Equivalent to 170 /8s, 22 /16s and 150 /24s Percentage of available address space announced: 77.1 Percentage of allocated address space announced: 77.1 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 99.4 Total number of prefixes smaller than registry allocations: 268351 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 210760 Total APNIC prefixes after maximum aggregation: 61530 APNIC Deaggregation factor: 3.43 Prefixes being announced from the APNIC address blocks: 204036 Unique aggregates announced from the APNIC address blocks: 85081 APNIC Region origin ASes present in the Internet Routing Table: 10346 APNIC Prefixes per ASN: 19.72 APNIC Region origin ASes announcing only one prefix: 2847 APNIC Region transit ASes present in the Internet Routing Table: 1552 Average APNIC Region AS path length visible: 4.6 Max APNIC Region AS path length visible: 26 Number of APNIC region 32-bit ASNs visible in the Routing Table: 5410 Number of APNIC addresses announced to Internet: 768263168 Equivalent to 45 /8s, 202 /16s and 196 /24s APNIC AS Blocks 4608-4864, 7467-7722, 9216-10239, 17408-18431 (pre-ERX allocations) 23552-24575, 37888-38911, 45056-46079, 55296-56319, 58368-59391, 63488-64098, 64297-64395, 131072-141625 APNIC Address Blocks 1/8, 14/8, 27/8, 36/8, 39/8, 42/8, 43/8, 49/8, 58/8, 59/8, 60/8, 61/8, 101/8, 103/8, 106/8, 110/8, 111/8, 112/8, 113/8, 114/8, 115/8, 116/8, 117/8, 118/8, 119/8, 120/8, 121/8, 122/8, 123/8, 124/8, 125/8, 126/8, 133/8, 150/8, 153/8, 163/8, 171/8, 175/8, 180/8, 182/8, 183/8, 202/8, 203/8, 210/8, 211/8, 218/8, 219/8, 220/8, 221/8, 222/8, 223/8, ARIN Region Analysis Summary ---------------------------- Prefixes being announced by ARIN Region ASes: 234530 Total ARIN prefixes after maximum aggregation: 107780 ARIN Deaggregation factor: 2.18 Prefixes being announced from the ARIN address blocks: 232216 Unique aggregates announced from the ARIN address blocks: 117409 ARIN Region origin ASes present in the Internet Routing Table: 18404 ARIN Prefixes per ASN: 12.62 ARIN Region origin ASes announcing only one prefix: 6749 ARIN Region transit ASes present in the Internet Routing Table: 1908 Average ARIN Region AS path length visible: 3.9 Max ARIN Region AS path length visible: 23 Number of ARIN region 32-bit ASNs visible in the Routing Table: 3170 Number of ARIN addresses announced to Internet: 1079096832 Equivalent to 64 /8s, 81 /16s and 182 /24s ARIN AS Blocks 1-1876, 1902-2042, 2044-2046, 2048-2106 (pre-ERX allocations) 2138-2584, 2615-2772, 2823-2829, 2880-3153 3354-4607, 4865-5119, 5632-6655, 6912-7466 7723-8191, 10240-12287, 13312-15359, 16384-17407 18432-20479, 21504-23551, 25600-26591, 26624-27647, 29696-30719, 31744-33791 35840-36863, 39936-40959, 46080-47103 53248-55295, 62464-63487, 64198-64296, 393216-399260 ARIN Address Blocks 3/8, 4/8, 6/8, 7/8, 8/8, 9/8, 11/8, 12/8, 13/8, 15/8, 16/8, 17/8, 18/8, 19/8, 20/8, 21/8, 22/8, 23/8, 24/8, 26/8, 28/8, 29/8, 30/8, 32/8, 33/8, 34/8, 35/8, 38/8, 40/8, 44/8, 47/8, 48/8, 50/8, 52/8, 53/8, 54/8, 55/8, 56/8, 57/8, 63/8, 64/8, 65/8, 66/8, 67/8, 68/8, 69/8, 70/8, 71/8, 72/8, 73/8, 74/8, 75/8, 76/8, 96/8, 97/8, 98/8, 99/8, 100/8, 104/8, 107/8, 108/8, 128/8, 129/8, 130/8, 131/8, 132/8, 134/8, 135/8, 136/8, 137/8, 138/8, 139/8, 140/8, 142/8, 143/8, 144/8, 146/8, 147/8, 148/8, 149/8, 152/8, 155/8, 156/8, 157/8, 158/8, 159/8, 160/8, 161/8, 162/8, 164/8, 165/8, 166/8, 167/8, 168/8, 169/8, 170/8, 172/8, 173/8, 174/8, 184/8, 192/8, 198/8, 199/8, 204/8, 205/8, 206/8, 207/8, 208/8, 209/8, 214/8, 215/8, 216/8, RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 225915 Total RIPE prefixes after maximum aggregation: 104821 RIPE Deaggregation factor: 2.16 Prefixes being announced from the RIPE address blocks: 222578 Unique aggregates announced from the RIPE address blocks: 130789 RIPE Region origin ASes present in the Internet Routing Table: 26853 RIPE Prefixes per ASN: 8.29 RIPE Region origin ASes announcing only one prefix: 11719 RIPE Region transit ASes present in the Internet Routing Table: 3812 Average RIPE Region AS path length visible: 4.5 Max RIPE Region AS path length visible: 34 Number of RIPE region 32-bit ASNs visible in the Routing Table: 8937 Number of RIPE addresses announced to Internet: 723959424 Equivalent to 43 /8s, 38 /16s and 190 /24s RIPE AS Blocks 1877-1901, 2043, 2047, 2107-2136, 2585-2614 (pre-ERX allocations) 2773-2822, 2830-2879, 3154-3353, 5377-5631 6656-6911, 8192-9215, 12288-13311, 15360-16383 20480-21503, 24576-25599, 28672-29695 30720-31743, 33792-35839, 38912-39935 40960-45055, 47104-52223, 56320-58367 59392-61439, 61952-62463, 64396-64495 196608-210331 RIPE Address Blocks 2/8, 5/8, 25/8, 31/8, 37/8, 46/8, 51/8, 62/8, 77/8, 78/8, 79/8, 80/8, 81/8, 82/8, 83/8, 84/8, 85/8, 86/8, 87/8, 88/8, 89/8, 90/8, 91/8, 92/8, 93/8, 94/8, 95/8, 109/8, 141/8, 145/8, 151/8, 176/8, 178/8, 185/8, 188/8, 193/8, 194/8, 195/8, 212/8, 213/8, 217/8, LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 103345 Total LACNIC prefixes after maximum aggregation: 24123 LACNIC Deaggregation factor: 4.28 Prefixes being announced from the LACNIC address blocks: 104610 Unique aggregates announced from the LACNIC address blocks: 45591 LACNIC Region origin ASes present in the Internet Routing Table: 9467 LACNIC Prefixes per ASN: 11.05 LACNIC Region origin ASes announcing only one prefix: 2412 LACNIC Region transit ASes present in the Internet Routing Table: 1770 Average LACNIC Region AS path length visible: 5.3 Max LACNIC Region AS path length visible: 31 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 7037 Number of LACNIC addresses announced to Internet: 173986048 Equivalent to 10 /8s, 94 /16s and 209 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-270748 + ERX transfers LACNIC Address Blocks 177/8, 179/8, 181/8, 186/8, 187/8, 189/8, 190/8, 191/8, 200/8, 201/8, AfriNIC Region Analysis Summary ------------------------------- Prefixes being announced by AfriNIC Region ASes: 21667 Total AfriNIC prefixes after maximum aggregation: 4490 AfriNIC Deaggregation factor: 4.83 Prefixes being announced from the AfriNIC address blocks: 32821 Unique aggregates announced from the AfriNIC address blocks: 9930 AfriNIC Region origin ASes present in the Internet Routing Table: 1372 AfriNIC Prefixes per ASN: 23.92 AfriNIC Region origin ASes announcing only one prefix: 486 AfriNIC Region transit ASes present in the Internet Routing Table: 264 Average AfriNIC Region AS path length visible: 5.0 Max AfriNIC Region AS path length visible: 21 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 665 Number of AfriNIC addresses announced to Internet: 107623168 Equivalent to 6 /8s, 106 /16s and 51 /24s AfriNIC AS Blocks 36864-37887, 327680-328703 & ERX transfers AfriNIC Address Blocks 41/8, 45/8, 102/8, 105/8, 154/8, 196/8, 197/8, APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 7545 5298 663 617 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4623 4192 73 ERX-CERNET-BKB China Education and Rese 7552 3329 1331 24 VIETEL-AS-AP Viettel Group, VN 45899 3131 1794 110 VNPT-AS-VN VNPT Corp, VN 7713 2702 831 493 TELKOMNET-AS-AP PT Telekomunikasi Indon 9808 2620 9043 62 CMNET-GD Guangdong Mobile Communication 4766 2285 11102 561 KIXS-AS-KR Korea Telecom, KR 9498 2241 433 219 BBIL-AP BHARTI Airtel Ltd., IN 4755 2138 441 193 TATACOMM-AS TATA Communications formerl 9394 2077 4898 24 CTTNET China TieTong Telecommunications Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 7155 4040 280 28 VIASAT-SP-BACKBONE, US 11492 3999 266 655 CABLEONE, US 16509 3853 7815 1701 AMAZON-02, US 22773 3532 2971 151 ASN-CXA-ALL-CCI-22773-RDC, US 6327 3384 1324 92 SHAW, CA 16625 2988 1569 2139 AKAMAI-AS, US 209 2384 5076 533 CENTURYLINK-US-LEGACY-QWEST, US 30036 2310 360 95 MEDIACOM-ENTERPRISE-BUSINESS, US 5650 2290 2941 1631 FRONTIER-FRTR, US 20115 2143 2795 520 CHARTER-20115, US Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 12479 5920 1599 131 UNI2-AS, ES 31334 3961 484 13 KABELDEUTSCHLAND-AS, DE 39891 3776 203 20 ALJAWWALSTC-AS, SA 8551 3287 379 45 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 20940 2885 462 1981 AKAMAI-ASN1, US 12389 2480 2248 731 ROSTELECOM-AS, RU 34984 2075 349 561 TELLCOM-AS, TR 9009 2057 218 1096 M247, GB 9121 1916 1691 18 TTNET, TR 13188 1604 100 47 TRIOLAN, UA Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 6249 3299 598 Uninet S.A. de C.V., MX 10620 3364 534 443 Telmex Colombia S.A., CO 11830 2672 369 63 Instituto Costarricense de Electricidad 6503 1672 323 389 Axtel, S.A.B. de C.V., MX 7303 1557 1030 265 Telecom Argentina S.A., AR 28573 1328 2229 189 CLARO S.A., BR 13999 1223 497 288 Mega Cable, S.A. de C.V., MX 6147 1127 379 39 Telefonica del Peru S.A.A., PE 3816 1103 563 137 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 11172 955 112 69 Alestra, S. de R.L. de C.V., MX Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24863 1239 393 22 LINKdotNET-AS, EG 24835 1099 566 24 RAYA-AS, EG 36992 1045 1535 74 ETISALAT-MISR, EG 36903 876 452 97 MT-MPLS, MA 6713 601 1863 34 IAM-AS, MA 29571 557 68 11 ORANGE-COTE-IVOIRE, CI 37342 482 32 1 MOVITEL, MZ 36935 386 522 40 Vodafone-, EG 15399 373 45 10 WANANCHI-, KE 23889 373 231 15 MauritiusTelecom, MU Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 6249 3299 598 Uninet S.A. de C.V., MX 12479 5920 1599 131 UNI2-AS, ES 7545 5298 663 617 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4623 4192 73 ERX-CERNET-BKB China Education and Rese 7155 4040 280 28 VIASAT-SP-BACKBONE, US 11492 3999 266 655 CABLEONE, US 31334 3961 484 13 KABELDEUTSCHLAND-AS, DE 16509 3853 7815 1701 AMAZON-02, US 39891 3776 203 20 ALJAWWALSTC-AS, SA 22773 3532 2971 151 ASN-CXA-ALL-CCI-22773-RDC, US Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 12479 5920 5789 UNI2-AS, ES 7545 5298 4681 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4623 4550 ERX-CERNET-BKB China Education and Research Net 7155 4040 4012 VIASAT-SP-BACKBONE, US 31334 3961 3948 KABELDEUTSCHLAND-AS, DE 39891 3776 3756 ALJAWWALSTC-AS, SA 22773 3532 3381 ASN-CXA-ALL-CCI-22773-RDC, US 11492 3999 3344 CABLEONE, US 7552 3329 3305 VIETEL-AS-AP Viettel Group, VN 6327 3384 3292 SHAW, CA Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Net Originated Transit AS Transit AS Name 62828 UNALLOCATED 8.21.130.0/24 3356 LEVEL3, US 393266 UNALLOCATED 8.23.52.0/24 174 COGENT-174, US 62485 UNALLOCATED 8.23.229.0/24 3356 LEVEL3, US 32985 UNALLOCATED 8.28.31.0/24 3356 LEVEL3, US 394936 UNALLOCATED 8.33.224.0/24 174 COGENT-174, US 27205 UNALLOCATED 8.38.16.0/21 6461 ZAYO-6461, US 27205 UNALLOCATED 8.38.16.0/22 32787 PROLEXIC-TECHNOLOGIES-DDOS-M 27205 UNALLOCATED 8.38.20.0/22 32787 PROLEXIC-TECHNOLOGIES-DDOS-M 14109 UNALLOCATED 8.38.252.0/24 3356 LEVEL3, US 23061 UNALLOCATED 8.39.119.0/24 3356 LEVEL3, US Complete listing at http://thyme.rand.apnic.net/current/data-badAS Prefixes from private and non-routed address space (Global) ----------------------------------------------------------- Prefix Origin AS Description 192.88.99.0/24 6939 HURRICANE, US Complete listing at http://thyme.rand.apnic.net/current/data-dsua Advertised Unallocated Addresses -------------------------------- Unassigned Network ASN Information AS Name 23.136.224.0/24 Origin: 15206 UNASSIGNED Transit: 174 COGENT-174, US 23.137.192.0/24 Origin: 31798 CANAD-86-31798, CA Transit: 174 COGENT-174, US 27.100.7.0/24 Origin: 56096 UNASSIGNED Transit: 45455 TH-2S1N-AP Two S One N Co Ltd, Internet 27.126.156.0/22 Origin: 55827 UNASSIGNED Transit: 9930 TTNET-MY TIME dotCom Berhad, MY 27.126.156.0/23 Origin: 55827 UNASSIGNED Transit: 9930 TTNET-MY TIME dotCom Berhad, MY Complete listing at http://thyme.rand.apnic.net/current/data-add-IANA Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:10 /9:11 /10:38 /11:98 /12:285 /13:579 /14:1158 /15:1915 /16:13395 /17:8149 /18:13830 /19:25775 /20:40476 /21:47588 /22:98605 /23:81428 /24:462765 /25:1294 /26:0 /27:0 /28:0 /29:0 /30:0 /31:0 /32:0 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 12479 4901 5920 UNI2-AS, ES 31334 3806 3961 KABELDEUTSCHLAND-AS, DE 6327 3173 3384 SHAW, CA 7155 3131 4040 VIASAT-SP-BACKBONE, US 11492 3129 3999 CABLEONE, US 39891 2946 3776 ALJAWWALSTC-AS, SA 8551 2747 3287 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 22773 2747 3532 ASN-CXA-ALL-CCI-22773-RDC, US 8151 2063 6249 Uninet S.A. de C.V., MX 30036 2058 2310 MEDIACOM-ENTERPRISE-BUSINESS, US Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1530 2:1150 3:30 4:19 5:3308 6:48 8:1379 9:1 12:1783 13:494 14:2227 15:74 16:9 17:285 18:79 20:58 23:3340 24:2641 25:4 27:2497 31:2925 32:102 35:41 36:929 37:3255 38:1846 39:320 40:132 41:3326 42:875 43:2107 44:196 45:13518 46:3661 47:277 49:1418 50:1580 51:87 52:1123 54:272 55:693 56:6 57:48 58:1884 59:1126 60:685 61:2203 62:2166 63:1945 64:5062 65:2313 66:4860 67:2862 68:1212 69:3801 70:1431 71:669 72:2773 74:2623 75:1436 76:676 77:2565 78:1975 79:2418 80:1858 81:1564 82:1205 83:1118 84:1227 85:2494 86:567 87:1714 88:1084 89:2696 90:324 91:7553 92:1492 93:2445 94:2616 95:3733 96:1013 97:337 98:966 99:963 100:85 101:1086 102:843 103:23148 104:3607 105:387 106:833 107:1946 108:703 109:3774 110:1781 111:1983 112:1576 113:1383 114:1491 115:1844 116:1790 117:2048 118:2122 119:1701 120:848 121:1037 122:2366 123:1887 124:1556 125:2032 128:1387 129:914 130:620 131:1823 132:760 133:300 134:1229 135:276 136:601 137:839 138:2176 139:988 140:594 141:878 142:878 143:1170 144:949 145:327 146:1479 147:1007 148:2051 149:1123 150:812 151:1281 152:1476 153:369 154:4747 155:896 156:3325 157:1082 158:760 159:1939 160:1736 161:990 162:3030 163:789 164:1433 165:1241 166:546 167:1486 168:3620 169:494 170:4232 171:742 172:1881 173:2380 174:1036 175:1012 176:2642 177:4157 178:3009 179:1465 180:2193 181:2442 182:2839 183:1111 184:2397 185:16120 186:3742 187:2569 188:4068 189:2114 190:8257 191:1513 192:10262 193:7371 194:6034 195:4303 196:3398 197:1864 198:6148 199:5928 200:7122 201:5119 202:10399 203:10133 204:4548 205:3075 206:3260 207:3293 208:4001 209:4378 210:4001 211:1988 212:3210 213:3015 214:1168 215:54 216:5958 217:2353 218:880 219:604 220:1977 221:913 222:1004 223:1458 End of report

1 0

MDXi / Lagos
by Chris Knipe 21 Feb '20

21 Feb '20

Hi Guys, Sorry for the off-topic post. I would appreciate it if someone that has rack space in MDXi can please ping me off list. I just have a few (two or three) random questions that I would appreciate some general feedback on. Many thanks, -- Regards, Chris Knipe

1 0