September 2021 - NANOG - lists.nanog.org

Re: IPv6 woes - RFC
by Stephen Satchell 19 Sep '21

19 Sep '21

I concur that the problem is not a routing hardware problem. It's a perception problem with the various ISPs. I have fiber service with AT&T. My little server farm endpoints all have IPv6 addresses, including the edge router. I also have a plan to allocate IPv6 addresses to my LAN devices, and to protect the LAN devices from outside interference by rules in the NFTABLES firewall that include connection tracking on outbound requests. (IPv4 will still use NAT to keep nefarious people from probing my internals.) Specifically, when I was doing my mail server refresh (moving from Red Hat to Canonical) I decided it was time to offer IPv6 connectivity in the mail server to "future proof" my setup. That included adding AAAA records in my DNS zone files. Failure! The issues: 1. I learned that there are no "static addresses" in IPv6, as far as AT&T was concerned. By all appearances, though, the IPv6 /64 is relatively static, for now, similar to the way that early cable modem deployments kept the same IPv4 addresses. (Until the cable people started forcing changes on DHCP lease renewal, that is.) 2. My request for PTR records was denied, which means I can't satisfy Best Practices for a mail server in the IPv6 space. No PTR records, no redirection of ip6.apra space, nothing. I include AT&T's refusal below. 3. I don't know how to get an IPv6 allocation from ARIN, how to request AT&T to route it, or how to deal with the DNS server issues. Oh, I know how to configure BIND9; I would prefer using a 24/7/365 provider. For example, my master zone files are with Register.com, so if my circuit goes down the name resolution still happens. Register.com appears not to provide reverse-DNS PTR zone support (in6.arpa). A Google search turned up NOTHING for in6.arpa hosting. That tells me that IPv6 is not "Internet Ready" for small users. Given the level of FU responses I get trying to work with it, I will stop banging my head against the wall. So I stick with IPv4, because that will be the "standard" until the day I die, as far as I can tell. (I removed the AAAA record, so as not to confuse mail server that DO operate IPv6.) > Subject: RE: Need IPv6 PTR record for my IPv6 mail server > Date: Mon, 19 Jul 2021 12:52:53 +0000 > From: Prov-DNS <prov-dns(a)att.com> > To: Prov-DNS <prov-dns(a)att.com>, att(a)satchell.net <att(a)satchell.net> > > > Hello > We don't process DNS request on IPv6 addresses. We only process DNS > request on IPv4 static assigned addresses. If you would like us to > process a DNS request for you on a IPv4 address please provide the > following information. > > IPv4 address you would like the record created for Host name you would > like that IP address pointed to > > Thanks > Michael AT&T Prov-DNS > > -----Original Message----- > From: Stephen Satchell <att(a)satchell.net> > Sent: Friday, July 16, 2021 5:42 PM > To: DNSUpdates cB <g12988(a)att.com> > Subject: Need IPv6 PTR record for my IPv6 mail server > > Here is the record I need inserted into your ip6.arpa DNS zone: > >> 2.3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.c.d.d.0.b.9.7.0.0.7.1.0.0.6.2.ip6.arpa. 0 IN PTR smtp.satchell.net. > > This is the result from the question section of a dig(1) request for the PTR record for my IPv6 address 2600:1700:79b0:ddc0::32, and the fully-qualified domain name of the server. > > You can verify the information using dig smtp.satchell.net AAAA and > checking the reverse. > > This is the only server in my collection that needs the IPv6 pointer.

4 5

The great Netflix vpn debacle!
by John Alcock 19 Sep '21

19 Sep '21

Well, It happened. I have multiple subscribers calling in. They can not access Netflix. Any contacts on list for Netflix that I can use to get my up blocks whitelisted? John

25 50

Never push the Big Red Button (New York City subway failure)
by Sean Donelan 17 Sep '21

17 Sep '21

