- Test - lists.nanog.org

100G L2 Service (USA x Europe)
by Erick Nascimento 23 Oct '24

23 Oct '24

Hello everyone, Huge Networks is looking for 100G L2 service between Equinix Ashburn (or NYC Metro area) to any datacenter in the London or Frankfurt Metro Area. Please contact me offline if you offer this type of service. -- Erick Nascimento Contact: +55 11 3090-4441 | +55 11 94775-9570 Av. das Nações Unidas, nº 14171 Conj. 1504 - Torre B Vila Gertrudes - São Paulo - SP CEP: 04794-000 www.huge-networks.com <https://huge-net.works/assinatura> <https://www.linkedin.com/company/huge-networks> <https://www.facebook.com/hugenetworks/> <https://www.instagram.com/hugenetworksbr/> <https://www.youtube.com/channel/UCS5FUWeh00QsnMF6sKZSGvg>

2 1

abja
by Randy Bush 21 Oct '24

21 Oct '24

on this day in 2001, abha ahuja, computer scientist, routing geek, and friend to many died. a bit of cheer: tomorrow is rob blokzijl's birthday. october is not all sad. randy

1 0

Netrality Chicago NOC Phone Number
by Rishi Panthee 19 Oct '24

19 Oct '24

Hi, Does someone have the NOC phone number for Netrality Chicago? The number they have listed online ending in 1012 goes to a condo nearby rather than the NOC. Thanks!

1 0

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 18 Oct '24

