- Test - lists.nanog.org

Weekly Routing Table Report
by cscora＠apnic.net 29 Dec '17

29 Dec '17

This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. The posting is sent to APOPS, NANOG, AfNOG, SANOG, PacNOG, SAFNOG, CaribNOG TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG, IRNOG 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>. Routing Table Report 04:00 +10GMT Sat 30 Dec, 2017 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 677557 Prefixes after maximum aggregation (per Origin AS): 263618 Deaggregation factor: 2.57 Unique aggregates announced (without unneeded subnets): 328121 Total ASes present in the Internet Routing Table: 59472 Prefixes per ASN: 11.39 Origin-only ASes present in the Internet Routing Table: 51332 Origin ASes announcing only one prefix: 22605 Transit ASes present in the Internet Routing Table: 8140 Transit-only ASes present in the Internet Routing Table: 256 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 30 Max AS path prepend of ASN ( 29046) 25 Prefixes from unregistered ASNs in the Routing Table: 88 Number of instances of unregistered ASNs: 89 Number of 32-bit ASNs allocated by the RIRs: 21049 Number of 32-bit ASNs visible in the Routing Table: 16874 Prefixes from 32-bit ASNs in the Routing Table: 69320 Number of bogon 32-bit ASNs visible in the Routing Table: 11 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 325 Number of addresses announced to Internet: 2859634018 Equivalent to 170 /8s, 114 /16s and 141 /24s Percentage of available address space announced: 77.2 Percentage of allocated address space announced: 77.2 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 98.8 Total number of prefixes smaller than registry allocations: 224347 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 186321 Total APNIC prefixes after maximum aggregation: 53408 APNIC Deaggregation factor: 3.49 Prefixes being announced from the APNIC address blocks: 185448 Unique aggregates announced from the APNIC address blocks: 77495 APNIC Region origin ASes present in the Internet Routing Table: 8557 APNIC Prefixes per ASN: 21.67 APNIC Region origin ASes announcing only one prefix: 2420 APNIC Region transit ASes present in the Internet Routing Table: 1250 Average APNIC Region AS path length visible: 4.3 Max APNIC Region AS path length visible: 29 Number of APNIC region 32-bit ASNs visible in the Routing Table: 3442 Number of APNIC addresses announced to Internet: 770161954 Equivalent to 45 /8s, 231 /16s and 189 /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-137529 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: 202626 Total ARIN prefixes after maximum aggregation: 97583 ARIN Deaggregation factor: 2.08 Prefixes being announced from the ARIN address blocks: 203867 Unique aggregates announced from the ARIN address blocks: 95602 ARIN Region origin ASes present in the Internet Routing Table: 18039 ARIN Prefixes per ASN: 11.30 ARIN Region origin ASes announcing only one prefix: 6678 ARIN Region transit ASes present in the Internet Routing Table: 1783 Average ARIN Region AS path length visible: 3.8 Max ARIN Region AS path length visible: 23 Number of ARIN region 32-bit ASNs visible in the Routing Table: 2285 Number of ARIN addresses announced to Internet: 1107279136 Equivalent to 65 /8s, 255 /16s and 189 /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-397212 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, 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: 183142 Total RIPE prefixes after maximum aggregation: 89231 RIPE Deaggregation factor: 2.05 Prefixes being announced from the RIPE address blocks: 179113 Unique aggregates announced from the RIPE address blocks: 107861 RIPE Region origin ASes present in the Internet Routing Table: 24778 RIPE Prefixes per ASN: 7.23 RIPE Region origin ASes announcing only one prefix: 11313 RIPE Region transit ASes present in the Internet Routing Table: 3509 Average RIPE Region AS path length visible: 4.5 Max RIPE Region AS path length visible: 30 Number of RIPE region 32-bit ASNs visible in the Routing Table: 6533 Number of RIPE addresses announced to Internet: 713927808 Equivalent to 42 /8s, 141 /16s and 172 /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-207259 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: 87687 Total LACNIC prefixes after maximum aggregation: 19412 LACNIC Deaggregation factor: 4.52 Prefixes being announced from the LACNIC address blocks: 88978 Unique aggregates announced from the LACNIC address blocks: 39696 LACNIC Region origin ASes present in the Internet Routing Table: 6705 LACNIC Prefixes per ASN: 13.27 LACNIC Region origin ASes announcing only one prefix: 1829 LACNIC Region transit ASes present in the Internet Routing Table: 1248 Average LACNIC Region AS path length visible: 5.2 Max LACNIC Region AS path length visible: 29 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 4232 Number of LACNIC addresses announced to Internet: 172587936 Equivalent to 10 /8s, 73 /16s and 123 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-268700 + 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: 17691 Total AfriNIC prefixes after maximum aggregation: 3917 AfriNIC Deaggregation factor: 4.52 Prefixes being announced from the AfriNIC address blocks: 19826 Unique aggregates announced from the AfriNIC address blocks: 7199 AfriNIC Region origin ASes present in the Internet Routing Table: 1105 AfriNIC Prefixes per ASN: 17.94 AfriNIC Region origin ASes announcing only one prefix: 364 AfriNIC Region transit ASes present in the Internet Routing Table: 224 Average AfriNIC Region AS path length visible: 4.7 Max AfriNIC Region AS path length visible: 21 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 382 Number of AfriNIC addresses announced to Internet: 95270656 Equivalent to 5 /8s, 173 /16s and 183 /24s AfriNIC AS Blocks 36864-37887, 327680-328703 & 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 4538 5423 4194 86 ERX-CERNET-BKB China Education and Rese 7545 3271 403 390 TPG-INTERNET-AP TPG Telecom Limited, AU 4766 2882 11133 767 KIXS-AS-KR Korea Telecom, KR 17974 2782 918 77 TELKOMNET-AS2-AP PT Telekomunikasi Indo 9829 2765 1499 540 BSNL-NIB National Internet Backbone, IN 45899 2561 1538 149 VNPT-AS-VN VNPT Corp, VN 7552 2530 1159 46 VIETEL-AS-AP Viettel Group, VN 9394 2168 4923 26 CTTNET China TieTong Telecommunications 9808 2090 8699 32 CMNET-GD Guangdong Mobile Communication 4755 2084 417 209 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 6327 3341 1323 86 SHAW - Shaw Communications Inc., CA 22773 3307 2951 146 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 18566 2169 405 108 MEGAPATH5-US - MegaPath Corporation, US 20115 2066 2324 465 CHARTER-NET-HKY-NC - Charter Communicat 16509 1987 4081 583 AMAZON-02 - Amazon.com, Inc., US 6389 1960 3671 39 BELLSOUTH-NET-BLK - BellSouth.net Inc., 209 1944 5063 649 CENTURYLINK-US-LEGACY-QWEST - Qwest Com 30036 1867 332 244 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 11492 1725 235 572 CABLEONE - CABLE ONE, INC., US 7018 1671 20197 1243 ATT-INTERNET4 - AT&T Services, Inc., 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 39891 3520 187 21 ALJAWWALSTC-AS, SA 20940 2856 848 2059 AKAMAI-ASN1, US 8551 2284 378 42 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12389 2092 1830 688 ROSTELECOM-AS, RU 34984 2004 330 468 TELLCOM-AS, TR 12479 1982 1068 127 UNI2-AS, ES 9121 1951 1691 17 TTNET, TR 13188 1605 100 46 TRIOLAN, UA 8402 1233 544 14 CORBINA-AS OJSC "Vimpelcom", RU 6849 1228 355 21 UKRTELNET, 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 3749 3433 599 Uninet S.A. de C.V., MX 10620 3578 539 262 Telmex Colombia S.A., CO 11830 2631 370 66 Instituto Costarricense de Electricidad 6503 1617 437 53 Axtel, S.A.B. de C.V., MX 7303 1497 1022 194 Telecom Argentina S.A., AR 6147 1192 377 27 Telefonica del Peru S.A.A., PE 28573 1022 2259 189 CLARO S.A., BR 3816 1010 507 113 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 11172 919 126 85 Alestra, S. de R.L. de C.V., MX 18881 904 1065 27 TELEFÔNICA BRASIL S.A, BR 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 1192 398 48 LINKdotNET-AS, EG 37611 780 91 8 Afrihost, ZA 36903 741 372 137 MT-MPLS, MA 36992 657 1383 31 ETISALAT-MISR, EG 8452 520 1730 18 TE-AS TE-AS, EG 24835 449 786 17 RAYA-AS, EG 29571 443 36 13 CITelecom-AS, CI 37492 435 367 77 ORANGE-, TN 37342 356 32 1 MOVITEL, MZ 15399 342 35 7 WANANCHI-, KE 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 4538 5423 4194 86 ERX-CERNET-BKB China Education and Rese 8151 3749 3433 599 Uninet S.A. de C.V., MX 10620 3578 539 262 Telmex Colombia S.A., CO 39891 3520 187 21 ALJAWWALSTC-AS, SA 6327 3341 1323 86 SHAW - Shaw Communications Inc., CA 22773 3307 2951 146 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 7545 3271 403 390 TPG-INTERNET-AP TPG Telecom Limited, AU 4766 2882 11133 767 KIXS-AS-KR Korea Telecom, KR 20940 2856 848 2059 AKAMAI-ASN1, US 17974 2782 918 77 TELKOMNET-AS2-AP PT Telekomunikasi Indo Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 39891 3520 3499 ALJAWWALSTC-AS, SA 10620 3578 3316 Telmex Colombia S.A., CO 6327 3341 3255 SHAW - Shaw Communications Inc., CA 22773 3307 3161 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 8151 3749 3150 Uninet S.A. de C.V., MX 7545 3271 2881 TPG-INTERNET-AP TPG Telecom Limited, AU 17974 2782 2705 TELKOMNET-AS2-AP PT Telekomunikasi Indonesia, I 11830 2631 2565 Instituto Costarricense de Electricidad y Telec 7552 2530 2484 VIETEL-AS-AP Viettel Group, VN 45899 2561 2412 VNPT-AS-VN VNPT Corp, VN Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 64525 PRIVATE 45.119.143.0/24 133275 GIGANTIC-AS Gigantic Infotel P 64525 PRIVATE 45.125.62.0/24 133275 GIGANTIC-AS Gigantic Infotel P 65001 PRIVATE 46.237.40.0/21 13118 ASN-YARTELECOM PJSC Rostelecom 65534 PRIVATE 58.68.109.0/24 10201 DWL-AS-IN Dishnet Wireless Lim 64513 PRIVATE 62.150.101.0/24 9155 QNET Kuwait, KW 204819 UNALLOCATED 82.195.160.0/22 1239 SPRINTLINK - Sprint, US 419333 UNALLOCATED 84.17.91.0/24 41933 IPRAGAZ-AS Istanbul/ TURKEY, T 64609 PRIVATE 94.245.126.0/24 6584 MICROSOFT-GP-AS - Microsoft Co 65000 PRIVATE 95.179.2.0/24 65001 -Private Use AS-, ZZ 65000 PRIVATE 95.179.3.0/24 65001 -Private Use AS-, ZZ Complete listing at http://thyme.rand.apnic.net/current/data-badAS Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 14.128.14.0/23 10247 NETLINE, ZA 14.192.50.0/23 10247 NETLINE, ZA 14.192.58.0/23 10247 NETLINE, ZA 27.100.7.0/24 56096 UNKNOWN 36.255.250.0/23 10247 NETLINE, ZA 41.78.180.0/23 37265 -Reserved AS-, ZZ 43.228.144.0/22 9829 BSNL-NIB National Internet Backbone, IN 43.251.20.0/22 9381 WTT-AS-AP WTT HK Limited, HK 43.251.84.0/22 133676 PNPL-AS Precious netcom pvt ltd, IN 43.251.84.0/23 133676 PNPL-AS Precious netcom pvt ltd, IN 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:15 /9:12 /10:37 /11:99 /12:279 /13:557 /14:1087 /15:1894 /16:13409 /17:7771 /18:13659 /19:25260 /20:38896 /21:44589 /22:82574 /23:66696 /24:378478 /25:840 /26:607 /27:661 /28:36 /29:20 /30:17 /31:4 /32:60 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 6327 3133 3341 SHAW - Shaw Communications Inc., CA 39891 2946 3520 ALJAWWALSTC-AS, SA 22773 2552 3307 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 18566 2063 2169 MEGAPATH5-US - MegaPath Corporation, US 11830 1977 2631 Instituto Costarricense de Electricidad y Telec 8551 1748 2284 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 30036 1634 1867 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Communi 10620 1577 3578 Telmex Colombia S.A., CO 11492 1521 1725 CABLEONE - CABLE ONE, INC., US 9121 1427 1951 TTNET, TR Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1572 2:820 4:18 5:2638 6:39 8:1094 9:1 12:1854 13:196 14:1758 15:28 16:3 17:185 18:76 20:53 21:12 23:2494 24:1924 25:2 27:2335 31:1966 32:87 35:22 36:460 37:2465 38:1461 39:223 40:101 41:2989 42:537 43:1917 44:91 45:3521 46:2978 47:192 49:1371 50:1052 51:47 52:921 54:355 55:6 56:7 57:42 58:1572 59:1002 60:372 61:1992 62:1767 63:1818 64:4648 65:2244 66:4486 67:2308 68:1192 69:3160 70:1132 71:587 72:2114 74:2697 75:392 76:423 77:1554 78:1616 79:1961 80:1475 81:1405 82:1070 83:778 84:1005 85:1977 86:569 87:1222 88:913 89:2311 90:175 91:6277 92:1124 93:2346 94:2432 95:2725 96:667 97:356 98:960 99:107 100:152 101:1531 102:10 103:16591 104:3208 105:211 106:520 107:1800 108:823 109:2717 110:1546 111:1718 112:1288 113:1391 114:1119 115:1598 116:1637 117:1664 118:2218 119:1656 120:912 121:1057 122:2414 123:1879 124:1482 125:1840 128:963 129:580 130:440 131:1630 132:596 133:194 134:997 135:221 136:449 137:457 138:1983 139:554 140:387 141:678 142:770 143:950 144:792 145:195 146:1147 147:687 148:1481 149:716 150:717 151:990 152:750 153:307 154:971 155:743 156:744 157:745 158:598 159:1649 160:849 161:735 162:2542 163:520 164:976 165:1487 166:398 167:1351 168:3112 169:787 170:3629 171:404 172:1020 173:1915 174:858 175:775 176:1859 177:3939 178:2485 179:1159 180:2232 181:2138 182:2402 183:1044 184:892 185:11951 186:3441 187:2340 188:2624 189:1940 190:8217 191:1341 192:9738 193:5861 194:4775 195:3987 196:2297 197:1426 198:5527 199:5885 200:7277 201:4903 202:10403 203:9947 204:4562 205:2872 206:3042 207:3107 208:3991 209:3939 210:4005 211:2128 212:2919 213:2624 214:859 215:66 216:5740 217:2111 218:910 219:626 220:1728 221:983 222:742 223:1229 End of report