NEW YORK CITY TRANSIT RAIL CONTROL CENTER POWER OUTAGE ISSUE ON AUGUST 29, 2021 Key Findings September 8, 2021 https://www.governor.ny.gov/sites/default/files/2021-09/WSP_Key_Findings_Su… Key Findings [...] 3. Based on the electrical equipment log readings and the manufacturer’s official assessment, it was determined that the most likely cause of RCC shutdown was the “Emergency Power Off” button being manually activated. Secondary Findings 1. The “Emergency Power Off” button did not have a protective cover at the time of the shutdown or the following WSP investigation. [...] Mitigation Steps 1. Set up the electrical equipment Control and Communication systems properly to stay active so that personnel can monitor RCC electrical system operations. [...]

24 32

Weekly Global IPv4 Routing Table Report
by cscora＠apnic.net 17 Sep '21

17 Sep '21

This is an automated weekly mailing describing the state of the Internet 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 http://thyme.rand.apnic.net. If you have any comments please contact Philip Smith <pfsinoz(a)gmail.com>. Global IPv4 Routing Table Report 04:00 +10GMT Sat 18 Sep, 2021 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 862995 Prefixes after maximum aggregation (per Origin AS): 326303 Deaggregation factor: 2.64 Unique aggregates announced (without unneeded subnets): 415008 Total ASes present in the Internet Routing Table: 71963 Prefixes per ASN: 11.99 Origin-only ASes present in the Internet Routing Table: 61847 Origin ASes announcing only one prefix: 25513 Transit ASes present in the Internet Routing Table: 10116 Transit-only ASes present in the Internet Routing Table: 335 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 37 Max AS path prepend of ASN ( 45609) 34 Prefixes from unregistered ASNs in the Routing Table: 926 Number of instances of unregistered ASNs: 931 Number of 32-bit ASNs allocated by the RIRs: 37242 Number of 32-bit ASNs visible in the Routing Table: 30939 Prefixes from 32-bit ASNs in the Routing Table: 144083 Number of bogon 32-bit ASNs visible in the Routing Table: 32 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 465 Number of addresses announced to Internet: 3054633344 Equivalent to 182 /8s, 18 /16s and 1 /24s Percentage of available address space announced: 82.5 Percentage of allocated address space announced: 82.5 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 99.5 Total number of prefixes smaller than registry allocations: 286863 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 231782 Total APNIC prefixes after maximum aggregation: 66191 APNIC Deaggregation factor: 3.50 Prefixes being announced from the APNIC address blocks: 227246 Unique aggregates announced from the APNIC address blocks: 91493 APNIC Region origin ASes present in the Internet Routing Table: 11963 APNIC Prefixes per ASN: 19.00 APNIC Region origin ASes announcing only one prefix: 3393 APNIC Region transit ASes present in the Internet Routing Table: 1675 Average APNIC Region AS path length visible: 4.5 Max APNIC Region AS path length visible: 37 Number of APNIC region 32-bit ASNs visible in the Routing Table: 7118 Number of APNIC addresses announced to Internet: 773766656 Equivalent to 46 /8s, 30 /16s and 190 /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-147769 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: 251907 Total ARIN prefixes after maximum aggregation: 115275 ARIN Deaggregation factor: 2.19 Prefixes being announced from the ARIN address blocks: 251845 Unique aggregates announced from the ARIN address blocks: 120093 ARIN Region origin ASes present in the Internet Routing Table: 18911 ARIN Prefixes per ASN: 13.32 ARIN Region origin ASes announcing only one prefix: 6886 ARIN Region transit ASes present in the Internet Routing Table: 1956 Average ARIN Region AS path length visible: 3.9 Max ARIN Region AS path length visible: 28 Number of ARIN region 32-bit ASNs visible in the Routing Table: 4111 Number of ARIN addresses announced to Internet: 1284624128 Equivalent to 76 /8s, 145 /16s and 207 /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: 240497 Total RIPE prefixes after maximum aggregation: 112388 RIPE Deaggregation factor: 2.14 Prefixes being announced from the RIPE address blocks: 236680 Unique aggregates announced from the RIPE address blocks: 144864 RIPE Region origin ASes present in the Internet Routing Table: 28032 RIPE Prefixes per ASN: 8.44 RIPE Region origin ASes announcing only one prefix: 12053 RIPE Region transit ASes present in the Internet Routing Table: 3903 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 29 Number of RIPE region 32-bit ASNs visible in the Routing Table: 10392 Number of RIPE addresses announced to Internet: 711440512 Equivalent to 42 /8s, 103 /16s and 184 /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: 111606 Total LACNIC prefixes after maximum aggregation: 26532 LACNIC Deaggregation factor: 4.21 Prefixes being announced from the LACNIC address blocks: 112559 Unique aggregates announced from the LACNIC address blocks: 47147 LACNIC Region origin ASes present in the Internet Routing Table: 10785 LACNIC Prefixes per ASN: 10.44 LACNIC Region origin ASes announcing only one prefix: 2639 LACNIC Region transit ASes present in the Internet Routing Table: 2107 Average LACNIC Region AS path length visible: 4.9 Max LACNIC Region AS path length visible: 29 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 8444 Number of LACNIC addresses announced to Internet: 176280064 Equivalent to 10 /8s, 129 /16s and 210 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-272796 + 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: 26277 Total AfriNIC prefixes after maximum aggregation: 5204 AfriNIC Deaggregation factor: 5.05 Prefixes being announced from the AfriNIC address blocks: 34200 Unique aggregates announced from the AfriNIC address blocks: 10999 AfriNIC Region origin ASes present in the Internet Routing Table: 1543 AfriNIC Prefixes per ASN: 22.16 AfriNIC Region origin ASes announcing only one prefix: 542 AfriNIC Region transit ASes present in the Internet Routing Table: 306 Average AfriNIC Region AS path length visible: 5.1 Max AfriNIC Region AS path length visible: 25 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 874 Number of AfriNIC addresses announced to Internet: 108186624 Equivalent to 6 /8s, 114 /16s and 204 /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 8037 9000 57 CMNET-GD Guangdong Mobile Communication 7545 5824 785 678 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4711 4192 74 ERX-CERNET-BKB China Education and Rese 7552 3661 1330 20 VIETEL-AS-AP Viettel Group, VN 7713 3507 1023 56 TELKOMNET-AS-AP PT Telekomunikasi Indon 45899 2900 1897 56 VNPT-AS-VN VNPT Corp, VN 4766 2502 11120 582 KIXS-AS-KR Korea Telecom, KR 9498 2364 502 239 BBIL-AP BHARTI Airtel Ltd., IN 45090 2127 1198 75 CNNIC-TENCENT-NET-AP Shenzhen Tencent C 4755 2115 437 192 TATACOMM-AS TATA Communications formerl 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 16509 5576 9716 2467 AMAZON-02, US 11492 4650 308 759 CABLEONE, US 22773 4028 3035 307 ASN-CXA-ALL-CCI-22773-RDC, US 7155 3961 264 32 VIASAT-SP-BACKBONE, US 16625 3590 1854 2500 AKAMAI-AS, US 6327 3368 1318 66 SHAW, CA 30036 2593 375 163 MEDIACOM-ENTERPRISE-BUSINESS, US 209 2508 5029 448 CENTURYLINK-US-LEGACY-QWEST, US 20115 2241 3032 504 CHARTER-20115, US 5972 2166 489 787 DNIC-ASBLK-05800-06055, 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 6894 1726 143 UNI2-AS, ES 20940 3796 3348 215 AKAMAI-ASN1, NL 8551 3291 378 39 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 39891 3269 187 23 ALJAWWALSTC-AS, SA 12389 2907 2279 895 ROSTELECOM-AS, RU 9009 2508 262 1333 M247, GB 34984 2224 357 598 TELLCOM-AS, TR 61317 1776 267 976 ASDETUK www.heficed.com, GB 58224 1639 891 570 TCI, IR 13188 1610 100 27 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 8553 3454 577 Uninet S.A. de C.V., MX 10620 3416 523 677 Telmex Colombia S.A., CO 11830 2497 369 62 Instituto Costarricense de Electricidad 13999 1717 384 465 Mega Cable, S.A. de C.V., MX 6503 1514 359 477 Axtel, S.A.B. de C.V., MX 28573 1463 2304 231 CLARO S.A., BR 3816 1240 652 152 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 26615 1131 2351 134 TIM SA, BR 6147 1086 369 22 Telefonica del Peru S.A.A., PE 11172 957 111 70 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 1633 393 20 LINKdotNET-AS, EG 24835 1463 499 33 RAYA-AS, EG 36992 1289 1417 272 ETISALAT-MISR, EG 36903 1183 537 110 MT-MPLS, MA 29571 781 68 11 ORANGE-COTE-IVOIRE, CI 6713 612 1863 34 IAM-AS, MA 36935 578 522 40 Vodafone-, EG 15399 502 49 29 WANANCHI-, KE 37342 469 32 1 MOVITEL, MZ 2018 343 319 74 TENET-1, ZA 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 8553 3454 577 Uninet S.A. de C.V., MX 9808 8037 9000 57 CMNET-GD Guangdong Mobile Communication 12479 6894 1726 143 UNI2-AS, ES 7545 5824 785 678 TPG-INTERNET-AP TPG Telecom Limited, AU 16509 5576 9716 2467 AMAZON-02, US 4538 4711 4192 74 ERX-CERNET-BKB China Education and Rese 11492 4650 308 759 CABLEONE, US 22773 4028 3035 307 ASN-CXA-ALL-CCI-22773-RDC, US 7155 3961 264 32 VIASAT-SP-BACKBONE, US 20940 3796 3348 215 AKAMAI-ASN1, NL Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 9808 8037 7980 CMNET-GD Guangdong Mobile Communication Co.Ltd. 12479 6894 6751 UNI2-AS, ES 7545 5824 5146 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4711 4637 ERX-CERNET-BKB China Education and Research Net 7155 3961 3929 VIASAT-SP-BACKBONE, US 11492 4650 3891 CABLEONE, US 22773 4028 3721 ASN-CXA-ALL-CCI-22773-RDC, US 7552 3661 3641 VIETEL-AS-AP Viettel Group, VN 20940 3796 3581 AKAMAI-ASN1, NL 7713 3507 3451 TELKOMNET-AS-AP PT Telekomunikasi Indonesia, ID 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 46887 LIGHTOWER, US 18604 UNALLOCATED 8.25.204.0/24 3356 LEVEL3, US 394936 UNALLOCATED 8.33.224.0/24 174 COGENT-174, US 54338 UNALLOCATED 8.33.241.0/24 6461 ZAYO-6461, US 23061 UNALLOCATED 8.39.119.0/24 3356 LEVEL3, US 1782 UNALLOCATED 8.42.19.0/24 46887 LIGHTOWER, 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 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.132.208.0/24 Origin: 7850 CITYLINKFIBER, US 23.132.208.0/24 Transit: 15164 UPNLLC, US 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: 174 COGENT-174, US 41.57.124.0/23 Origin: 37442 UNASSIGNED 41.57.124.0/23 Transit: 37204 TELONE, ZW 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:16 /9:13 /10:41 /11:100 /12:301 /13:596 /14:1215 /15:2037 /16:13419 /17:8267 /18:14009 /19:25398 /20:42555 /21:50911 /22:107040 /23:92168 /24:503459 /25:1450 /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 5819 6894 UNI2-AS, ES 11492 3602 4650 CABLEONE, US 6327 3176 3368 SHAW, CA 7155 3049 3961 VIASAT-SP-BACKBONE, US 22773 2998 4028 ASN-CXA-ALL-CCI-22773-RDC, US 8151 2943 8553 Uninet S.A. de C.V., MX 39891 2805 3269 ALJAWWALSTC-AS, SA 8551 2757 3291 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 30036 2247 2593 MEDIACOM-ENTERPRISE-BUSINESS, US 11830 1931 2497 Instituto Costarricense de Electricidad y Telec Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1913 2:1098 3:145 4:20 5:3599 6:83 7:5 8:1543 9:1 11:164 12:1735 13:385 14:2285 15:104 16:23 17:355 18:113 20:126 21:4 22:188 23:5101 24:2451 25:2 27:2532 29:19 31:2360 32:113 34:1 35:47 36:1728 37:3840 38:2237 39:641 40:165 41:3795 42:985 43:2060 44:286 45:15395 46:3737 47:354 48:7 49:1632 50:1813 51:101 52:1284 54:249 55:747 56:4 57:54 58:1736 59:1191 60:933 61:2314 62:2294 63:1955 64:5367 65:2363 66:4992 67:2868 68:1165 69:4121 70:1363 71:677 72:3154 74:2626 75:1499 76:696 77:2036 78:1679 79:2622 80:1872 81:1554 82:1399 83:1153 84:1310 85:2762 86:719 87:1826 88:973 89:3032 90:516 91:7381 92:1828 93:2551 94:3156 95:3500 96:1304 97:345 98:978 99:959 100:76 101:1057 102:1682 103:26934 104:4021 105:436 106:827 107:2335 108:729 109:3865 110:2047 111:3131 112:1938 113:1412 114:1473 115:1929 116:1872 117:2409 118:2305 119:1892 120:1555 121:1081 122:2524 123:2164 124:1605 125:2080 128:1347 129:1369 130:882 131:2027 132:773 133:362 134:1852 135:312 136:785 137:849 138:2394 139:1189 140:757 141:1215 142:1201 143:1351 144:1269 145:325 146:1517 147:1404 148:2159 149:1509 150:820 151:1086 152:1638 153:428 154:3056 155:1337 156:1761 157:1222 158:990 159:2027 160:2360 161:1254 162:3389 163:1097 164:1548 165:1430 166:593 167:1656 168:3635 169:692 170:4314 171:806 172:2755 173:2874 174:1001 175:1106 176:3282 177:4451 178:3001 179:1886 180:2245 181:2654 182:3252 183:2021 184:2417 185:18848 186:4240 187:3130 188:3341 189:2877 190:8688 191:1349 192:10724 193:8303 194:6784 195:4850 196:2908 197:2117 198:6030 199:5935 200:7363 201:5228 202:10527 203:10025 204:4525 205:3389 206:3784 207:3365 208:4036 209:4755 210:4180 211:2360 212:3769 213:3394 214:1168 215:64 216:6375 217:2588 218:1219 219:673 220:1958 221:980 222:854 223:2047 End of report