18 Oct '24

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 19 Oct, 2024 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: 964712 Prefixes after maximum aggregation (per Origin AS): 366964 Deaggregation factor: 2.63 Unique aggregates announced (without unneeded subnets): 468314 Number of IPv4 prefixes with a valid ROA: 319217 Number of IPv4 prefixes with an invalid ROA: 1057 Number of IPv4 prefixes with no ROA: 644438 Total ASes present in the Internet Routing Table: 76358 Prefixes per ASN: 12.63 Origin-only ASes present in the Internet Routing Table: 65415 Origin ASes announcing only one prefix: 26857 Transit ASes present in the Internet Routing Table: 10943 Transit-only ASes present in the Internet Routing Table: 533 Average AS path length visible in the Internet Routing Table: 5.3 Max AS path length visible: 89 Max AS path prepend of ASN (152107) 85 Prefixes from unregistered ASNs in the Routing Table: 1004 Number of instances of unregistered ASNs: 1015 Number of 32-bit ASNs allocated by the RIRs: 45580 Number of 32-bit ASNs visible in the Routing Table: 37275 Prefixes from 32-bit ASNs in the Routing Table: 193534 Number of bogon 32-bit ASNs visible in the Routing Table: 51 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 523 Number of addresses announced to Internet: 3028035072 Equivalent to 180 /8s, 124 /16s and 38 /24s Percentage of available address space announced: 81.8 Percentage of allocated address space announced: 81.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: 315447 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 258106 Total APNIC prefixes after maximum aggregation: 75560 APNIC Deaggregation factor: 3.42 Prefixes being announced from the APNIC address blocks: 250022 Unique aggregates announced from the APNIC address blocks: 101060 APNIC Region origin ASes present in the Internet Routing Table: 14409 APNIC Prefixes per ASN: 17.35 APNIC Region origin ASes announcing only one prefix: 4392 APNIC Region transit ASes present in the Internet Routing Table: 1909 Average APNIC Region AS path length visible: 5.5 Max APNIC Region AS path length visible: 89 Number of APNIC region 32-bit ASNs visible in the Routing Table: 9840 Number of APNIC addresses announced to Internet: 756799616 Equivalent to 45 /8s, 27 /16s and 216 /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-153913 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: 281921 Total ARIN prefixes after maximum aggregation: 126129 ARIN Deaggregation factor: 2.24 Prefixes being announced from the ARIN address blocks: 285249 Unique aggregates announced from the ARIN address blocks: 135502 ARIN Region origin ASes present in the Internet Routing Table: 19174 ARIN Prefixes per ASN: 14.88 ARIN Region origin ASes announcing only one prefix: 6975 ARIN Region transit ASes present in the Internet Routing Table: 2003 Average ARIN Region AS path length visible: 4.6 Max ARIN Region AS path length visible: 33 Number of ARIN region 32-bit ASNs visible in the Routing Table: 5034 Number of ARIN addresses announced to Internet: 1266824960 Equivalent to 75 /8s, 130 /16s and 55 /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, 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: 268106 Total RIPE prefixes after maximum aggregation: 129491 RIPE Deaggregation factor: 2.07 Prefixes being announced from the RIPE address blocks: 264845 Unique aggregates announced from the RIPE address blocks: 168422 RIPE Region origin ASes present in the Internet Routing Table: 28784 RIPE Prefixes per ASN: 9.20 RIPE Region origin ASes announcing only one prefix: 12139 RIPE Region transit ASes present in the Internet Routing Table: 3981 Average RIPE Region AS path length visible: 5.3 Max RIPE Region AS path length visible: 43 Number of RIPE region 32-bit ASNs visible in the Routing Table: 12067 Number of RIPE addresses announced to Internet: 722340224 Equivalent to 43 /8s, 14 /16s and 9 /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, 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: 122484 Total LACNIC prefixes after maximum aggregation: 28523 LACNIC Deaggregation factor: 4.29 Prefixes being announced from the LACNIC address blocks: 120142 Unique aggregates announced from the LACNIC address blocks: 48565 LACNIC Region origin ASes present in the Internet Routing Table: 11173 LACNIC Prefixes per ASN: 10.75 LACNIC Region origin ASes announcing only one prefix: 2657 LACNIC Region transit ASes present in the Internet Routing Table: 2470 Average LACNIC Region AS path length visible: 5.9 Max LACNIC Region AS path length visible: 61 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 9079 Number of LACNIC addresses announced to Internet: 177570304 Equivalent to 10 /8s, 149 /16s and 130 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-274844 + 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: 33091 Total AfriNIC prefixes after maximum aggregation: 6612 AfriNIC Deaggregation factor: 5.00 Prefixes being announced from the AfriNIC address blocks: 43931 Unique aggregates announced from the AfriNIC address blocks: 14328 AfriNIC Region origin ASes present in the Internet Routing Table: 1896 AfriNIC Prefixes per ASN: 23.17 AfriNIC Region origin ASes announcing only one prefix: 694 AfriNIC Region transit ASes present in the Internet Routing Table: 370 Average AfriNIC Region AS path length visible: 6.0 Max AfriNIC Region AS path length visible: 32 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 1255 Number of AfriNIC addresses announced to Internet: 104219904 Equivalent to 6 /8s, 54 /16s and 69 /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 10077 8751 85 CHINAMOBILE-CN China Mobile Communication 7545 5977 840 656 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4872 4192 74 ERX-CERNET-BKB China Education and Resear 18403 4529 347 23 FPT-AS-AP FPT Telecom Company, VN 7552 3966 1331 25 VIETEL-AS-AP Viettel Group, VN 9498 3849 512 267 BBIL-AP BHARTI Airtel Ltd., IN 7713 3647 1036 71 TELKOMNET-AS-AP PT Telekomunikasi Indones 45899 3260 1841 105 VNPT-AS-VN VNPT Corp, VN 24560 2780 829 541 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd., 4766 2285 11519 586 KIXS-AS-KR Korea Telecom, KR 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 10878 11911 3790 AMAZON-02, US 11492 4660 310 547 CABLEONE, US 174 4452 8764 859 COGENT-174, US 7155 4166 287 88 VIASAT-SP-BACKBONE, US 6327 3603 1320 79 SHAW, CA 22773 3406 3035 188 ASN-CXA-ALL-CCI-22773-RDC, US 749 3264 54912 2511 DNIC-AS-00749, US 7018 3194 23677 1974 ATT-INTERNET4, US 396982 2867 3652 421 GOOGLE-CLOUD-PLATFORM, US 16625 2846 1241 2119 AKAMAI-AS, 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 7634 1709 143 UNI2-AS, ES 39891 4668 282 60 ALJAWWALSTC-AS, SA 20940 3862 3395 129 AKAMAI-ASN1, NL 9009 3683 317 1890 M247, RO 12389 2954 2294 883 ROSTELECOM-AS, RU 34984 2335 357 580 TELLCOM-AS, TR 212238 1795 131 1333 CDNEXT, GB 13188 1606 100 30 TRIOLAN, UA 8452 1579 1852 14 TE-AS TE-AS, EG 8551 1472 366 32 BEZEQ-INTERNATIONAL-AS Bezeqint Internet 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 11547 3236 509 UNINET, MX 10620 3546 494 937 Telmex Colombia S.A., CO 13999 2532 534 356 Mega Cable, S.A. de C.V., MX 11830 2007 369 64 Instituto Costarricense de Electricidad y 28573 1339 2310 261 Claro NXT Telecomunicacoes Ltda, BR 3816 1320 779 195 COLOMBIA TELECOMUNICACIONES S.A. ESP BIC, 6503 1155 374 163 Axtel, S.A.B. de C.V., MX 11664 1149 278 33 Techtel LMDS Comunicaciones Interactivas 6147 1105 369 22 Telefonica del Peru S.A.A., PE 22884 1059 97 372 TOTAL PLAY TELECOMUNICACIONES SA DE CV, M 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 1636 593 29 RAYA-AS, EG 24863 1615 389 16 LINKdotNET-AS, EG 36992 1414 1519 283 ETISALAT-MISR, EG 29571 1352 86 61 ORANGE-COTE-IVOIRE, CI 36903 1249 554 96 MT-MPLS, MA 36935 975 521 41 Vodafone-, EG 20011 808 155 353 INTERNET-SOLUTIONS, ZA 37069 639 1099 13 MOBINIL, EG 6713 555 1861 35 IAM-AS, MA 36914 517 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 8151 11547 3236 509 UNINET, MX 16509 10878 11911 3790 AMAZON-02, US 9808 10077 8751 85 CHINAMOBILE-CN China Mobile Communication 12479 7634 1709 143 UNI2-AS, ES 7545 5977 840 656 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4872 4192 74 ERX-CERNET-BKB China Education and Resear 39891 4668 282 60 ALJAWWALSTC-AS, SA 11492 4660 310 547 CABLEONE, US 18403 4529 347 23 FPT-AS-AP FPT Telecom Company, VN 174 4452 8764 859 COGENT-174, 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 10077 9992 CHINAMOBILE-CN China Mobile Communications Grou 12479 7634 7491 UNI2-AS, ES 16509 10878 7088 AMAZON-02, US 7545 5977 5321 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4872 4798 ERX-CERNET-BKB China Education and Research Net 39891 4668 4608 ALJAWWALSTC-AS, SA 18403 4529 4506 FPT-AS-AP FPT Telecom Company, VN 11492 4660 4113 CABLEONE, US 7155 4166 4078 VIASAT-SP-BACKBONE, US 7552 3966 3941 VIETEL-AS-AP Viettel Group, VN 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 33123 UNALLOCATED 8.10.69.0/24 174 COGENT-174, US 12169 UNALLOCATED 8.15.207.0/24 32787 PROLEXIC-TECHNOLOGIES-D 40493 UNALLOCATED 8.17.26.0/24 3356 LEVEL3, US 46639 UNALLOCATED 8.17.66.0/24 701 UUNET, US 53775 UNALLOCATED 8.20.88.0/24 7029 WINDSTREAM, US 393266 UNALLOCATED 8.23.52.0/24 46887 CROWNCASTLE-AS46887, US 396894 UNALLOCATED 8.28.201.0/24 46887 CROWNCASTLE-AS46887, US 394936 UNALLOCATED 8.33.224.0/24 22442 HOU-PHONOSCOPE, US 54338 UNALLOCATED 8.33.241.0/24 3356 LEVEL3, US 46639 UNALLOCATED 8.38.73.0/24 3356 LEVEL3, 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 14.192.20.0/22 Origin: 26658 HENGTONG-IDC-LLC, US 14.192.20.0/22 Transit: 6939 HURRICANE, US 23.137.192.0/24 Origin: 31798 DATACITY, CA 23.137.192.0/24 Transit: 21949 BEANFIELD, CA 23.139.88.0/24 Origin: 397244 RESERVED, ZZ 23.139.88.0/24 Transit: 33387 NOCIX, US 23.140.216.0/24 Origin: 27176 DATAWAGON, US 23.140.216.0/24 Transit: 20278 NEXEON, US 23.141.0.0/24 Origin: 395350 RESERVED, ZZ 23.141.0.0/24 Transit: 11426 TWC-11426-CAROLINAS, 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:16 /10:36 /11:91 /12:295 /13:576 /14:1172 /15:2062 /16:13173 /17:8266 /18:13755 /19:24580 /20:44956 /21:52240 /22:112343 /23:100217 /24:590187 /25:731 /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 6701 7634 UNI2-AS, ES 8151 5733 11547 UNINET, MX 11492 3555 4660 CABLEONE, US 39891 3428 4668 ALJAWWALSTC-AS, SA 6327 3398 3603 SHAW, CA 7155 3110 4166 VIASAT-SP-BACKBONE, US 22773 2537 3406 ASN-CXA-ALL-CCI-22773-RDC, US 16509 2220 10878 AMAZON-02, US 30036 2178 2517 MEDIACOM-ENTERPRISE-BUSINESS, US 10620 2175 3546 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:2295 2:1543 3:501 4:8 5:4456 6:169 7:6 8:1519 9:1 11:172 12:1418 13:371 14:2468 15:330 16:264 17:358 18:893 20:430 21:4 22:188 23:6916 24:2646 25:2 27:2601 29:19 31:2880 32:47 34:70 35:141 36:2372 37:4524 38:8707 39:916 40:150 41:4117 42:2182 43:2455 44:332 45:17636 46:4652 47:301 49:2025 50:1875 51:581 52:1580 54:317 55:955 56:8 57:223 58:2261 59:1259 60:1139 61:2740 62:2806 63:1854 64:5409 65:2276 66:4656 67:2998 68:1333 69:4014 70:1129 71:570 72:2865 74:2787 75:1626 76:635 77:2580 78:1865 79:1647 80:2207 81:2029 82:1755 83:1378 84:1758 85:3083 86:979 87:2407 88:1263 89:4374 90:678 91:8253 92:2606 93:2809 94:3794 95:4318 96:1262 97:316 98:1074 99:739 100:72 101:1172 102:3452 103:32294 104:4461 105:702 106:985 107:2390 108:1173 109:4011 110:2202 111:3321 112:2051 113:1790 114:1936 115:2117 116:1991 117:2715 118:2880 119:1980 120:1896 121:1406 122:2709 123:2154 124:1639 125:2861 126:64 128:1416 129:933 130:1248 131:1843 132:819 133:444 134:1521 135:314 136:1234 137:1120 138:2874 139:1519 140:1466 141:1560 142:1783 143:1586 144:1030 145:392 146:2091 147:2053 148:2507 149:2821 150:1095 151:1377 152:2110 153:500 154:7011 155:1492 156:2570 157:1832 158:1204 159:2445 160:3212 161:1759 162:3562 163:1755 164:1933 165:2138 166:1309 167:1854 168:4074 169:789 170:4919 171:1024 172:3899 173:3115 174:909 175:1256 176:3469 177:4729 178:3563 179:2217 180:2499 181:3912 182:3320 183:2053 184:2253 185:21164 186:5015 187:4215 188:4252 189:4044 190:9631 191:1517 192:11090 193:9278 194:7608 195:5416 196:3230 197:3365 198:6052 199:8179 200:8108 201:6239 202:10542 203:10380 204:4631 205:3681 206:4624 207:3693 208:4206 209:5176 210:4778 211:2671 212:4495 213:3643 214:1071 215:48 216:6631 217:3026 218:1382 219:557 220:2069 221:1047 222:838 223:2284 End of report

