- NANOG - lists.nanog.org

Court orders for blocking of streaming services
by Joe Greco 09 May '22

09 May '22

Greetings - Recently, a court issued a troubling set of rulings in a default decision against "Israel.TV" and some other sites. https://storage.courtlistener.com/recap/gov.uscourts.nysd.572373/gov.uscour… https://storage.courtlistener.com/recap/gov.uscourts.nysd.572374/gov.uscour… https://storage.courtlistener.com/recap/gov.uscourts.nysd.572375/gov.uscour… While the issue of domains being confiscated and being handed over to a prevailing plaintiff for an international domain with no obvious nexus to the United States by a United States court via orders to companies that happen to be in the United States is a bit of a concerning issue, that's not operationally relevant. What's more concerning is that the ruling includes an expansive clause B, "Against Internet Service Providers (ISPs):" IT IS FURTHER ORDERED that all ISPs (including without limitation those set forth in Exhibit B hereto) and any other ISPs providing services in the United States shall block access to the Website at any domain address known today (including but not limited to those set forth in Exhibit A hereto) or to be used in the future by the Defendants (.Newly-Detected Websites.) by any technological means available on the ISPs. systems. The domain addresses and any NewlyDetected Websites shall be channeled in such a way that users will be unable to connect and/or use the Website, and will be diverted by the ISPs. DNS servers to a landing page operated and controlled by Plaintiffs (the .Landing Page.) which can be reached as follows: This expansive clause basically demands that ISP's implement a DNS override in recursers, which may be dubiously effective given things such as DNSSEC and DNS-over-HTTPS complications. This is not an insignificant amount of work to implement, and since they have not limited the list to big players, that means us small guys would need to do this too. Perhaps more worryingly is the clause "by any technological means available," which seems like it could be opening the door to mandatory DPI filtering of port 53 traffic, an expensive and dicey proposition, or filtering at the CPE for those who run dnsmasq on busybox based CPE, etc., etc. This seems to be transferring the expense of complying to third parties who had nothing to do with the pirate sites. Complying with random court orders where there isn't even a formal notice that there's been a court order is problematic. I would guess that the 96 ISP's listed in the order are going to receive a formal notice, but by what mechanism does the court think that a small service provider would even be aware of such an order? What happens with respect to the "Newly Detected Websites"? What mechanism exists here? Who is going to pay for the costs? And how is this practical when this scales to hundreds or thousands of such rulings? It seems to me like the court overstepped here and issued a ruling that contained a lot of wishful thinking that doesn't reflect the ability of miscreants on the Internet to just rapidly register a new domain name with a new fake credit card. Certainly it is trivial to host the actual websites well out of legal reach of US courts, and with domain registrars without US presence. This leaves those of us in the network operations community in the position of shouldering costs to comply with a court order, but without a clear mechanism to continue to be in compliance. This could become a full time job, if the defendants want to play the game right. "israel.tv"? "1srael.tv" (with a "1" or "L" for the first letter, etc). Is anybody here considering recovering compliance costs from the plaintiffs? ... JG -- Joe Greco - sol.net Network Services - Milwaukee, WI - http://www.sol.net "The strain of anti-intellectualism has been a constant thread winding its way through our political and cultural life, nurtured by the false notion that democracy means that 'my ignorance is just as good as your knowledge.'"-Asimov

10 17

Re: 10 Do's + Don'ts for Visiting Québec + Register Now for N85!
by Mel Beckman 08 May '22

08 May '22

I’m a Minnesotan, the land of Powder Milk Biscuits, and thus an honorary Canadian. I can attest that poutine is indeed wonderful, and I would say essential to withstand the viciously cold northern winters. It originated in Quebec, and is still very popular there, and also throughout Canada. Importantly, poutine is a critical infrastructure component for network administrators. I would go so far as to say that it is the only food that can serve all North American Network Operators as universal sustenance. https://www.britannica.com/topic/poutine “It has become a symbol of Québécois and Canadian cuisine and culture.” -mel On May 8, 2022, at 7:31 AM, Laura Smith via NANOG <nanog(a)nanog.org> wrote: ------- Original Message ------- On Friday, May 6th, 2022 at 13:59, J EMail <70ford500(a)gmail.com> wrote: poutine should be on this list. God no ! There are many great things about Canada and Québec .... but poutine most certainly is not. A culinary abomination that deserves to be confined to the history books.