1 0

Cogent on-net corporate building
by Lewis,Mitchell T. 29 Dec '17

29 Dec '17

Anyone a cogent customer in an on-net corporate building(Not a Cogent or Carrier Neutral Datacenter)? I have a few questions about setup. Off list responses are fine. Regards, Mitchell T. Lewis [ mailto:MLewis@TechCompute.Net | MLewis(a)TechCompute.Net ] [ http://linkedin.com/in/mlewiscc ] |203-816-0371 PGP Fingerprint: 79F2A12BAC77827581C734212AFA805732A1394E [ https://pgp.mit.edu/pks/lookup?op=get&search=0x2AFA805732A1394E | Public PGP Key ]

1 0

Re: Waste will kill ipv6 too
by Scott Weeks 29 Dec '17

29 Dec '17

> :: Isn't this the utopia we've been seeking out? > > I like that one! :-) >> Seriously. All I was trying to say is there're going to be things not thought of yet that will chew up address space faster than ever before now that everyone believes it's essentially inexhaustible. And, I expect, sooner than imagined. scott

3 3

Re: Waste will kill ipv6 too
by Scott Weeks 29 Dec '17

29 Dec '17

:: Now think about scaling. Yes :: If the population doubles, we're now down to four spare /3s. :: If that doubled population doubles the number of devices, :: we're down to two spare /3s. If the population doubles :: again, there will be no civilization left, let alone an :: Internet. Etc. So realistically, the current address space :: allocation policies can handle a doubling of the planet's :: population, with each person having a quarter of a million :: addressable nodes. Each node having its own /64 to address :: individual endpoints within whatever that 'node' represents. Space: the final IP frontier These are the voyages of the range of IPv6 Its many-year mission: to explore strange new device implementations; to seek out new planet-covering nano-device applications and new ad-hoc networking technologies; to boldly go via DTN where no internet segment has gone before. <cue space-like music> :: Isn't this the utopia we've been seeking out? I like that one! :-) scott

