- Test - lists.nanog.org

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 24 Mar '23

24 Mar '23

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 25 Mar, 2023 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: 916706 Prefixes after maximum aggregation (per Origin AS): 347952 Deaggregation factor: 2.63 Unique aggregates announced (without unneeded subnets): 447433 Total ASes present in the Internet Routing Table: 74277 Prefixes per ASN: 12.34 Origin-only ASes present in the Internet Routing Table: 63736 Origin ASes announcing only one prefix: 26191 Transit ASes present in the Internet Routing Table: 10541 Transit-only ASes present in the Internet Routing Table: 437 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 55 Max AS path prepend of ASN (265020) 50 Prefixes from unregistered ASNs in the Routing Table: 1062 Number of instances of unregistered ASNs: 1081 Number of 32-bit ASNs allocated by the RIRs: 41520 Number of 32-bit ASNs visible in the Routing Table: 34390 Prefixes from 32-bit ASNs in the Routing Table: 168886 Number of bogon 32-bit ASNs visible in the Routing Table: 64 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 504 Number of addresses announced to Internet: 3063124224 Equivalent to 182 /8s, 147 /16s and 145 /24s Percentage of available address space announced: 82.7 Percentage of allocated address space announced: 82.7 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: 306925 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 242068 Total APNIC prefixes after maximum aggregation: 69187 APNIC Deaggregation factor: 3.50 Prefixes being announced from the APNIC address blocks: 236645 Unique aggregates announced from the APNIC address blocks: 98042 APNIC Region origin ASes present in the Internet Routing Table: 13391 APNIC Prefixes per ASN: 17.67 APNIC Region origin ASes announcing only one prefix: 3931 APNIC Region transit ASes present in the Internet Routing Table: 1800 Average APNIC Region AS path length visible: 4.5 Max APNIC Region AS path length visible: 38 Number of APNIC region 32-bit ASNs visible in the Routing Table: 8674 Number of APNIC addresses announced to Internet: 773729408 Equivalent to 46 /8s, 30 /16s and 44 /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: 268307 Total ARIN prefixes after maximum aggregation: 122098 ARIN Deaggregation factor: 2.20 Prefixes being announced from the ARIN address blocks: 270513 Unique aggregates announced from the ARIN address blocks: 130377 ARIN Region origin ASes present in the Internet Routing Table: 19069 ARIN Prefixes per ASN: 14.19 ARIN Region origin ASes announcing only one prefix: 6964 ARIN Region transit ASes present in the Internet Routing Table: 1967 Average ARIN Region AS path length visible: 3.7 Max ARIN Region AS path length visible: 24 Number of ARIN region 32-bit ASNs visible in the Routing Table: 4765 Number of ARIN addresses announced to Internet: 1286019328 Equivalent to 76 /8s, 167 /16s and 25 /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: 258329 Total RIPE prefixes after maximum aggregation: 121641 RIPE Deaggregation factor: 2.12 Prefixes being announced from the RIPE address blocks: 254652 Unique aggregates announced from the RIPE address blocks: 157366 RIPE Region origin ASes present in the Internet Routing Table: 28296 RIPE Prefixes per ASN: 9.00 RIPE Region origin ASes announcing only one prefix: 12048 RIPE Region transit ASes present in the Internet Routing Table: 3961 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 38 Number of RIPE region 32-bit ASNs visible in the Routing Table: 11111 Number of RIPE addresses announced to Internet: 718214272 Equivalent to 42 /8s, 207 /16s and 20 /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: 117659 Total LACNIC prefixes after maximum aggregation: 28455 LACNIC Deaggregation factor: 4.13 Prefixes being announced from the LACNIC address blocks: 116993 Unique aggregates announced from the LACNIC address blocks: 49024 LACNIC Region origin ASes present in the Internet Routing Table: 10965 LACNIC Prefixes per ASN: 10.67 LACNIC Region origin ASes announcing only one prefix: 2641 LACNIC Region transit ASes present in the Internet Routing Table: 2278 Average LACNIC Region AS path length visible: 4.9 Max LACNIC Region AS path length visible: 55 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 8762 Number of LACNIC addresses announced to Internet: 176649984 Equivalent to 10 /8s, 135 /16s and 119 /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: 29281 Total AfriNIC prefixes after maximum aggregation: 5801 AfriNIC Deaggregation factor: 5.05 Prefixes being announced from the AfriNIC address blocks: 37399 Unique aggregates announced from the AfriNIC address blocks: 12219 AfriNIC Region origin ASes present in the Internet Routing Table: 1735 AfriNIC Prefixes per ASN: 21.56 AfriNIC Region origin ASes announcing only one prefix: 607 AfriNIC Region transit ASes present in the Internet Routing Table: 333 Average AfriNIC Region AS path length visible: 4.9 Max AfriNIC Region AS path length visible: 37 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 1078 Number of AfriNIC addresses announced to Internet: 108126976 Equivalent to 6 /8s, 113 /16s and 227 /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 9511 8884 51 CHINAMOBILE-CN China Mobile Communicati 7545 5755 786 691 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4867 4192 75 ERX-CERNET-BKB China Education and Rese 7713 3530 1043 65 TELKOMNET-AS-AP PT Telekomunikasi Indon 7552 3454 1331 21 VIETEL-AS-AP Viettel Group, VN 45899 3384 1874 95 VNPT-AS-VN VNPT Corp, VN 9498 2853 491 237 BBIL-AP BHARTI Airtel Ltd., IN 4766 2558 11252 593 KIXS-AS-KR Korea Telecom, KR 24560 2361 837 441 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd 45090 2184 1438 79 TENCENT-NET-AP Shenzhen Tencent Compute 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 8118 10764 2897 AMAZON-02, US 11492 4534 300 620 CABLEONE, US 7155 3962 279 45 VIASAT-SP-BACKBONE, US 22773 3622 3062 292 ASN-CXA-ALL-CCI-22773-RDC, US 6327 3514 1320 64 SHAW, CA 16625 3157 1590 2338 AKAMAI-AS, US 749 3037 50520 2304 DNIC-AS-00749, US 396982 2624 3588 357 GOOGLE-CLOUD-PLATFORM, US 7018 2553 24117 1559 ATT-INTERNET4, US 30036 2509 361 483 MEDIACOM-ENTERPRISE-BUSINESS, 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 7165 1705 149 UNI2-AS, ES 39891 4833 286 59 ALJAWWALSTC-AS, SA 20940 4044 3399 164 AKAMAI-ASN1, NL 8551 3891 370 37 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12389 2957 2292 913 ROSTELECOM-AS, RU 9009 2664 252 1395 M247, RO 34984 2267 359 612 TELLCOM-AS, TR 6849 2135 339 19 UKRTELNET, UA 58224 1849 949 547 TCI, IR 13188 1607 100 27 TRIOLAN, UA 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 11197 3340 579 Uninet S.A. de C.V., MX 10620 3498 506 850 Telmex Colombia S.A., CO 13999 2295 366 610 Mega Cable, S.A. de C.V., MX 11830 2263 369 64 Instituto Costarricense de Electricidad 28573 1330 2324 246 Claro NXT Telecomunicacoes Ltda, BR 3816 1303 767 159 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6503 1299 339 514 Axtel, S.A.B. de C.V., MX 6147 1130 370 22 Telefonica del Peru S.A.A., PE 11664 1102 180 454 Techtel LMDS Comunicaciones Interactiva 26615 1030 2498 45 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 24863 1575 393 19 LINKdotNET-AS, EG 24835 1542 533 30 RAYA-AS, EG 36992 1343 1518 275 ETISALAT-MISR, EG 36903 1242 550 99 MT-MPLS, MA 29571 1019 67 53 ORANGE-COTE-IVOIRE, CI 36935 880 520 42 Vodafone-, EG 6713 549 1861 34 IAM-AS, MA 15399 528 54 47 WANANCHI-, KE 37342 493 32 1 MOVITEL, MZ 24757 487 73 5 EthioNet-AS, ET 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 11197 3340 579 Uninet S.A. de C.V., MX 9808 9511 8884 51 CHINAMOBILE-CN China Mobile Communicati 16509 8118 10764 2897 AMAZON-02, US 12479 7165 1705 149 UNI2-AS, ES 7545 5755 786 691 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4867 4192 75 ERX-CERNET-BKB China Education and Rese 39891 4833 286 59 ALJAWWALSTC-AS, SA 11492 4534 300 620 CABLEONE, US 20940 4044 3399 164 AKAMAI-ASN1, NL 7155 3962 279 45 VIASAT-SP-BACKBONE, 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 9511 9460 CHINAMOBILE-CN China Mobile Communications Grou 12479 7165 7016 UNI2-AS, ES 16509 8118 5221 AMAZON-02, US 7545 5755 5064 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4867 4792 ERX-CERNET-BKB China Education and Research Net 39891 4833 4774 ALJAWWALSTC-AS, SA 7155 3962 3917 VIASAT-SP-BACKBONE, US 11492 4534 3914 CABLEONE, US 20940 4044 3880 AKAMAI-ASN1, NL 8551 3891 3854 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 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 3507 UNALLOCATED 5.105.166.0/24 213035 AS-SERVERION Serverion B.V., 398083 UNALLOCATED 5.133.124.0/24 399587 UT, US 33123 UNALLOCATED 8.10.69.0/24 11168 SCC, US 12169 UNALLOCATED 8.15.207.0/24 32787 PROLEXIC-TECHNOLOGIES-DDOS-M 53775 UNALLOCATED 8.20.88.0/24 7029 WINDSTREAM, US 62828 UNALLOCATED 8.21.130.0/24 3356 LEVEL3, US 393266 UNALLOCATED 8.23.52.0/24 46887 LIGHTOWER, US 396894 UNALLOCATED 8.28.201.0/24 46887 LIGHTOWER, US 394936 UNALLOCATED 8.33.224.0/24 22442 HOU-PHONOSCOPE, US 54338 UNALLOCATED 8.33.241.0/24 6461 ZAYO-6461, 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.131.185.0/24 Origin: 174 COGENT-174, US 23.131.185.0/24 Transit: 2516 KDDI KDDI CORPORATION, JP 23.131.186.0/24 Origin: 174 COGENT-174, US 23.131.186.0/24 Transit: 2516 KDDI KDDI CORPORATION, JP 23.131.187.0/24 Origin: 174 COGENT-174, US 23.131.187.0/24 Transit: 2516 KDDI KDDI CORPORATION, JP 23.131.188.0/24 Origin: 174 COGENT-174, US 23.131.188.0/24 Transit: 2516 KDDI KDDI CORPORATION, JP 23.136.112.0/24 Origin: 54835 UNASSIGNED 23.136.112.0/24 Transit: 21559 OSNET, PR 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:39 /11:103 /12:299 /13:578 /14:1198 /15:2040 /16:13480 /17:8279 /18:13859 /19:25215 /20:44274 /21:51595 /22:109669 /23:97628 /24:547681 /25:740 /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 6223 7165 UNI2-AS, ES 8151 5163 11197 Uninet S.A. de C.V., MX 39891 3632 4833 ALJAWWALSTC-AS, SA 11492 3442 4534 CABLEONE, US 8551 3363 3891 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 6327 3323 3514 SHAW, CA 7155 3037 3962 VIASAT-SP-BACKBONE, US 22773 2677 3622 ASN-CXA-ALL-CCI-22773-RDC, US 30036 2166 2509 MEDIACOM-ENTERPRISE-BUSINESS, US 10620 2052 3498 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:1703 2:1230 3:170 4:5 5:4458 6:122 7:6 8:1553 9:1 11:172 12:1577 13:392 14:2315 15:295 16:135 17:368 18:402 20:248 21:4 22:188 23:6138 24:2611 25:6 27:2493 29:19 31:2526 32:101 34:10 35:107 36:1913 37:4637 38:4378 39:807 40:151 41:3987 42:988 43:2332 44:309 45:16497 46:4247 47:377 49:1750 50:1835 51:570 52:1585 54:388 55:766 56:8 57:89 58:1752 59:1130 60:974 61:2440 62:2651 63:1909 64:5672 65:2317 66:4942 67:3016 68:1368 69:4178 70:1257 71:669 72:2972 74:2601 75:1463 76:607 77:2440 78:1861 79:3161 80:2078 81:1738 82:1499 83:1266 84:1538 85:3004 86:744 87:1963 88:1244 89:3625 90:613 91:7690 92:2035 93:2587 94:3581 95:3974 96:1329 97:335 98:1158 99:745 100:73 101:1070 102:2637 103:31162 104:4608 105:483 106:908 107:2557 108:987 109:4402 110:2080 111:3244 112:2055 113:1559 114:1634 115:2023 116:1923 117:2542 118:2278 119:1980 120:1779 121:1113 122:2601 123:2182 124:1619 125:2487 128:1315 129:1073 130:1009 131:2006 132:801 133:421 134:1901 135:300 136:862 137:934 138:2555 139:1526 140:1221 141:1494 142:1441 143:1500 144:1170 145:356 146:1939 147:1568 148:2336 149:1954 150:874 151:1154 152:1842 153:488 154:4280 155:1412 156:1683 157:1280 158:1045 159:2271 160:2537 161:1516 162:3538 163:1505 164:1593 165:1681 166:881 167:1712 168:3880 169:929 170:4610 171:882 172:3523 173:2949 174:1020 175:1160 176:3680 177:4602 178:3640 179:2198 180:2399 181:3424 182:3361 183:1932 184:2350 185:20169 186:4686 187:3975 188:4086 189:3613 190:9150 191:1441 192:10953 193:8847 194:7278 195:5166 196:3099 197:2394 198:5957 199:6096 200:7879 201:5877 202:10753 203:10217 204:4621 205:3542 206:3943 207:3456 208:4081 209:4883 210:4435 211:2497 212:4117 213:3535 214:1083 215:60 216:6610 217:2678 218:1290 219:580 220:2012 221:974 222:888 223:2166 End of report