1 0

It can be challenging to advise DDoS mitigation subscribers on their RPKI-ROA needs
by Steven Wallace 18 Oct '24

18 Oct '24

DDoS mitigation services, particularly those that dynamically announce more specific routes during an attack, add complexity when advising customers on creating their RPKI-ROAs. Smaller organizations, often served by networks that provide DDoS mitigation on their behalf, might be unaware of these services or lack an understanding of how traffic is rerouted. In some cases, you can identify customers of DDoS mitigation services by looking at as-sets published by these providers or by investigating related IRR objects for the IP addresses. However, this approach isn’t reliable. Currently, there’s no established best practice for helping organizations determine the correct ROAs to create. This can lead to confusion, especially when DDoS mitigation is involved. ARIN plans to implement a check in their hosted RPKI interface that will help validate proposed ROAs against the current global routing table. While this feature will be useful, there is a risk that it could give DDoS mitigation customers a false sense of security. They might create ROAs that inadvertently block their DDoS scrubbing service from functioning properly. I’d like to engage with stakeholders in this space to explore opportunities for improvement. Any suggestions or input on this topic would be greatly appreciated. thanks, steven Steven Wallace Director - Routing Integrity Internet2 ssw(a)internet2.edu

5 8

3 Days Until N92! Important Safety Alert: Busy Bike Lane at Venue
by Nanog News 17 Oct '24