2 1

Spoofer Report for NANOG for Apr 2022
by CAIDA Spoofer Project 08 May '22

08 May '22

In response to feedback from operational security communities, CAIDA's source address validation measurement project (https://spoofer.caida.org) is automatically generating monthly reports of ASes originating prefixes in BGP for systems from which we received packets with a spoofed source address. We are publishing these reports to network and security operations lists in order to ensure this information reaches operational contacts in these ASes. This report summarises tests conducted within usa, can. Inferred improvements during Apr 2022: ASN Name Fixed-By 32035 CCDT 2022-04-11 7018 ATT-INTERNET4 2022-04-22 Further information for the inferred remediation is available at: https://spoofer.caida.org/remedy.php Source Address Validation issues inferred during Apr 2022: ASN Name First-Spoofed Last-Spoofed 54825 PACKET 2016-04-15 2022-04-30 209 CENTURYLINK-US-LEGACY-QWEST 2016-08-16 2022-04-29 6128 CABLE-NET-1 2016-09-03 2022-04-24 20412 CLARITY-TELECOM 2016-09-30 2022-04-30 6181 FUSE-NET 2016-10-10 2022-04-17 271 BCNET 2016-10-24 2022-04-27 30036 MEDIACOM-ENTERPRISE-BUSINESS 2016-11-16 2022-04-18 22898 ATLINK 2016-12-16 2022-04-27 1246 TLL-WEST 2017-04-20 2022-04-29 63296 AWBROADBAND 2017-09-01 2022-04-19 62240 Clouvider 2017-10-20 2022-04-19 33452 RW 2018-09-19 2022-04-18 21804 ACCESS-SK 2019-06-09 2022-04-30 5078 ONENET-AS-1 2020-04-06 2022-04-14 398836 NP-NETWORKS 2021-03-12 2022-04-30 56207 Converge 2021-03-26 2022-04-22 22191 WILKES-COMM 2021-06-25 2022-04-28 63457 EMPIRE-CONNECT 2021-09-08 2022-04-14 212934 AS_POTVIN 2021-10-03 2022-04-19 22773 ASN-CXA-ALL-CCI-22773-RDC 2021-10-24 2022-04-30 399065 DEFASTLINK 2022-03-12 2022-04-24 47027 SEASIDE-COMM 2022-03-22 2022-04-18 14315 1GSERVERS 2022-04-12 2022-04-12 396097 SAIL-INET 2022-04-22 2022-04-22 Further information for these tests where we received spoofed packets is available at: https://spoofer.caida.org/recent_tests.php?country_include=usa,can&no_block… Please send any feedback or suggestions to spoofer-info(a)caida.org

1 0

Announcement of Experiments
by Alexandros Milolidakis 07 May '22

07 May '22

Hi NANOG, We are a group of researchers from the KTH Royal Institute of Technology (Sweden). Starting from May 9 until May 31, we plan to conduct a research study involving AS-PATH poisoning to measure how reliable route collectors are to report BGP poisoned routes. We will use the PEERING Testbed [1] to announce the following two prefixes: - 184.164.236.0/24 - 184.164.237.0/24 for our AS-path poisoning experiments. The above experimental prefixes do not host any production services, hence user traffic will *not* be affected. Furthermore, we will always start the AS-PATH with the correct ASN as the origin. Lastly, to keep the AS-PATH short, we will announce no more than four Poisoned ASNs per announcement. The frequency of the announcements will not exceed four per hour. If, for any reason, you want to opt out from us using your ASN for our experiments, you can do so in the following form before May 9: https://forms.gle/ZvZaodndPhCqMvR89 I remain at your disposal for any questions. Best regards, Alexandros [1] https://peering.ee.columbia.edu/

13 17

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 06 May '22