1 0

Hulu US Cogent IPs problem
by Jose Montero Martín (TRABAJO) 24 Mar '23

24 Mar '23

Good morning, Our customers are facing issues accessing Hulu from our Cogent IPs geolocated in the US. Every time they try to log in they receive the following prompted message: "Something went wrong. Please try again later" With a big black button "Log out and try again" These IPs are perfectly located but we are still having problems. I read all the thread related in the newsletter and also read the https://thebrotherswisp.com/index.php/geo-and-vpn/ webpage. I also contacted Hulu via customer support and ipadmin(a)hulu.com, also using Digital Envoy contact webpage and e-mail. I always receive an e-mail informing us that there is no location or proxy problem either. Even further, I tried with another Cogent IP range also located in the US with success. Anyone who can help me even off the list would be appreciated. Kind regards,

2 1

Spectrum Engineer
by Dennis Burgess 23 Mar '23

23 Mar '23

Can someone from spectrum give me a call or shoot me a email. We have a customer that is hard down, BGP is up, we are advertising the prefix to you but its not making its way out on the public internet. [LTI-Full_175px] Dennis Burgess Mikrotik : Trainer, Network Associate, Routing Engineer, Wireless Engineer, Traffic Control Engineer, Inter-Networking Engineer, Security Engineer, Enterprise Wireless Engineer Hurricane Electric: IPv6 Sage Level Cambium: ePMP Author of "Learn RouterOS- Second Edition" Link Technologies, Inc -- Mikrotik & WISP Support Services Office: 314-735-0270 Website: http://www.linktechs.net<http://www.linktechs.net/> Create Wireless Coverage's with www.towercoverage.com Need MikroTik Cloud Management: https://cloud.linktechs.net