4 3

Re: Implementing 464XLAT at a small WISP
by JORDI PALET MARTINEZ 28 Dec '17

28 Dec '17

In many ocassions you have MUCH better support from the OpenSource community than from vendors …. Look at Ubiquity and Mikrotik, supporting a very reduced set of transitions mechanisms. I’ve many WISP that have big troubles to keep growing because that, and you know what, at the end they reflash that “nice” hardware with LEDE, and done! Regards, Jordi -----Mensaje original----- De: Loganaden Velvindron <logan(a)hackers.mu> Responder a: <logan(a)hackers.mu> Fecha: jueves, 28 de diciembre de 2017, 12:04 Para: <jordi.palet(a)consulintel.es> CC: <nanog(a)nanog.org> Asunto: Re: Implementing 464XLAT at a small WISP On Thu, Dec 28, 2017 at 2:43 PM, JORDI PALET MARTINEZ <jordi.palet(a)consulintel.es> wrote: > I’ve customers with have 1Gbit FTTH link using LEDE with NAT. > > Depending on the hardware (I’m talking about Chinese made routers with cost less than 50 USD) they easily reach 9xx Mbits. It may depend on the chip set, as some LEDE implementations take advantage of hardware NAT. > > I’ve tested it myself with iperf, simulating a WAN link to traverse the router in a 2 LAN lab environment. The tests have been done using both, native IPv4 and CLAT (so having only IPv6 in the WAN link). > > Regular LEDE stable firmware, in most of the devices, don’t support by default hardware NAT, so you can in those cases, reach 500-600 Mbits, again, depending on specific hardware. > > So, I don’t think number of users is an issue. > > Not sure if that’s responding your question … > Thanks for sharing. It's interesting to see enterprise customers adopting OpenWRT/LEDE despite no official support from CPE vendors for 3rd party firmware on their products. > Regards, > Jordi > > -----Mensaje original----- > De: Loganaden Velvindron <logan(a)hackers.mu> > Responder a: <logan(a)hackers.mu> > Fecha: jueves, 28 de diciembre de 2017, 10:52 > Para: <jordi.palet(a)consulintel.es> > CC: <nanog(a)nanog.org> > Asunto: Re: Implementing 464XLAT at a small WISP > > On Thu, Dec 28, 2017 at 1:11 PM, JORDI PALET MARTINEZ > <jordi.palet(a)consulintel.es> wrote: > > Nice ;-) > > > > I’ve been doing this for some time already … and have trials with several customers (tens of thousands of customers). > > > > Note that most of the routers that support LEDE (quite a big list), will work by default with a standard stable release. > > > > I'm curious about the limits in terms of number of users from running > OpenWRT/LEDE on this kind of gear. Afaik, LEDE or OpenWRT do not have > customer drivers that push a lot of traffic. Often the linux driver > running on the default firmware is developed out of the free. > https://pappp.net/?p=1525 > > > > You mention it, but we use something like for the offload: > > ethtool --offload eth0 gro off lro off > > ethtool --offload eth1 gro off lro off > > > > Also, for the DNS64, I use exclude. It can be improved also to avoid including (in the exclusion) the prefixes for transition mechanisms, such as 2001::/32, 2002::/16, etc. > > > > dns64 64:ff9b::/96 { > > clients { any; }; > > mapped { any; }; > > exclude { 0::/3; 4000::/2; 8000::/1; 2001:db8::/32; }; > > break-dnssec no; > > }; > > > > I’ve an ID on this: > > > > https://datatracker.ietf.org/doc/draft-palet-v6ops-464xlat-deployment/ > > > > > > I’m working in the next few days in a review of this, so any inputs are welcome! > > > > Regards, > > Jordi > > > > -----Mensaje original----- > > De: NANOG <nanog-bounces(a)nanog.org> en nombre de Brock Tice <brock(a)bmwl.co> > > Responder a: <brock(a)bmwl.co> > > Fecha: jueves, 28 de diciembre de 2017, 1:48 > > Para: <nanog(a)nanog.org> > > Asunto: Implementing 464XLAT at a small WISP > > > > We recently deployed our first half-dozen IPv6-only customers after 6+ > > months of testing, using 464XLAT. > > > > It took me ages to sort all this out, so I hope someone finds this > > helpful. Feedback very much welcome. > > > > https://blog.brocktice.com/2017/12/27/deploying-464xlat-for-ipv6-only-clien… > > > > > > > > > > ********************************************** > > IPv4 is over > > Are you ready for the new Internet ? > > http://www.consulintel.es > > The IPv6 Company > > > > This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. > > > > > > > > > > > ********************************************** > IPv4 is over > Are you ready for the new Internet ? > http://www.consulintel.es > The IPv6 Company > > This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. > > > ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.consulintel.es The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.