1 0

(Free)RADIUS Front-End
by Mark Tinka 17 Sep '21

17 Sep '21

Hi all. I haven't been in the space in yonks, but I'm having to look into it for an acquisition. What's the latest on front-end panels for RADIUS, specifically, FreeRADIUS? I fumbled around with Daloradius some years back, but mainly to manage some pfSense captive portals for guest wi-fi VLAN's at the office. I found these chaps who make some basic comparisons between themselves and what is out there: https://www.cloudradius.com/is-there-a-freeradius-gui/ Grateful to get feedback, on- and off-list, about what folk are doing with this tech. nowadays. Enterpri$e options are welcome too, but essentially, we are just looking for an easy on-premise (no cloud, please; I consider RADIUS critical network infrastructure) pretty GUI system that can make the engineers, NOC, provisioning and billing teams happy; and especially, the customers, of course. I don't trust myself with Google to avoid snake oil in my search :-). All help appreciated. Thanks. Mark.

1 0

Re: Comcast Customer Owned Modem Firmware : WAS : Xfi Advances Security (comcast)
by Livingood, Jason 17 Sep '21

17 Sep '21

> Does Comcast actually allow customers who own their own modems full management of the modem firmware? As far as I have been aware since my time at Adelphia 20-odd years ago, that has never been allowed by provider; all users of a given model had the same firmware enforced, customer owned or leased didn't matter. No and I am not aware of any DOCSIS network operator that does permit that. But we are very responsive to firmware updates from the OEMs and try to quickly test & deploy those. See for example: https://kb.netgear.com/000036375/What-s-the-latest-firmware-version-of-my-N… Thx Jason