06 May '22

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 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 https://thyme.apnic.net. If you have any comments please contact Philip Smith <pfsinoz(a)gmail.com>. IPv4 Routing Table Report 04:00 +10GMT Sat 07 May, 2022 BGP Table (Global) as seen in Japan. Report Website: https://thyme.apnic.net Detailed Analysis: https://thyme.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 897482 Prefixes after maximum aggregation (per Origin AS): 337711 Deaggregation factor: 2.66 Unique aggregates announced (without unneeded subnets): 430691 Total ASes present in the Internet Routing Table: 73091 Prefixes per ASN: 12.28 Origin-only ASes present in the Internet Routing Table: 62741 Origin ASes announcing only one prefix: 25750 Transit ASes present in the Internet Routing Table: 10350 Transit-only ASes present in the Internet Routing Table: 367 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 66 Max AS path prepend of ASN (267602) 58 Prefixes from unregistered ASNs in the Routing Table: 854 Number of instances of unregistered ASNs: 861 Number of 32-bit ASNs allocated by the RIRs: 39312 Number of 32-bit ASNs visible in the Routing Table: 32591 Prefixes from 32-bit ASNs in the Routing Table: 153631 Number of bogon 32-bit ASNs visible in the Routing Table: 23 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 482 Number of addresses announced to Internet: 3067538816 Equivalent to 182 /8s, 214 /16s and 237 /24s Percentage of available address space announced: 82.9 Percentage of allocated address space announced: 82.9 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 99.6 Total number of prefixes smaller than registry allocations: 304613 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 235349 Total APNIC prefixes after maximum aggregation: 66645 APNIC Deaggregation factor: 3.53 Prefixes being announced from the APNIC address blocks: 230358 Unique aggregates announced from the APNIC address blocks: 94786 APNIC Region origin ASes present in the Internet Routing Table: 12607 APNIC Prefixes per ASN: 18.27 APNIC Region origin ASes announcing only one prefix: 3589 APNIC Region transit ASes present in the Internet Routing Table: 1729 Average APNIC Region AS path length visible: 4.7 Max APNIC Region AS path length visible: 32 Number of APNIC region 32-bit ASNs visible in the Routing Table: 7806 Number of APNIC addresses announced to Internet: 774069504 Equivalent to 46 /8s, 35 /16s and 93 /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-151865 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: 261514 Total ARIN prefixes after maximum aggregation: 119897 ARIN Deaggregation factor: 2.18 Prefixes being announced from the ARIN address blocks: 261402 Unique aggregates announced from the ARIN address blocks: 124878 ARIN Region origin ASes present in the Internet Routing Table: 19015 ARIN Prefixes per ASN: 13.75 ARIN Region origin ASes announcing only one prefix: 6898 ARIN Region transit ASes present in the Internet Routing Table: 1942 Average ARIN Region AS path length visible: 3.8 Max ARIN Region AS path length visible: 35 Number of ARIN region 32-bit ASNs visible in the Routing Table: 4476 Number of ARIN addresses announced to Internet: 1295461632 Equivalent to 77 /8s, 55 /16s and 45 /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-401308 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: 257121 Total RIPE prefixes after maximum aggregation: 117453 RIPE Deaggregation factor: 2.19 Prefixes being announced from the RIPE address blocks: 254519 Unique aggregates announced from the RIPE address blocks: 150317 RIPE Region origin ASes present in the Internet Routing Table: 28130 RIPE Prefixes per ASN: 9.05 RIPE Region origin ASes announcing only one prefix: 12047 RIPE Region transit ASes present in the Internet Routing Table: 3975 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 33 Number of RIPE region 32-bit ASNs visible in the Routing Table: 10688 Number of RIPE addresses announced to Internet: 713885056 Equivalent to 42 /8s, 141 /16s and 5 /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-213403 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: 114893 Total LACNIC prefixes after maximum aggregation: 27612 LACNIC Deaggregation factor: 4.16 Prefixes being announced from the LACNIC address blocks: 114718 Unique aggregates announced from the LACNIC address blocks: 48579 LACNIC Region origin ASes present in the Internet Routing Table: 10968 LACNIC Prefixes per ASN: 10.46 LACNIC Region origin ASes announcing only one prefix: 2654 LACNIC Region transit ASes present in the Internet Routing Table: 2201 Average LACNIC Region AS path length visible: 4.9 Max LACNIC Region AS path length visible: 66 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 8662 Number of LACNIC addresses announced to Internet: 176484096 Equivalent to 10 /8s, 132 /16s and 239 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-273820 + 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: 27751 Total AfriNIC prefixes after maximum aggregation: 5437 AfriNIC Deaggregation factor: 5.10 Prefixes being announced from the AfriNIC address blocks: 36003 Unique aggregates announced from the AfriNIC address blocks: 11713 AfriNIC Region origin ASes present in the Internet Routing Table: 1630 AfriNIC Prefixes per ASN: 22.09 AfriNIC Region origin ASes announcing only one prefix: 562 AfriNIC Region transit ASes present in the Internet Routing Table: 326 Average AfriNIC Region AS path length visible: 5.1 Max AfriNIC Region AS path length visible: 36 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 959 Number of AfriNIC addresses announced to Internet: 107366400 Equivalent to 6 /8s, 102 /16s and 72 /24s AfriNIC AS Blocks 36864-37887, 327680-329727 & 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 9808 9141 8884 44 CHINAMOBILE-CN China Mobile Communicati 7545 5922 789 697 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4710 4192 75 ERX-CERNET-BKB China Education and Rese 7552 3592 1330 19 VIETEL-AS-AP Viettel Group, VN 7713 3494 1039 53 TELKOMNET-AS-AP PT Telekomunikasi Indon 45899 3431 1880 56 VNPT-AS-VN VNPT Corp, VN 4766 2495 11121 601 KIXS-AS-KR Korea Telecom, KR 9498 2403 499 239 BBIL-AP BHARTI Airtel Ltd., IN 45090 2169 1438 79 TENCENT-NET-AP Shenzhen Tencent Compute 4755 2119 438 201 TATACOMM-AS TATA Communications formerl Complete listing at https://thyme.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 16509 6340 10279 2727 AMAZON-02, US 11492 4476 297 694 CABLEONE, US 22773 3934 3075 361 ASN-CXA-ALL-CCI-22773-RDC, US 7155 3901 264 31 VIASAT-SP-BACKBONE, US 16625 3596 1837 2540 AKAMAI-AS, US 6327 3437 1318 62 SHAW, CA 749 2882 50780 2138 DNIC-AS-00749, US 30036 2623 374 130 MEDIACOM-ENTERPRISE-BUSINESS, US 209 2515 4962 424 CENTURYLINK-US-LEGACY-QWEST, US 20115 2251 3051 492 CHARTER-20115, US Complete listing at https://thyme.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 12479 6767 1730 150 UNI2-AS, ES 9121 6715 1692 17 TTNET, TR 8551 4008 374 39 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 20940 3939 3360 201 AKAMAI-ASN1, NL 39891 3819 220 34 ALJAWWALSTC-AS, SA 12389 2948 2273 909 ROSTELECOM-AS, RU 6849 2907 355 21 UKRTELNET, UA 9009 2493 249 1296 M247, GB 34984 2239 358 633 TELLCOM-AS, TR 47331 2086 328 1598 TTNET, TR Complete listing at https://thyme.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 10580 3394 561 Uninet S.A. de C.V., MX 10620 3475 519 738 Telmex Colombia S.A., CO 11830 2433 369 63 Instituto Costarricense de Electricidad 13999 1782 298 469 Mega Cable, S.A. de C.V., MX 6503 1456 355 525 Axtel, S.A.B. de C.V., MX 28573 1401 2333 253 CLARO S.A., BR 3816 1256 669 148 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6147 1080 369 21 Telefonica del Peru S.A.A., PE 11664 1014 191 443 Techtel LMDS Comunicaciones Interactiva 11172 961 133 63 Alestra, S. de R.L. de C.V., MX Complete listing at https://thyme.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24863 1653 393 21 LINKdotNET-AS, EG 24835 1442 501 30 RAYA-AS, EG 36992 1314 1519 263 ETISALAT-MISR, EG 36903 1199 545 114 MT-MPLS, MA 29571 928 65 59 ORANGE-COTE-IVOIRE, CI 36935 619 520 42 Vodafone-, EG 6713 612 1863 34 IAM-AS, MA 15399 512 51 33 WANANCHI-, KE 37342 467 32 1 MOVITEL, MZ 23889 423 232 16 MauritiusTelecom, MU Complete listing at https://thyme.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 10580 3394 561 Uninet S.A. de C.V., MX 9808 9141 8884 44 CHINAMOBILE-CN China Mobile Communicati 12479 6767 1730 150 UNI2-AS, ES 9121 6715 1692 17 TTNET, TR 16509 6340 10279 2727 AMAZON-02, US 7545 5922 789 697 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4710 4192 75 ERX-CERNET-BKB China Education and Rese 11492 4476 297 694 CABLEONE, US 8551 4008 374 39 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 20940 3939 3360 201 AKAMAI-ASN1, NL Complete listing at https://thyme.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 9808 9141 9097 CHINAMOBILE-CN China Mobile Communications Grou 9121 6715 6698 TTNET, TR 12479 6767 6617 UNI2-AS, ES 7545 5922 5225 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4710 4635 ERX-CERNET-BKB China Education and Research Net 8551 4008 3969 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 7155 3901 3870 VIASAT-SP-BACKBONE, US 39891 3819 3785 ALJAWWALSTC-AS, SA 11492 4476 3782 CABLEONE, US 20940 3939 3738 AKAMAI-ASN1, NL Complete listing at https://thyme.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Net Originated Transit AS Transit AS Name 398083 UNALLOCATED 5.133.124.0/24 399587 UT, US 33123 UNALLOCATED 8.10.69.0/24 11168 SCC, US 62828 UNALLOCATED 8.21.130.0/24 3356 LEVEL3, US 393266 UNALLOCATED 8.23.52.0/24 46887 LIGHTOWER, US 18604 UNALLOCATED 8.25.204.0/24 3356 LEVEL3, US 394936 UNALLOCATED 8.33.224.0/24 22442 HOU-PHONOSCOPE, US 54338 UNALLOCATED 8.33.241.0/24 6461 ZAYO-6461, US 395438 UNALLOCATED 8.42.206.0/24 3356 LEVEL3, US 395056 UNALLOCATED 8.45.133.0/24 3356 LEVEL3, US 32306 UNALLOCATED 8.46.80.0/24 33652 CMCS, US Complete listing at https://thyme.apnic.net/current/data-badAS Prefixes from the Special Purpose Address Registry (Global) ----------------------------------------------------------- Prefix Origin AS Description 192.88.99.0/24 6939 HURRICANE, US Complete listing at https://thyme.apnic.net/current/data-spar Advertised Unallocated Addresses -------------------------------- Unassigned Network ASN Information AS Name 23.141.0.0/24 Origin: 395350 UNASSIGNED 23.141.0.0/24 Transit: 11426 TWC-11426-CAROLINAS, US 27.100.7.0/24 Origin: 56096 UNASSIGNED 27.100.7.0/24 Transit: 45455 TH-2S1N-AP Two S One N Co Ltd, Internet 41.57.124.0/22 Origin: 37442 UNASSIGNED 41.57.124.0/22 Transit: 37204 TELONE, ZW 41.57.124.0/23 Origin: 37442 UNASSIGNED 41.57.124.0/23 Transit: 37204 TELONE, ZW 41.57.124.0/24 Origin: 37442 UNASSIGNED 41.57.124.0/24 Transit: 37204 TELONE, ZW Complete listing at https://thyme.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:16 /9:13 /10:41 /11:100 /12:303 /13:591 /14:1212 /15:2065 /16:13550 /17:8313 /18:13908 /19:25196 /20:43781 /21:52215 /22:108367 /23:95963 /24:531046 /25:802 /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 9121 5871 6715 TTNET, TR 12479 5748 6767 UNI2-AS, ES 8151 4296 10580 Uninet S.A. de C.V., MX 8551 3474 4008 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 11492 3382 4476 CABLEONE, US 6327 3249 3437 SHAW, CA 39891 3131 3819 ALJAWWALSTC-AS, SA 7155 2991 3901 VIASAT-SP-BACKBONE, US 22773 2936 3934 ASN-CXA-ALL-CCI-22773-RDC, US 6849 2758 2907 UKRTELNET, UA Complete listing at https://thyme.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1941 2:1033 3:154 4:6 5:3786 6:103 7:5 8:1566 9:1 11:172 12:1708 13:298 14:2386 15:198 16:45 17:385 18:158 20:205 21:4 22:188 23:5645 24:2286 25:6 27:2594 29:19 31:2421 32:96 34:1 35:73 36:1756 37:4416 38:2796 39:700 40:153 41:3973 42:1089 43:2197 44:292 45:16037 46:4137 47:321 49:1702 50:2159 51:100 52:1419 54:365 55:736 56:8 57:59 58:1808 59:1204 60:959 61:2254 62:2508 63:1953 64:5514 65:2320 66:4851 67:2975 68:1190 69:4156 70:1336 71:673 72:3051 74:2647 75:1390 76:585 77:2179 78:3913 79:3108 80:1988 81:1740 82:1494 83:1208 84:1366 85:3659 86:712 87:1959 88:2736 89:3295 90:517 91:7612 92:1996 93:2580 94:3498 95:4769 96:1306 97:349 98:993 99:736 100:75 101:1043 102:2069 103:29069 104:4375 105:462 106:875 107:2540 108:832 109:4205 110:2035 111:3277 112:2029 113:1548 114:1489 115:1975 116:1905 117:2509 118:2329 119:1840 120:1692 121:1073 122:2580 123:2116 124:1588 125:2125 128:1234 129:1104 130:968 131:2051 132:771 133:372 134:1903 135:289 136:882 137:846 138:2451 139:1502 140:854 141:1400 142:1291 143:1448 144:1210 145:343 146:1811 147:1488 148:2224 149:1729 150:844 151:1081 152:1850 153:459 154:3556 155:1417 156:1877 157:1227 158:1042 159:2151 160:2489 161:1267 162:3459 163:1261 164:1638 165:1596 166:710 167:1703 168:3808 169:840 170:4502 171:831 172:3137 173:3099 174:1023 175:1127 176:3519 177:4656 178:3497 179:2016 180:2283 181:2996 182:3253 183:1954 184:2385 185:19433 186:4328 187:3724 188:3866 189:3238 190:8870 191:1323 192:11005 193:8606 194:6996 195:4965 196:2986 197:2419 198:6002 199:6041 200:7492 201:5721 202:10485 203:10037 204:4557 205:3448 206:3772 207:3392 208:4038 209:4663 210:4280 211:2456 212:4036 213:3419 214:1153 215:67 216:6443 217:2664 218:1269 219:571 220:1946 221:979 222:843 223:2149 End of report