2 1

Searchable archives of the list?
by Joel M Snyder 23 Mar '23

23 Mar '23

This seems an absurd question but … “where are the searchable archives of this list?” I have found an innumerable set of archives and copies of archives broken into months, but I cannot find a way to search the content of the list archive (short of downloading the archives and grepping from there). Is there a searchable archive someplace maintained by nanog? And if so… how about updating the nanog web pages about this list with a pointer? And finally, the question I was searching to avoid asking on the list: does anyone have any experience, good or bad, with leasing out unused IPv4 space through ipway? Thanks, jms --- Joel M Snyder - Opus One - jms(a)Opus1.COM

5 5

ElastiFlow Getting Started?
by Mike Hammett 23 Mar '23

23 Mar '23

Does anyone know of a getting started guide for the latest release of ElastiFlow? I went the docker path because I recall setting up a system before that had a lot of work with dependencies and getting things tied together. I got it installed and it seems to run without error, but there's nothing telling me how to actually access the UI. Something is listening on port 8080, but it just gives me a 404. That seems to be pertinent to the API, which I don't care about at this time. That seems like low hanging fruit that the documentation misses. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest-IX http://www.midwest-ix.com

4 4

Re: CUPS in a BNG?
by Tom Mitchell 22 Mar '23

22 Mar '23