1 0

Xfi Advances Security (comcast)
by Jason Kuehl 16 Sep '21

16 Sep '21

For whatever reason Comcast Xfinity is blocking my VPN URL. I've started the process to unblock, and I'm trying to get a hold of their security team to resolve this. I've been bounced around all morning. Does anyone have a contact at Comcast that can whitelist a URL or get me to a team that can understand what is going on for the block to happen? -- Sincerely, Jason W Kuehl Cell 920-419-8983 jason.w.kuehl(a)gmail.com

10 16

Fastly Peering Contact?
by Bryan Holloway 16 Sep '21

16 Sep '21

Hey all ... looking for a Fastly (54113) peering contact that might be able to get me in touch with the right folks to do stuff. E-mails to the 'policy' peeringdb contact don't seem to be getting through. Thanks! - bryan

2 1

Webinar TODAY + VIDEO - Ep.1 "Internet Innovators" + more
by Nanog News 16 Sep '21

16 Sep '21

*🖥️ Webinar TODAYJoin us for a Fireside Chat w/ CENIC Nick Plunkett * *Date + Time:* September 16, 11am - 1pm PST / 2pm - 4pm EST *Agenda: *Join us for a fireside chat discussion. We will talk about several topics including: - The path taken to a tech career - What is CENIC - Opportunities for volunteer or educational work *Speaker: *Nick Plunkett, Network Interconnection Engineer - Internet Services at CENIC *REGISTER NOW <https://www.nanog.org/events/webinar-fireside-cenic/> * *VIDEO | Watch Ep.1 "Internet Innovators" w/ Vint Cerf* *NANOG Discusses Past, Present, Future of Internet with a Internet Legend * Have you checked out our new web series *ft. the brightest and boldest tech minds* of our time? Welcome to NANOG’s* Internet Innovators*! *Join us,* every month as we look to the past, present and future of the Internet and talk to the innovators who were actually there. *Don't have the time for a full episode? *Watch S1, Ep.1 CLIP - <https://youtu.be/yR4RbNR48T8>A legendary “father” of Internet Vint Cerf discusses “what it takes to be revolutionary.” *STAY TUNED. *Join us Wednesday, Sept. 30 for Ep. 2 of *Internet Innovators.* The candid, entertaining and never one to not address the elephant in the room, Chief scientist of *Telstra Internet *Geoff Huston will have an intimate conversation about why he thinks the Internet is busted. *WATCH Ep.1 NOW <https://www.nanog.org/news-stories/nanog-tv/internet-innovators/vint-cerf-i…>* *Now Accepting Applications for NANOG 83 Peering Coordination Forum * *The Peering Coordination Forum* is a 90-minute session that will take place Nov. 1 during the NANOG 83 conference. The forum is an opportunity for attendees to meet + network with others in the peering community present at NANOG. *NANOG 83 Peering Coordination Forum *applications will remain open until we have 20 applications. If you are a Peering Representative with a table, you will have the opportunity to request a plexiglass shield for your table. *APPLY NOW* <https://nanog.org/events/nanog-83/peering-forum/> *🕺👏 Hybrid NANOG 83 is Just Around the Corner * Have you heard? NANOG is now a hybrid <https://www.nanog.org/stories/hybrid-event-faqs/> platform, providing equally robust programming virtually and/or in-person. *Join us *from the comfort of your laptop or see us in-person in Minneapolis, MN on Nov 1 - 3. We can't wait to see you! *REGISTER NOW * <https://www.nanog.org/events/nanog-83/>