1 0

Re: [NANOG] [Mailman List] Strange behavior on the Juniper MX240
by Nehul Patel 06 May '22

06 May '22

Yes Mark it is odd On Thu, May 5, 2022 at 10:09 PM Mark Tinka via NANOG < admin(a)community.nanog.org> wrote: > Mark_Tinka4 <https://community.nanog.org/u/mark_tinka4> > May 6 > > Odd, as this said it came alive in Junos 10.4: > juniper.net > <https://www.juniper.net/documentation/us/en/software/junos/junos-overview/t…> > memory-enhanced | Junos OS | Juniper Networks > <https://www.juniper.net/documentation/us/en/software/junos/junos-overview/t…> > > Allocate more jtree memory for routing tables and Layer 3 VPNs. > > Mark. > ------------------------------ > > Visit Topic > <https://community.nanog.org/t/strange-behavior-on-the-juniper-mx240/55213/27> > to respond. > > To unsubscribe from these emails, click here > <https://community.nanog.org/email/unsubscribe/75ed36d4ce5f33f98f7b0c938cdc3…> > . > >

2 1

Re: Strange behavior on the Juniper MX240
by Saku Ytti 06 May '22

06 May '22

On Fri, 6 May 2022 at 12:17, Mark Tinka <mark(a)tinka.africa> wrote: > We have run into issues with platforms that have shipped with FIB's in favour of IPv4 and less for IPv6 and MPLS labels. Shifted around, you could give up whatever is left for IPv6 and ACL's to give more to IPv4, but you then end up losing native IPv6 scalability. And, of course, whatever other permutation you may think of that leaves you in a babysitting scenario for the protocol(s) assigned to peasantry. You are always here. You always need to understand your scale and how much resources you have available, what is possible and what is not. Existence or non-existence of configuration toggle to affect this doesn't make that situation worse or better. It is not implied to be a tactical short-term fix, it depends and you must understand what you are doing to determine your position in any case. -- ++ytti