2 1

Re: Implementing 464XLAT at a small WISP
by JORDI PALET MARTINEZ 28 Dec '17

28 Dec '17

I’ve customers with have 1Gbit FTTH link using LEDE with NAT. Depending on the hardware (I’m talking about Chinese made routers with cost less than 50 USD) they easily reach 9xx Mbits. It may depend on the chip set, as some LEDE implementations take advantage of hardware NAT. I’ve tested it myself with iperf, simulating a WAN link to traverse the router in a 2 LAN lab environment. The tests have been done using both, native IPv4 and CLAT (so having only IPv6 in the WAN link). Regular LEDE stable firmware, in most of the devices, don’t support by default hardware NAT, so you can in those cases, reach 500-600 Mbits, again, depending on specific hardware. So, I don’t think number of users is an issue. Not sure if that’s responding your question … Regards, Jordi -----Mensaje original----- De: Loganaden Velvindron <logan(a)hackers.mu> Responder a: <logan(a)hackers.mu> Fecha: jueves, 28 de diciembre de 2017, 10:52 Para: <jordi.palet(a)consulintel.es> CC: <nanog(a)nanog.org> Asunto: Re: Implementing 464XLAT at a small WISP On Thu, Dec 28, 2017 at 1:11 PM, JORDI PALET MARTINEZ <jordi.palet(a)consulintel.es> wrote: > Nice ;-) > > I’ve been doing this for some time already … and have trials with several customers (tens of thousands of customers). > > Note that most of the routers that support LEDE (quite a big list), will work by default with a standard stable release. > I'm curious about the limits in terms of number of users from running OpenWRT/LEDE on this kind of gear. Afaik, LEDE or OpenWRT do not have customer drivers that push a lot of traffic. Often the linux driver running on the default firmware is developed out of the free. https://pappp.net/?p=1525 > You mention it, but we use something like for the offload: > ethtool --offload eth0 gro off lro off > ethtool --offload eth1 gro off lro off > > Also, for the DNS64, I use exclude. It can be improved also to avoid including (in the exclusion) the prefixes for transition mechanisms, such as 2001::/32, 2002::/16, etc. > > dns64 64:ff9b::/96 { > clients { any; }; > mapped { any; }; > exclude { 0::/3; 4000::/2; 8000::/1; 2001:db8::/32; }; > break-dnssec no; > }; > > I’ve an ID on this: > > https://datatracker.ietf.org/doc/draft-palet-v6ops-464xlat-deployment/ > > > I’m working in the next few days in a review of this, so any inputs are welcome! > > Regards, > Jordi > > -----Mensaje original----- > De: NANOG <nanog-bounces(a)nanog.org> en nombre de Brock Tice <brock(a)bmwl.co> > Responder a: <brock(a)bmwl.co> > Fecha: jueves, 28 de diciembre de 2017, 1:48 > Para: <nanog(a)nanog.org> > Asunto: Implementing 464XLAT at a small WISP > > We recently deployed our first half-dozen IPv6-only customers after 6+ > months of testing, using 464XLAT. > > It took me ages to sort all this out, so I hope someone finds this > helpful. Feedback very much welcome. > > https://blog.brocktice.com/2017/12/27/deploying-464xlat-for-ipv6-only-clien… > > > > > ********************************************** > IPv4 is over > Are you ready for the new Internet ? > http://www.consulintel.es > The IPv6 Company > > This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. > > > ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.consulintel.es The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.

