February 2026 - NANOG - lists.nanog.org

What are you guys doing for tacacs+ in 2026?
by Drew Weaver 18 Feb '26

18 Feb '26

Howdy. I imagine that this is an issue that has come up before but I am having an issue finding how anyone else handled it. (Unless everyone is still running tac_plus on RHEL7) I'm trying to migrate some tac plus instances to a new Linux distro that apparently doesn't support tcp_wrappers and I'm having trouble both compiling it and making an RPM for it. I've tried both the original https://www.shrubbery.net/tac_plus/ and the now sadly abandoned Facebook version https://github.com/facebook/tac_plus If there is another tacacs+ solution everyone has moved to that I am unaware of please enlighten me. Thank you, -Drew

15 27

NANOG 96 Talks are Streaming! + More!
by Nanog News 13 Feb '26

13 Feb '26

*** NANOG 96 Talks are Streaming!* ------------------------------------------------------------*N96 Talks Are Officially Live on YouTube! 🎥✨* NANOG 96 sessions are currently streaming! All talks will be uploaded by today at 6:30pm PST, but you can start watching now. Subscribe to the NANOG YouTube channel and keep the conversation going long after the conference. *WATCH NOW* (https://www.youtube.com/playlist?list=PLO8DR5ZGla8i1P6NjMTMxvym0SWTtyn0G) *** Inside NANOG 96: Attendees Share What Made our Last Conference Unforgettable* ------------------------------------------------------------*Straight from your Socials, the NANOG Community Shares What Made N96 Worth It* 806 attendees gathered in San Francisco, Feb. 2–4 to exchange ideas and shape the future of the Internet. LinkedIn lit up with photos, takeaways, and thoughtful recaps from attendees. Here is a snapshot of what the NANOG community is still talking about. *READ NOW *(https://nanog.org/stories/inside-nanog-96-attendees-share-what-made-our-last-conference-unforgettable/) *** NANOG Welcomes 34 New Committee Appointees in 2026* ------------------------------------------------------------*Volunteer Leadership Continues to Power the Future of NANOG* Whether you enjoy the NANOG Conferences because of the program, the interactions, or the community you find, it's a committee of volunteers that worked to make it happen. Check out all of the committees and their members for 2026 below. *LEARN MORE *(https://nanog.org/about/who-we-are/committees/) *** Spotlight on Compudopt: Love for Our Communities in Action* ------------------------------------------------------------ This February, show love by connecting neighbors in need. Many families still lack the devices needed to access the networks you help build and maintain. Introduce Compudopt to your CSR team to power digital access. Email Carolyn.Fung(a)compudopt.org to explore the opportunities! *EMAIL NOW* (mailto:Carolyn.Fung@compudopt.org) *** A Little Love from NANOG ❤️* ------------------------------------------------------------ *NANOG has always been powered by community.* The hallway track debates. The late night troubleshooting. The quiet mentorship moments. The volunteers who raise their hands. The operators who show up, share, and build. Love looks a little different here. It looks like collaboration. It looks like knowledge freely exchanged. It looks like a room full of people who care deeply about making the Internet stronger. To every attendee, volunteer, speaker, and Newcomer finding your place in the community, thank you for being part of it. You make NANOG what it is. *** Stay Connected* ------------------------------------------------------------http://www.facebook.comhttp://www.instagram.com/nanog_org/http://www.linkedin.com/company/nanog/https://www.twitter.com/nanog/http://nanog.org

1 0

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 13 Feb '26

13 Feb '26

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 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 14 Feb, 2026 IPv4 BGP Table (Global) as seen at Japan. Report Website: https://thyme.apnic.net Detailed Analysis: https://thyme.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 1033567 Prefixes after maximum aggregation (per Origin AS): 397442 Deaggregation factor: 2.60 Unique aggregates announced (without unneeded subnets): 509204 Number of IPv4 prefixes with a valid ROA: 614359 Number of IPv4 prefixes with an invalid ROA: 1447 Number of IPv4 prefixes with no ROA: 417761 Total ASes present in the Internet Routing Table: 77952 Prefixes per ASN: 13.26 Origin-only ASes present in the Internet Routing Table: 66954 Origin ASes announcing only one prefix: 27251 Transit ASes present in the Internet Routing Table: 10998 Transit-only ASes present in the Internet Routing Table: 552 Average AS path length visible in the Internet Routing Table: 4.7 Max AS path length visible: 69 Max AS path prepend of ASN (269326) 61 Prefixes from unregistered ASNs in the Routing Table: 1102 Number of instances of unregistered ASNs: 1142 Number of 32-bit ASNs allocated by the RIRs: 48724 Number of 32-bit ASNs visible in the Routing Table: 39855 Prefixes from 32-bit ASNs in the Routing Table: 222994 Number of bogon 32-bit ASNs visible in the Routing Table: 127 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 446 Number of addresses announced to Internet: 3104214656 Equivalent to 185 /8s, 6 /16s and 142 /24s Percentage of available address space announced: 83.8 Percentage of allocated address space announced: 83.8 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: 336801 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 281735 Total APNIC prefixes after maximum aggregation: 82491 APNIC Deaggregation factor: 3.42 Prefixes being announced from the APNIC address blocks: 268189 Unique aggregates announced from the APNIC address blocks: 107036 APNIC Region origin ASes present in the Internet Routing Table: 15051 APNIC Prefixes per ASN: 17.82 APNIC Region origin ASes announcing only one prefix: 4617 APNIC Region transit ASes present in the Internet Routing Table: 1978 Average APNIC Region AS path length visible: 4.7 Max APNIC Region AS path length visible: 35 Number of APNIC region 32-bit ASNs visible in the Routing Table: 10600 Number of APNIC addresses announced to Internet: 753103616 Equivalent to 44 /8s, 227 /16s and 115 /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-155961 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: 303705 Total ARIN prefixes after maximum aggregation: 136377 ARIN Deaggregation factor: 2.23 Prefixes being announced from the ARIN address blocks: 303104 Unique aggregates announced from the ARIN address blocks: 146611 ARIN Region origin ASes present in the Internet Routing Table: 19388 ARIN Prefixes per ASN: 15.63 ARIN Region origin ASes announcing only one prefix: 7080 ARIN Region transit ASes present in the Internet Routing Table: 1927 Average ARIN Region AS path length visible: 4.3 Max ARIN Region AS path length visible: 25 Number of ARIN region 32-bit ASNs visible in the Routing Table: 5466 Number of ARIN addresses announced to Internet: 1342902272 Equivalent to 80 /8s, 11 /16s and 16 /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-402332 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, 45/8, 47/8, 48/8, 50/8, 52/8, 54/8, 55/8, 56/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: 284032 Total RIPE prefixes after maximum aggregation: 140611 RIPE Deaggregation factor: 2.02 Prefixes being announced from the RIPE address blocks: 286370 Unique aggregates announced from the RIPE address blocks: 185996 RIPE Region origin ASes present in the Internet Routing Table: 29241 RIPE Prefixes per ASN: 9.79 RIPE Region origin ASes announcing only one prefix: 12140 RIPE Region transit ASes present in the Internet Routing Table: 3988 Average RIPE Region AS path length visible: 4.8 Max RIPE Region AS path length visible: 31 Number of RIPE region 32-bit ASNs visible in the Routing Table: 13041 Number of RIPE addresses announced to Internet: 733873024 Equivalent to 43 /8s, 190 /16s and 3 /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-216475 RIPE Address Blocks 2/8, 5/8, 25/8, 31/8, 37/8, 46/8, 51/8, 53/8, 57/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: 126578 Total LACNIC prefixes after maximum aggregation: 30299 LACNIC Deaggregation factor: 4.18 Prefixes being announced from the LACNIC address blocks: 122331 Unique aggregates announced from the LACNIC address blocks: 49544 LACNIC Region origin ASes present in the Internet Routing Table: 11362 LACNIC Prefixes per ASN: 10.77 LACNIC Region origin ASes announcing only one prefix: 2677 LACNIC Region transit ASes present in the Internet Routing Table: 2552 Average LACNIC Region AS path length visible: 5.4 Max LACNIC Region AS path length visible: 69 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 9369 Number of LACNIC addresses announced to Internet: 170848256 Equivalent to 10 /8s, 46 /16s and 240 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-275868 + 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: 36415 Total AfriNIC prefixes after maximum aggregation: 6949 AfriNIC Deaggregation factor: 5.24 Prefixes being announced from the AfriNIC address blocks: 53127 Unique aggregates announced from the AfriNIC address blocks: 19628 AfriNIC Region origin ASes present in the Internet Routing Table: 2016 AfriNIC Prefixes per ASN: 26.35 AfriNIC Region origin ASes announcing only one prefix: 737 AfriNIC Region transit ASes present in the Internet Routing Table: 387 Average AfriNIC Region AS path length visible: 5.3 Max AfriNIC Region AS path length visible: 53 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 1379 Number of AfriNIC addresses announced to Internet: 103284480 Equivalent to 6 /8s, 39 /16s and 255 /24s AfriNIC AS Blocks 36864-37887, 327680-329727 & ERX transfers AfriNIC Address Blocks 41/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 13815 8945 105 CHINAMOBILE-CN China Mobile Communication 7545 6007 832 555 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 5027 4193 77 ERX-CERNET-BKB China Education and Resear 9498 4790 545 330 BBIL-AP BHARTI Airtel Ltd., IN 7552 4070 1332 29 VIETEL-AS-AP Viettel Group, VN 7713 3699 1044 68 TELKOMNET-AS-AP PT Telekomunikasi Indones 56046 3467 887 178 CMNET-JIANGSU-AP China Mobile communicati 45899 3333 1868 99 VNPT-AS-VN VNPT Corp, VN 17561 3036 191 587 LCS-AS-AP LARUS Limited, HK 24560 2973 865 499 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd., 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 14190 38853 5507 AMAZON-02 - Amazon.com, Inc., US 22773 4782 3114 365 ASN-CXA-ALL-CCI-22773-RDC - Cox Communica 11492 4637 308 1021 CABLEONE - CABLE ONE, INC., US 7155 3861 286 85 VIASAT-SP-BACKBONE - ViaSat,Inc., US 174 3757 8769 865 COGENT-174 - Cogent Communications, LLC, 6327 3699 1321 71 SHAW - Shaw Communications, CA 396982 3322 4856 492 GOOGLE-CLOUD-PLATFORM - Google LLC, US 749 3142 54728 2393 DNIC-AS-00749 - United States Department 16625 2801 1206 2123 AKAMAI-AS - Akamai Technologies, Inc., US 36352 2695 221 888 AS-COLOCROSSING - HostPapa, 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 7243 1711 149 UNI2-AS, ES 39891 4969 306 72 ALJAWWALSTC-AS, SA 9009 3898 365 2231 M247, RO 20940 3830 3393 113 AKAMAI-ASN1, NL 12389 3173 2318 869 ROSTELECOM-AS PJSC Rostelecom. Technical 212238 2600 187 1896 CDNEXT, GB 34984 2450 365 575 TELLCOM-AS, TR 8452 1702 1853 19 TE-AS TE-AS, EG 13188 1607 100 27 TRIOLAN, UA 203020 1593 242 772 HOSTROYALE, IN 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 12681 3292 604 UNINET, MX 10620 3448 457 1103 Telmex Colombia S.A., CO 13999 2461 506 349 Mega Cable, S.A. de C.V., MX 11830 1992 369 65 Instituto Costarricense de Electricidad y 11664 1413 278 33 Techtel LMDS Comunicaciones Interactivas 28573 1374 2430 272 Claro NXT Telecomunicacoes Ltda, BR 3816 1342 770 213 COLOMBIA TELECOMUNICACIONES S.A. ESP BIC, 6147 1255 371 22 INTEGRATEL PERU S.A.A., PE 22884 1055 67 357 TOTAL PLAY TELECOMUNICACIONES SA DE CV, M 26615 1020 2486 57 TIM SA, BR 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 24835 1984 648 34 RAYA-AS, EG 36992 1844 1532 338 ETISALAT-MISR, EG 24863 1286 389 16 LINKdotNET-AS, EG 36903 1232 555 98 MT-MPLS, MA 36935 1193 523 46 Vodafone-, EG 37069 1117 1112 11 MOBINIL, EG 29571 1071 78 20 ORANGE-COTE-IVOIRE, CI 20011 580 154 212 NTT-DATA-Inc, ZA 328608 579 48 167 Africa-on-Cloud-AS, ZA 36914 562 82 3 KENET-AS, KE 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 16509 14190 38853 5507 AMAZON-02 - Amazon.com, Inc., US 9808 13815 8945 105 CHINAMOBILE-CN China Mobile Communication 8151 12681 3292 604 UNINET, MX 12479 7243 1711 149 UNI2-AS, ES 7545 6007 832 555 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 5027 4193 77 ERX-CERNET-BKB China Education and Resear 39891 4969 306 72 ALJAWWALSTC-AS, SA 9498 4790 545 330 BBIL-AP BHARTI Airtel Ltd., IN 22773 4782 3114 365 ASN-CXA-ALL-CCI-22773-RDC - Cox Communica 11492 4637 308 1021 CABLEONE - CABLE ONE, INC., US Complete listing at https://thyme.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 9808 13815 13710 CHINAMOBILE-CN China Mobile Communications Grou 8151 12681 12077 UNINET, MX 12479 7243 7094 UNI2-AS, ES 7545 6007 5452 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 5027 4950 ERX-CERNET-BKB China Education and Research Net 39891 4969 4897 ALJAWWALSTC-AS, SA 9498 4790 4460 BBIL-AP BHARTI Airtel Ltd., IN 22773 4782 4417 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 7552 4070 4041 VIETEL-AS-AP Viettel Group, VN 7155 3861 3776 VIASAT-SP-BACKBONE - ViaSat,Inc., US 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 393266 UNALLOCATED 8.23.52.0/24 46887 CROWNCASTLE-AS46887 - C 396894 UNALLOCATED 8.28.201.0/24 3356 LEVEL3 - Level 3 Parent 13450 UNALLOCATED 8.29.117.0/24 55002 DEFENSE-NET - F5, Inc., 394936 UNALLOCATED 8.33.224.0/24 22442 HOU-PHONOSCOPE - Phonos 395195 UNALLOCATED 8.38.115.0/24 3356 LEVEL3 - Level 3 Parent 1782 UNALLOCATED 8.42.19.0/24 3356 LEVEL3 - Level 3 Parent 13342 UNALLOCATED 12.17.5.0/24 174 COGENT-174 - Cogent Com 26345 UNALLOCATED 12.21.93.0/24 40264 TWC-40264-WI-MN-UPPERMI 396831 UNALLOCATED 12.23.198.0/24 7018 ATT-INTERNET4 - AT&T En 397665 UNALLOCATED 12.24.28.0/24 7018 ATT-INTERNET4 - AT&T En 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 - Hurricane Electric LLC, US Complete listing at https://thyme.apnic.net/current/data-spar Advertised Unallocated Addresses -------------------------------- Unassigned Network ASN Information AS Name 23.137.48.0/24 Origin: 16904 ARVIG-16904 - Arvig Enterprises Inc., US 23.137.48.0/24 Transit: 3257 GTT-BACKBONE GTT, US 23.137.200.0/24 Origin: 16276 OVH, FR 23.137.200.0/24 Transit: 2516 KDDI KDDI CORPORATION, JP 23.140.216.0/24 Origin: 27176 DATAWAGON - DataWagon LLC, US 23.140.216.0/24 Transit: 20278 NEXEON - Nexeon Technologies, Inc., US 23.141.0.0/24 Origin: 395350 RESERVED, ZZ 23.141.0.0/24 Transit: 11426 TWC-11426-CAROLINAS - Charter Communicat 23.142.24.0/24 Origin: 62164 HEYMMAN-2, CA 23.142.24.0/24 Transit: 64236 UNREAL-SERVERS - UnReal Servers, LLC, US 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:14 /10:40 /11:92 /12:302 /13:580 /14:1197 /15:2089 /16:13697 /17:8342 /18:13617 /19:25128 /20:46111 /21:52825 /22:113805 /23:106902 /24:648132 /25:678 /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 8151 6851 12681 UNINET, MX 12479 6171 7243 UNI2-AS, ES 39891 3655 4969 ALJAWWALSTC-AS, SA 11492 3497 4637 CABLEONE - CABLE ONE, INC., US 6327 3479 3699 SHAW - Shaw Communications, CA 22773 3053 4782 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications Inc., US 7155 2820 3861 VIASAT-SP-BACKBONE - ViaSat,Inc., US 16509 2521 14190 AMAZON-02 - Amazon.com, Inc., US 30036 2313 2658 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Communications Corp, US 10620 2228 3448 Telmex Colombia S.A., CO Complete listing at https://thyme.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1847 2:1540 3:985 4:9 5:5072 6:187 7:6 8:1530 9:26 11:172 12:1228 13:639 14:2687 15:425 16:174 17:398 18:915 20:598 21:4 22:188 23:8182 24:2621 25:2 27:2717 29:19 31:3437 32:32 34:81 35:295 36:4637 37:4504 38:10436 39:1269 40:435 41:4522 42:968 43:2930 44:420 45:19757 46:4928 47:407 48:38 49:2202 50:2075 51:599 52:1278 54:243 55:1109 56:11 57:317 58:2243 59:1429 60:1174 61:3136 62:3100 63:1770 64:6225 65:2130 66:6044 67:3259 68:1489 69:4214 70:1046 71:618 72:3075 74:2974 75:1506 76:588 77:2826 78:1915 79:1799 80:2337 81:2213 82:4023 83:1461 84:2046 85:3813 86:1109 87:2398 88:1346 89:4697 90:817 91:8429 92:2850 93:3010 94:4328 95:4579 96:1453 97:314 98:946 99:787 100:70 101:1344 102:4390 103:32270 104:5541 105:793 106:924 107:2839 108:1234 109:4219 110:2303 111:4164 112:3155 113:1702 114:2179 115:2224 116:2170 117:3462 118:2524 119:2101 120:2707 121:1569 122:2964 123:2338 124:1698 125:2995 126:125 128:1667 129:946 130:1593 131:2371 132:783 133:461 134:1634 135:558 136:1629 137:1407 138:3023 139:1615 140:1846 141:1569 142:2477 143:2157 144:1675 145:629 146:2203 147:2205 148:2791 149:3016 150:1315 151:2707 152:2283 153:893 154:9675 155:2293 156:4600 157:2243 158:1499 159:2769 160:3713 161:1980 162:4043 163:2338 164:2019 165:2601 166:1288 167:2243 168:3987 169:926 170:5491 171:1115 172:4567 173:3461 174:895 175:1352 176:3799 177:4749 178:4386 179:2288 180:3092 181:4411 182:3947 183:2613 184:1994 185:21754 186:5612 187:4869 188:4550 189:4463 190:9758 191:1556 192:11473 193:9527 194:7833 195:5698 196:3275 197:3204 198:6259 199:6126 200:8221 201:6396 202:10812 203:10540 204:4749 205:3792 206:4484 207:3997 208:4376 209:5486 210:5012 211:2781 212:4988 213:4074 214:1080 215:54 216:7180 217:3490 218:1715 219:590 220:2197 221:1316 222:1073 223:3321 End of report

1 0

ARIN again being impossible. Why are they so difficult? Trying to contact someone in management there (who helped us in Sep 2024)
by John Palmer 13 Feb '26

13 Feb '26

ARIN is again being problematic. We have some legacy resources that were registered back in the bad old days of the 1990's and are trying to bring them under the ARIN RSA. We also have resources that are already registered under the proper organization, but want them under our existing RSA. They are asking for a document showing that the company is in good standing. We attached the document but they refuse to accept it and are giving us the run-around. We already certified this back in 2024. The ARIN consultant simply went on the state website and was able to see the company was in good standing. Now they want a document that doesn't exist (state provides no such document). The other two three orgs that we are trying to merge into our current OrgId - those may be a bit more difficult - being registered back when you sent Jon Postel an e-mail template to get space. Look, we are trying to give them MORE money (the fee will go up if we add those IP4 resources to our existing RSA). Hard to believe they are this difficult. If there is any management from ARIN on this list, please contact me. Thanks John

6 7

EVPN-MPLS MH-ES DF Election Behavior and BUM forwarding
by Graham Johnston 12 Feb '26

12 Feb '26

Good day everyone. For those of you that are using EVPN-MPLS, although this likely applies equally to VXLAN based transport, I have a question for you based on your observations in your production networks. I have a basic configuration as follows: * Two PE routers that provide connectivity to a single downstream device via an all-active multi-homed LAG connection. * The downstream device could be a single aggregation switch, or something like an OLT. Either way, the downstream devices is configured with an uplink port to each PE, and the ports in question use LACP. * The two PE routers do not have any physical connections between each other, but instead have redundant connections to a pair of core routers. These uplinks carry MPLS traffic. * The upstream core routers are acting as route reflectors. * MRAI is set to 0 for route exchange between the core and PE routers. What I am curious to get feedback on is related to BUM traffic forwarding in the brief moment between the start and conclusion of a DF election; and risks related to BUM packets being forwarded back into the same ES from whence they came. Scenario of concern: * PE1 and PE2 are both in a steady state in the network, full routing tables are already propagated. * The port between PE1 and the CE device is active, with LACP negotiated, and with PE1 having announced the relevant EVPN routes, specifically including the type 1 and 4 routes; the port from PE2 to CE is not currently active. * Upon the link between the CE device and PE2 becoming active, with LACP negotiated, PE2 should announce the relevant type 1 and 4 routes and the DF election should commence. Before the conclusion of the DF election, we expect the following to happen, but we only have reference to single vendor implementation and we know there can be RFC interpretation differences which lead to implementation differences. * There will likely be a very brief moment wherein LACP is up and the port on PE2 can send and receive traffic, but the EVPN routes have not yet propagated from PE2 to PE1 for PE1 to include PE2's ESI label in outgoing BUM traffic that may need to be delivered to ports unrelated to this ES that may exist in the same EVI on PE2. The result of which is that those BUM packets could be forwarded by PE2 back to the CE device. I'm not clear that this is avoidable, but I expect the propagation and processing period here is very short. * Whereas, if PE2 received a BUM packet from the newly activated ES interface that was destined for PE1, it would include PE1's ES label in the stack. As PE2, in this scenario, already knows this label value prior to the activation of the ES port, I suspect there was never really a risk of PE1 receiving a BUM packet from PE2, from the same ES, that it then forwarded back into the ES. * In this moment, we believe that PE2 should not assume the DF role, for no other reason than it clearly had received routes for this ES that indicated another PE already being active. My reading of RFC7432 in this regard does not seem 110% explicit, but I don't know why PE2 would assume anything other than a non-DF role prior to the conclusion of the election. * As soon as the type 1 and 4 routes reach from PE2 reach PE1 and they are processed, all future BUM packets sent to PE2 should have PE2's ESI label on the stack, at which point, PE2 should not forward BUM traffic into the ES, as long as it didn't assume the DF role prior to the conclusion of the election. * After the election timer has concluded: - the DF role may stay with PE1, at which point nothing really changes other than the shared knowledge of that. All is good. - the DF role could move to PE2, but both PE1 and PE2 have ESI labels for each other already, and it's really just the rest of the network adjusting where it sends BUM packets relative to this ES. I guess there's a chance that there was already a packet in flight to PE1 for this ES, and PE1 may not forward the packet into the ES; I'm not clear on this, but this isn't an area of concern right now. Other scenarios: I'm frankly not worried about other scenarios as I suspect most platforms have a holddown timer that can be used to suppress forwarding of BUM packets into an ES before routes have a chance to propagate and the conclusion of the DF election. What I'm concerned about in asking for this feedback is largely interpretation of section 8.5 (Designated Forwarder Election) of RFC7432, and how it, for instance, doesn't explicitly say that ahead of step 4, the new PE should assume a non-DF role; and what operators see in their production networks. Do the major manufacturers of network gear and network operating systems all do the same thing? Are there systemic problems related to ES looped BUM traffic prior to the conclusion of the DF election and we just need to accept that? Hopefully this all makes sense. If there is something I neglected to comment on or consider, or just got wrong, I'm happy to receive some education. Thanks in advance, Graham

4 3

Sling TV contact
by Joshua Zukerman (Clearline Communications) 10 Feb '26

10 Feb '26

Hello, I am looking for a contact at Sling TV. I operate a small WISP that was given an ARIN IPv4 allocation last year and have been slowing rolling out the new IP allocations to my customers (mostly residential with some business). When trying to access Sling.com, there is an HTTP error when visiting from any IPv4 address in the new IP allocation. I added the allocation to various Geo IP location databases online that I could find last year. I have rDNS setup for the new IP allocation. This appears to be the only website that my customers cannot access. My customer cannot find any phone number to call Sling to inform them of the issue. Thank you. Regards, Joshua Zukerman Clearline Communications Inc. DBA TK Networks Office 207-558-9911 AS401455

3 2

Spoofer Report for NANOG for Jan 2026
by CAIDA Spoofer Project 08 Feb '26

08 Feb '26

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 Jan 2026: none inferred Source Address Validation issues inferred during Jan 2026: ASN Name First-Spoofed Last-Spoofed 27364 ACS-INTERNET 2016-09-27 2026-01-09 22883 CONDENAST 2019-05-29 2026-01-27 21804 ACCESS-SK 2019-06-09 2026-01-29 52643 N&G Tecnologia LTDA 2019-09-24 2026-01-27 393397 LREC-LRT 2020-08-02 2026-01-24 36352 AS-COLOCROSSING 2020-10-08 2026-01-29 55016 IMPER-AS-1 2021-05-18 2026-01-25 22773 ASN-CXA-ALL-CCI-22773-RDC 2021-10-24 2026-01-27 12183 TALKIE-COMMUNICATIONS 2022-12-10 2026-01-30 855 CANET-ASN-4 2023-04-26 2026-01-18 400282 2023-04-27 2026-01-31 393577 SCCNET 2023-05-03 2026-01-31 394684 AS-GOLD 2024-01-17 2026-01-31 27425 ASN-IDK-27425 2024-02-21 2026-01-22 53755 IOFLOOD 2024-02-23 2026-01-30 393530 TLU 2024-05-22 2026-01-28 19935 CRRS 2024-05-29 2026-01-22 273143 2025-01-22 2026-01-24 54334 ROYA 2025-03-13 2026-01-29 273843 2025-04-02 2026-01-28 271951 IT PRONETWORK C.A. 2026-01-21 2026-01-21 399439 ATV-PUBLIC 2026-01-28 2026-01-28 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

Fwd: [cherry.heiyui@keio.jp: Sad news: Dave Farber has passed away]
by Rich Kulawiec 08 Feb '26

08 Feb '26

----- Forwarded message from "Cherry, Hei Yui WONG" <cherry.heiyui(a)keio.jp> ----- > From: "Cherry, Hei Yui WONG" <cherry.heiyui(a)keio.jp> > Date: Sun, 8 Feb 2026 11:06:40 +0900 > Subject: Sad news: Dave Farber has passed away > > We are heartbroken to report that our colleague -- our mentor, friend, and > conscience -- David J. Farber passed away suddenly at his home in Roppongi, > Tokyo. He left us on Saturday, Feb. 7, 2026, at the too-young age of 91. > > To his son Manny, he was simply ???Dad???, his bedrock whom he will miss > immeasurably. They spoke almost daily by video throughout his time in > Japan, and shared special times on numerous visits. He is survived by son > Manny Farber and daughter-in-law Mei Xu, daughter-in-law Carol Hagan and > grandsons Nate Farber and Sam Farber. He was preceded in death by his wife > Gloria (G.G.) and son Joe Farber. > > Dave???s career began with his education at Stevens Institute of Technology, > which he loved deeply and served as a Trustee. He joined the legendary Bell > Labs during its heyday, and worked at the Rand Corporation. Along the way, > among countless other activities, he served as Chief Technologist of the > U.S. Federal Communications Commission; became a proficient > (instrument-rated) pilot; and was an active board member of the Electronic > Frontier Foundation, a digital civil-liberties organization. > > His professional accomplishments and impact are almost endless, but often > captured by one moniker: ???grandfather of the Internet,??? acknowledging the > foundational contributions made by his many students at the University of > California, Irvine; the University of Delaware; the University of > Pennsylvania; and Carnegie Mellon University > > In 2018, at the age of 83, Dave moved to Japan to become Distinguished > Professor at Keio University and Co-Director of the Keio Cyber Civilization > Research Center (CCRC). He loved teaching, and taught his final class on > January 22, 2026. > > At CCRC, one of his most enjoyable activities was co-hosting the IP-Asia > online gathering, which has met every Monday for more than five years and > has addressed many aspects of the impact of technology on civilization. > Dave thrived in Japan in every way. > > We, the IP-Asia community, will gather for an online remembrance of Dave at > the usual time and place, 2100 JST on Monday, February 9, 2026. > > It???s impossible to summarize a life and career as rich and long as Dave???s > in our few words here. And each of us, even those who knew him for decades, > represent just one facet of his life. But because we are here at its end, > we have the sad duty of sharing this news. Further information and a more > formal obituary are forthcoming. > > With condolences to Manny and the rest of the family, > > Jiro Kokuryo > Cherry Wong > Kaori Suzuki > Rodney Van Meter > Dan Gillmor > > Manny can be reached at manny.farber(a)gmail.com. ----- End forwarded message -----

2 1

Hey Google - Recaptcha sucks
by William Herrin 07 Feb '26

07 Feb '26

I'm at SEATAC airport trying to access www.google.com via the public wifi with Firefox. Apparently you really don't like that because it's stuck in a Recaptcha loop displaying captcha after captcha after captcha. I can't help but notice that Chrome works. It's your _competitor_ Firefox that you don't seem to like. IP address: 198.134.98.50 Time: 2026-02-05T20:03:35Z URL: https://www.google.com/ FIx it, eh? Regards, Bill Herrin

8 10

AS49666 certain nets out of global table
by Marco Moock 07 Feb '26

07 Feb '26

Hello! Today I noticed various connection attempts from 2001:4188:2::/48 on my TOR relay, but all replies got back a route unreachable. When checking https://bgp.tools/prefix/2001:4188:2:600:10:10:34:36 I noticed that this net was not in the table since start of January. Certain (but not all) of their IPv4 nets are also not propagated anymore to the public bgp looking glasses. Is that part of the Iran internet shutdown or is that a non-political issue? Sadly, their peers don't have RIPE probes with IPv6, so no way to test there. -- kind regards Marco Send unsolicited bulk mail to 1770474123muell(a)stinkedores.dorfdsl.de

1 0