2 1

Strange behavior on the Juniper MX240
by Nehul Patel 06 May '22

06 May '22

Hi NANOG, We are seeing some strange behavior on our Juniper MX240 Chassis it is randomly dropping the routes to the certain destination IP address getting the following errors on the MX240 Chassis If Someone has seen these errors before please suggest how to resolve it May 4 12:42:00 cr01 newsyslog[44735]: logfile turned over due to size>1024K May 4 12:42:01 /kernel: RT_PFE: RT msg op 1 (PREFIX ADD) failed, err 5 (Invalid) May 4 12:42:01 /kernel: RT_PFE: RT msg op 3 (PREFIX CHANGE) failed, err 5 (Invalid) May 4 12:42:01 last message repeated 4 times May 4 12:42:01 fpc0 RT: IPv6:0 - 2600:40fc:1011::/48 (add rt entry into jtree failed) May 4 12:42:01 fpc0 RT-HAL,rt_entry_add_msg_proc,2028: rt_halp_vectors->rt_create failed May 4 12:42:01 fpc0 RT-HAL,rt_entry_add_msg_proc,2092: proto ipv6,len 48 prefix 2600:40fc:1011::/48 nh 1048576 May 4 12:42:01 fpc0 RT-HAL,rt_msg_handler,540: route process failed May 4 12:42:01 fpc0 RT: Failed prefix add IPv6 - 2001:67c:20fc::/48 (No memory) on FE 0 May 4 12:42:01 fpc0 RT: IPv6:0 - 2001:67c:20fc::/48 (add rt entry into jtree failed) May 4 12:42:01 fpc0 RT-HAL,rt_entry_add_msg_proc,2028: rt_halp_vectors->rt_create failed May 4 12:42:01 fpc0 RT-HAL,rt_entry_add_msg_proc,2092: proto ipv6,len 48 prefix 2001:67c:20fc::/48 nh 1048576 May 4 12:42:01 fpc0 RT-HAL,rt_msg_handler,540: route process failed May 4 12:42:01 fpc0 RT: Failed prefix add IPv6 - 2606:2800:e004::/48 (No memory) on FE 0 May 4 12:42:01 fpc0 RT: Failed prefix add IPv6 - 2a05:3181:ffff::/48 (No memory) on FE 0 May 4 12:42:01 /kernel: RT_PFE: RT msg op 3 (PREFIX CHANGE) failed, err 5 (Invalid) May 4 12:42:01 /kernel: RT_PFE: RT msg op 1 (PREFIX ADD) failed, err 5 (Invalid) May 4 12:42:01 /kernel: RT_PFE: RT msg op 2 (PREFIX DELETE) failed, err 5 (Invalid) May 4 12:42:02 fpc0 RT: Failed prefix add IPv4 - 79.120.22/24 (No memory) on FE 0 May 4 12:42:02 fpc0 RT: IPv4:0 - 79.120.22/24 (add rt entry into jtree failed) May 4 12:42:02 fpc0 RT-HAL,rt_entry_add_msg_proc,2028: rt_halp_vectors->rt_create failed May 4 12:42:02 fpc0 RT-HAL,rt_entry_add_msg_proc,2092: proto ipv4,len 24 prefix 79.120.22/24 nh 1048583 May 4 12:42:02 /kernel: RT_PFE: RT msg op 1 (PREFIX ADD) failed, err 5 (Invalid) May 4 12:42:02 fpc0 RT-HAL,rt_msg_handler,540: route process failed May 4 09:33:17 fpc0 RSMON: Resource Category:jtree Instance:jtree2-seg0 Type:free-pages Available:20 is less than LWM limit:1638, rsmon_syslog_limit() May 4 09:33:17 fpc0 RSMON: Resource Category:jtree Instance:jtree2-seg0 Type:free-dwords Available:1280 is less than LWM limit:104857, rsmon_syslog_limit() May 4 09:33:18 fpc0 RSMON: Resource Category:jtree Instance:jtree3-seg0 Type:free-pages Available:19 is less than LWM limit:1638, rsmon_syslog_limit() May 4 09:33:18 fpc0 RSMON: Resource Category:jtree Instance:jtree3-seg0 Type:free-dwords Available:1216 is less than LWM limit:104857, rsmon_syslog_limit() May 4 09:33:18 fpc1 RSMON: Resource Category:jtree Instance:jtree0-seg0 Type:free-pages Available:16 is less than LWM limit:1638, rsmon_syslog_limit() May 4 09:33:18 fpc1 RSMON: Resource Category:jtree Instance:jtree0-seg0 Type:free-dwords Available:1024 is less than LWM limit:104857, rsmon_syslog_limit() May 4 09:33:18 fpc1 RSMON: Resource Category:jtree Instance:jtree1-seg0 Type:free-pages Available:15 is less than LWM limit:1638, rsmon_syslog_limit() May 4 09:33:18 fpc1 RSMON: Resource Category:jtree Instance:jtree1-seg0 Type:free-dwords Available:960 is less than LWM limit:104857, rsmon_syslog_limit() May 4 09:33:18 fpc1 RSMON: Resource Category:jtree Instance:jtree2-seg0 Type:free-pages Available:19 is less than LWM limit:1638, rsmon_syslog_limit() May 4 09:33:19 fpc1 RSMON: Resource Category:jtree Instance:jtree2-seg0 Type:free-dwords Available:1216 is less than LWM limit:104857, rsmon_syslog_limit() May 4 09:33:19 fpc1 RSMON: Resource Category:jtree Instance:jtree3-seg0 Type:free-pages Available:17 is less than LWM limit:1638, rsmon_syslog_limit() May 4 09:33:19 fpc1 RSMON: Resource Category:jtree Instance:jtree3-seg0 Type:free-dwords Available:1088 is less than LWM limit:104857, rsmon_syslog_limit() May 4 09:33:19 fpc2 RSMON: Resource Category:jtree Instance:jtree0-seg0 Type:free-pages Available:15 is less than LWM limit:1638, rsmon_syslog_limit() May 4 09:33:19 fpc2 RSMON: Resource Category:jtree Instance:jtree0-seg0 Type:free-dwords Available:960 is less than LWM limit:104857, rsmon_syslog_limit() May 4 09:33:19 fpc2 RSMON: Resource Category:jtree Instance:jtree1-seg0 Type:free-pages Available:15 is less than LWM limit:1638, rsmon_syslog_limit() May 4 09:33:19 fpc2 RSMON: Resource Category:jtree Instance:jtree1-seg0 Type:free-dwords Available:960 is less than LWM limit:104857, rsmon_syslog_limit() Any suggestions will be helpful Please do let me know if you have any questions. Regards and thanks, Nehul