1 0

Implementing 464XLAT at a small WISP
by Brock Tice 28 Dec '17

28 Dec '17

We recently deployed our first half-dozen IPv6-only customers after 6+ months of testing, using 464XLAT. It took me ages to sort all this out, so I hope someone finds this helpful. Feedback very much welcome. https://blog.brocktice.com/2017/12/27/deploying-464xlat-for-ipv6-only-clien…

3 2

Geolocation: IPv4 Subnet blocked by HULU, and others
by Michael Crapse 27 Dec '17

27 Dec '17

I am a local WISP. And my customers have trouble reaching Hulu, Disney now, and previously netflix and amazon prime(both resolved). I have emailed, mailed, and called both HULU and Disney now to get my 196.53.96.0/22 subnet unblacklisted as a VPN provider(no longer so) from their services. They have replied saying it takes 3-5 days to resolve the issue, that was several weeks ago. Can i get contact from those two services that can help my customers reach their services, thank you. Thank you for the help. -Michael

14 20

mailchimp contact
by Dennis Burgess 26 Dec '17

26 Dec '17

Would a MailChimp contact pelase hit me off-list :) Dennis Burgess - Network Solution Engineer - Consultant MikroTik Certified Trainer/Consultant<http://www.linktechs.net/productcart/pc/viewcontent.asp?idpage=5> - MTCNA, MTCRE, MTCWE, MTCTCE, MTCINE For Wireless Hardware/Routers visit www.linktechs.net<http://www.linktechs.net/> Radio Frequency Coverages: www.towercoverage.com<http://www.towercoverage.com/> Office: 314-735-0270 E-Mail: dmburgess(a)linktechs.net<mailto:dmburgess@linktechs.net>

1 0

Re: AS PATH limits
by Ken Chase 23 Dec '17

23 Dec '17

If you're on cogent, since 22:30 UTC yesterday or so this has been happening (or happened). *> 186.177.184.0/23 38.*.*.* 45050 0 174 262206 262206 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 262197 ? oddly, i see other pops with 174 sources giving a more sane route (even 6939 is giving us a route that goes thru 174 after 2 hops). 'Sup, 174? Wonder if this is just stuck in the router Im looking at and the update process is failing because the route is too long to process properly for removal or something. mmm, bugs!) /kc -- Ken Chase - math(a)sizone.org Guelph Canada

9 19