1 0

Re: IPv6 woes - RFC
by Michael Thomas 16 Sep '21

16 Sep '21

On 9/14/21 12:44 AM, Eliot Lear wrote: > > There were four proposals for the IPng: > > * NIMROD, PIP, SIP, and TUBA > > SIP was the one that was chosen, supported by endpoint manufacturers > such as Sun and SGI, and it was the MOST compatible. Operators and > router manufacturers at the time pushed TUBA, which was considerably > less compatible with the concepts used in v4 because of variable > length addressing. If we endpoints had some notion that v6 would > take as long as it has to diffuse, perhaps we all might have thought > differently. I don't know. > > So I'm beginning to think that the reason ipv6 didn't take off is one simple thing: time. All of the infighting took years and by then that ship had long sailed. The basic mechanisms for v6 for hosts were not complicated and all of the second system syndrome fluff could be mostly be ignored or implemented when it actually made sense. If this had been settled within a year instead of five, there may have been a chance especially since specialized hardware was either nonexistent or just coming on the scene. I mean, Kalpana was still pretty new when a lot of this was being first discussed from what I can tell. Maybe somebody else knows when hardware routing came on the scene but there was still lots of software forwarding planes when I started at Cisco in 1998 just as broadband was starting to flow. The IETF was a victim of its own dysfunction, film at 11 and now we're having a 30 year reunion. Mike

3 3