9 25

Re: [NANOG] [Mailman List] Strange behavior on the Juniper MX240
by Nehul Patel 06 May '22

06 May '22

ok mark got it currently we are using the following DPCE Cards DPCE-R-4XGE-XFP DPCE-R-Q-4XGE-XFP When we tried using the command set chassis memory-enhanced route on the current Junos version 10.4 it says the command is not supported so we will need to upgrade the Junos to the newer version in order to try above command of it. On Thu, May 5, 2022 at 11:55 AM Mark Tinka via NANOG < admin(a)community.nanog.org> wrote: > Mark_Tinka4 <https://community.nanog.org/u/mark_tinka4> > May 5 > > If memory serves, I believe the DPC used I-chip for Layer 3, and EZ-chip > for Layer 2 (Ethernet framing + MAC look-up). Someone with a longer memory > may need to chime in. Mark. > ------------------------------ > > Visit Topic > <https://community.nanog.org/t/strange-behavior-on-the-juniper-mx240/55213/21> > to respond. > > To unsubscribe from these emails, click here > <https://community.nanog.org/email/unsubscribe/003092263321bdfde4f4ae64f65f0…> > . > >

2 1

Re: [NANOG] [Mailman List] Strange behavior on the Juniper MX240
by Nehul Patel 05 May '22