OK - That makes sense. For scaling a CP, it only about redundancy, correct, but with the DP it's really about scaling up and out. But still, a CP is no longer on the bus with the DP, nor on the network. It's on the WAN/Internet, and latencies are orders of magnitude greater. Is anybody doing this and are those latencies acceptable? On Wed, Mar 22, 2023 at 2:59 PM Joel Halpern <jmh(a)joelhalpern.com> wrote: > With a reasonable design, it separates the scale issues of the control > plane from the scale issues of the data plane. And since the relationship > between those two scale factors is different for different deployments, it > allows you as an operator to build for your needs. It also, with suitable > designs separates the failure modes. > > Whether either of those applies in your case probably depends upon your > needs and what vendors you find useful. > > Yours, > > Joel > On 3/22/2023 5:53 PM, Tom Mitchell wrote: > > What is it about the architecture that makes it a preferred solution. I > get that centralizing the user databases makes sense, but why the control > plane. What benefit does that have? > > -- Tom > > > On Wed, Mar 22, 2023 at 2:17 PM <brian.johnson(a)netgeek.us> wrote: > >> The CUPS makes a lot of sense for this application. Latency is dependent >> on the design, and equipment used. I’ve seen/done several designs for this >> using two different vendors equipment and two different BNG software >> stacks. >> >> When I do a design for BNG from scratch, this is how I do it now. :) >> >> As always… YMMV. >> >> - Brian >> >> On Mar 22, 2023, at 4:02 PM, Tom Mitchell <tmitchell(a)netelastic.com> >> wrote: >> >> Anyone have any thoughts on this CUPS thing? I have a customer asking, >> but it seems the lack of CP resiliency and additional latency between the >> DP and CP make this a really dumb idea. Has anyone tried it? Does it make >> any sense? >> >> Thanks! >> >> >>