17 Oct '24

*** NANOG 92 Attendees: Stay Safe Navigating Bicycle Lanes* ------------------------------------------------------------ *Look Both Ways for Bikes and Cars When Crossing Outside our Toronto Venue* In front of our N92 Venue —The Westin Harbour Castle Hotel, there is a well-trafficked bicycle 'highway' consisting of two lanes with fast-moving cyclists who have the right of way. For your safety, please ensure that you look in both directions for bicycles and then check for cars before crossing. *** A (Tech) Road Less Traveled* ------------------------------------------------------------ *How a Passion for People Turned into a Career in Tech* "I can talk to anyone," she said. "I love to talk to people. I'm that person at the grocery store who asks, 'How was your day?' and actually cares." Samantha is one of the many vibrant members of our community who will be joining us at the upcoming Women in Tech Mixer; read more about her career story. *READ MORE * https://nanog.org/stories/a-tech-road-less-traveled/ *** POWER UP for NANOG 92 at the WIT Mixer* ------------------------------------------------------------ *Join Us Before NANOG 92 Begins* Whether you're a seasoned professional or just starting out, this is your chance to connect, learn, and be inspired by leading women in tech. The Women In Tech Mixer welcomes all attendees that identify as female and/or with she/her pronouns. *NANOG SOCIALS * https://nanog.org/events/nanog-92/socials/ *** And the Countdown Begins...* ------------------------------------------------------------ *NANOG 92 will Blast off in Four Days!* Can't attend NANOG 92 in person? No worries! Join us virtually for just $100! Get full access to live streaming and engage in real-time Q&A sessions with industry experts. Don’t miss out—register now! *MORE INFO * https://nanog.org/events/nanog-92/ ** Stay Connected ------------------------------------------------------------ http://www.facebook.com http://www.instagram.com/nanog_org/ http://www.linkedin.com/company/nanog/ https://www.twitter.com/nanog/ http://nanog.org