05 May '22

Ok Mark thank you for the suggestion we are currently running on the RE-S-1300 i am trying to check if juniper docs as the list of the DPCE with the I-Chip but not able to find it yet if you know DPCE model number let me know for it On Thu, May 5, 2022, 08:20 Nehul Patel <nehul.patel(a)gmail.com> wrote: > Ok Mark thank you for the suggestion we are currently running on the > RE-S-1300 i am trying to check if juniper docs as the list of the DPCE with > the I-Chip but not able to find it yet if you know DPCE model number let me > know for it > > > > On Thu, May 5, 2022, 01:46 Mark Tinka via NANOG <admin(a)community.nanog.org> > wrote: > >> Mark_Tinka4 <https://community.nanog.org/u/mark_tinka4> >> May 5 >> >> Certainly an option, but this requires quite a bit of babysitting, >> because as the DFZ oscillates, you can run into issues that send you into >> circles, largely unaware about FIB issues, especially when just a subset of >> routes are affected. >> >> So yes, definitely an option, but the OP will need to watch the line >> cards like a hawk, and be ultra sensitive to debugging regular issues vs. >> FIB-related issues. >> >> Mark. >> ------------------------------ >> >> Visit Topic >> <https://community.nanog.org/t/strange-behavior-on-the-juniper-mx240/55213/18> >> to respond. >> >> To unsubscribe from these emails, click here >> <https://community.nanog.org/email/unsubscribe/47c76e5320108f540dc1dd4ac05e9…> >> . >> >> >

2 1