1 0

CUPS in a BNG?
by Tom Mitchell 22 Mar '23

22 Mar '23

Anyone have any thoughts on this CUPS thing? I have a customer asking, but it seems the lack of CP resiliency and additional latency between the DP and CP make this a really dumb idea. Has anyone tried it? Does it make any sense? Thanks!

2 2

Spamhaus flags any IP announced by our ASN as a criminal network
by Brandon Zhi 22 Mar '23

22 Mar '23

Hello guy, We recently discovered that any IP address announced by our ASN is blacklisted by Spamhaus, even if we only announced it but not use it. I would like to ask if this is manually set by Spamhaus or is the system misjudgment? Has anyone encountered the same situation as us? Best, *Brandon Zhi* HUIZE LTD www.huize.asia <https://huize.asia/>| www.ixp.su | Twitter This e-mail and any attachments or any reproduction of this e-mail in whatever manner are confidential and for the use of the addressee(s) only. HUIZE LTD can’t take any liability and guarantee of the text of the email message and virus.

14 25

1.1.1.1 support?
by Saku Ytti 22 Mar '23

22 Mar '23

Am I correct to understand that 1.1.1.1 only does support via community forum? They had just enough interest in the service to collect user data to monetise, but 0 interest in trying to figure out how to detect and solve problems? Why not build a web form where they ask you to explain what is not working, in terms of automatically testable. Like no A record for X. Then after you submit this form, they test against all 1.1.1.1 and some 9.9.9.9 and 8.8.8.8 and if they find a difference in behaviour, the ticket is accepted and sent to someone who understands DNS? If there is no difference in behaviour, direct people to community forums. This trivial, cheap and fast to produce support channel would ensure virtually 0 trash support cases, so you wouldn't even have to hire people to support your data collection enterprise. Very obviously they selfishly had no interest in ensuring 1.1.1.1 actually works, as long as they are getting the data. I do not know how to characterise this as anything but unethical. https://community.cloudflare.com/t/1-1-1-1-wont-resolve-www-moi-gov-cy-in-l… https://community.cloudflare.com/t/1-1-1-1-failing-to-resolve/474228 If you can't due to resources or competence support DNS, do not offer one. -- ++ytti, cake having and cake eating user