1 0

jon postel
by Randy Bush 16 Oct '24

16 Oct '24

dr postel died this day in 1998. october is a bad month for internet hero[ine]s randy

3 2

arista full tables recommendation
by Alex Buie 15 Oct '24

15 Oct '24

Hi all, We're an arista shop (primarily 7050qx-32s, 7050tx, and 7060cx right now) and wanted to get some input on recommendations for "real routers" that can better handle full internet tables. As it is right now we do some creative import filtering to import and inject a handful of routes we care about due to limited fib space and otherwise just use a default received from our carriers, with any particular transit carrier being the "primary" at a given time and using pingcheck <https://github.com/arista-eosext/PingCheck> to influence that decision. We'd like to move towards consuming full tables (or at the very least, customer routes) from each of our ISPs - would be grateful for any pointers or recommendations in arista models or family of devices that would be good core/peering routers, especially other than the latest generation. We'd be landing 10g optics from the carriers currently and peering to the downstream switches at 40G or 100G. (frequently we are in the used equipment space for our acquisitions so previous generation or two or three tends to land us in a pretty good spot). thanks in advance for any advice you can provide! Alex

4 3

CGNAT growing pains
by Jon Lewis 13 Oct '24

13 Oct '24

We started rolling out CGNAT about 6 months ago. It was smooth sailing for the first few months, but we eventually did run into a number of issues. Our customer base is primarily FTTH with "dynamic" IP assignment via DHCP. Since connections are always-on, customer ONTs/routers get an IP assigned, and then when the lease is renewed, they request a new lease for the existing IP, and, in general, that request is granted. This gives customers the mistaken impression they have a static IP. So, my impression, from working with some customers who've needed to be moved from CGNAT back to public IP is that customers who are doing port-forwarding don't even bother with dynamic DNS. They just know they can connect to their IP as they've never seen it change. We do offer/sell static IP, but pre-CGNAT, it was strictly for business customers. i.e. A residential customer could only get static IP service by converting their account to a business account. That may change in the near future. One issue we didn't foresee has been IP Geo issues. i.e. We all knew that streaming services like Netflix use IP Geo to determine what content should be made available, but that's, AFAIK, limited by country or region. What we didn't anticipate is services like Hulu Live TV doing IP Geo down to the city level to determine which local channels are a subscriber's local channels. We're using Juniper MX gear and SPC3 cards for our CGNAT routers, each one having a single large external pool. Since we serve most of FL, one external pool can't IP Geo correctly for customers as far apart as Miami and Jacksonville hitting the same CGNAT router. We don't currently have an acceptable solution to this other than moving impacted customers off CGNAT. One of the great unknowns (at least for us) with CGNAT was what our PBA settings should be. i.e. How large each port-block should be, and how many port-blocks to allow per customer. We started with 256x4. It seemed to work. We eventually noticed that we were logging port-block exceeded errors. This is one aspect where Juniper's CGNAT support is lacking. There's a counter for these errors, and it's available via SNMP, but there's no way to attribute the errors to subscriber IPs. We're polling the mib and graphing it, so we know it's a continuing issue and can see when it's incrementing faster/slower, but Junos provides no means for determining if "PBEs" are all being caused by a single customer, a handful of customers, etc. We have a JTAC case open on this. As a quick & hopeful fix, we both increased the port-block size and block limit. That helped, but didn't stop the errors. It also cut our CGNAT ratio by more than half (64:1 -> 28:1), if we stay at this ratio, we'll need much larger external pools than originally anticipated. Tuning these settings is kind of painful as JTAC strongly recommends bouncing the CGNAT service anytime CGNAT related config changes are made. This means briefly breaking Internet access for all CGNAT'd customers. For the PBEs, JTAC's suggestions so far have been to shorten some of the timeouts in the config and to keep doing what we're doing, which is a cron job that essentially does a "show services nat source port-block", parses the output looking for subscriber IPs that have used up the ports in several of their port-blocks, then does a "show services sessions source-prefix ..." and logs all of this. This at least gives us snapshots of "who's a heavy user right now" and lets us look at how they were using all their ports. i.e. was it bittorent, are they compromised and scanning the internet for more systems to compromise, is it legit looking traffic - just lots of it, etc.? The latest CGNAT issue is a customer with a Palo Alto Networks firewall connected to our network and several of their employees are our FTTH customers. On their PANW firewall, they're doing IP Geo based filtering, limiting access to internal servers to "US IPs". Since we only CGNAT traffic to the external Internet, their on-net employees hit the firewall from their 100.64/10 IPs and get blocked. I suggested they whitelist 100.64/10, saying we block traffic from 100.64/10 from entering our network via peering and transit, so they can be assured anything from 100.64/10 came from inside our network / our customers. They say the firewall won't let them whitelist 100.64.0.0/10, giving an error that it's invalid IP space. I know we're not the first to implement CGNAT, so I'm curious if others have run into these sorts of issues, or others we haven't run into yet, and if so, how you solved them. ---------------------------------------------------------------------- Jon Lewis, MCP :) | I route Blue Stream Fiber, Sr. Neteng | therefore you are _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________

10 14

Frustration with increasing information demands from Network Vendors
by chiel 12 Oct '24

12 Oct '24

Hi, I have an handful of Juniper devices (mx204 / QFX5100). I recently bought a new QFX5110 switch I want to update to a newer software release. My account on the Juniper website seems to be disabled and therefor I send an email to customer care. They replied with a form that I have to fill in. A couple of of the questions are "/$ Revenue Range/", "/# of Sales Reps/", "/# of Office Locations/". "/Details of potential opportunities in progress (also Provide)/". I only filled in the form with my own details (name, email address, etc..) and said I refused to give information about the other questions. Juniper (customer care) replied with "/Please note we need these details to reinstate the account. We can not proceed if the form is incomplete/. " I really really really find it disgusting that companies have no problem asking for this kind of information!! Its not only Juniper but also other major brands. I just bought a single switch and I can't update it without sharing all this information. I'm I do only one that feels this strongly about this?

13 17