6 9

Re: Verizon/Qwest single end-user difficulty vs Xfinity (was Re: NANOG Digest, Vol 182, Issue 14)
by Tom Daly 21 Mar '23

21 Mar '23

Jeff, Since you are using bridge mode, try adjusting down the MTU supported through the network. We have observed that a realistic MTU for Verizon 5G home internet is about 1428 bytes. Good luck, Tom On Sun, Mar 19, 2023 at 8:00 AM <nanog-request(a)nanog.org> wrote: > Send NANOG mailing list submissions to > nanog(a)nanog.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://mailman.nanog.org/mailman/listinfo/nanog > or, via email, send a message with subject or body 'help' to > nanog-request(a)nanog.org > > You can reach the person managing the list at > nanog-owner(a)nanog.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of NANOG digest..." > > > Today's Topics: > > 1. Spamhaus flags any IP announced by our ASN as a criminal > network (Brandon Zhi) > 2. Verizon/Qwest single end-user difficulty vs Xfinity (Jeff Woolsey) > 3. Re: Spamhaus flags any IP announced by our ASN as a criminal > network (Tom Beecher) > 4. Re: Verizon/Qwest single end-user difficulty vs Xfinity > (Darin Steffl) > 5. Re: Verizon/Qwest single end-user difficulty vs Xfinity (Joe) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 18 Mar 2023 14:57:12 +0100 > From: Brandon Zhi <Brandon(a)huize.asia> > To: nanog(a)nanog.org > Subject: Spamhaus flags any IP announced by our ASN as a criminal > network > Message-ID: > < > CAAyZddEAu48oYngA6xgwrsijbVf9LiwLHVE5OnO3y+8faUSMLg(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hello guy, > > We recently discovered that any IP address announced by our ASN is > blacklisted by Spamhaus, even if we only announced it but not use it. > > I would like to ask if this is manually set by Spamhaus or is the system > misjudgment? Has anyone encountered the same situation as us? > > > Best, > > *Brandon Zhi* > HUIZE LTD > > www.huize.asia <https://huize.asia/>| www.ixp.su | Twitter > > > This e-mail and any attachments or any reproduction of this e-mail in > whatever manner are confidential and for the use of the addressee(s) only. > HUIZE LTD can?t take any liability and guarantee of the text of the email > message and virus. >

2 1