- NANOG - lists.nanog.org

Microsoft AS8075 contact?
by Bryan Holloway 19 Jun '20

19 Jun '20

Hello ... If anyone from Microsoft peering is lurking, I could use an assist. We have a reachability issue in Chicago. E-mail to their PeeringDB NOC contact have gone unanswered. Thank you!

1 1

Google captcha issue
by Christopher Tyler 19 Jun '20

19 Jun '20

We run a smaller ISP of about 7.5k customers and the other day we got an email (excerpt below) from one of Google's automated tools. We are seeing automated scraping of Google Web Search from a large number of your IPs. Automated scraping violates our /robots.txt file and also our Terms of Service. We request that you terminate this traffic immediately. Failure to do so may cause your network to be blocked by our abuse systems. To allow you to identify the traffic, we are providing a list of your IPs they used today (Source field), as well as the most common destination (Google) IP and port and a timestamp of a recent request (in UTC) to aid in your identification. Note that this list may not be exhaustive, and we request that you terminate all such traffic, not just traffic from IPs in this list. All of the destination ports are either 80 or 443, so they at least appear to be legit web traffic on the surface. They are obviously spoofed IP address as there are network addresses in the list and the IP belongs to a router that doesn't appear to be compromised in any way. The initial letter included 700+ IP addresses from our network. It's now affecting our customers as they are now getting Captcha's for every couple of Google searches that they perform. Does anyone know of a good way to track the perpetrator(s) down and/or know of a way to mitigate this? -- Christopher Tyler Senior Network Engineer MTCRE/MTCNA/MTCTCE/MTCWE Total Highspeed Internet Solutions 1091 W. Kathryn Street Nixa, MO 65714 (417) 851-1107 x. 9002 www.totalhighspeed.com

4 4

Weekly Routing Table Report
by cscora＠apnic.net 19 Jun '20

19 Jun '20

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 TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG and the RIPE Routing WG. Daily listings are sent to bgp-stats(a)lists.apnic.net For historical data, please see http://thyme.rand.apnic.net. If you have any comments please contact Philip Smith <pfsinoz(a)gmail.com>. Routing Table Report 04:00 +10GMT Sat 20 Jun, 2020 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 815154 Prefixes after maximum aggregation (per Origin AS): 309453 Deaggregation factor: 2.63 Unique aggregates announced (without unneeded subnets): 397027 Total ASes present in the Internet Routing Table: 68353 Prefixes per ASN: 11.93 Origin-only ASes present in the Internet Routing Table: 58751 Origin ASes announcing only one prefix: 24470 Transit ASes present in the Internet Routing Table: 9602 Transit-only ASes present in the Internet Routing Table: 307 Average AS path length visible in the Internet Routing Table: 4.4 Max AS path length visible: 50 Max AS path prepend of ASN ( 22394) 38 Prefixes from unregistered ASNs in the Routing Table: 859 Number of instances of unregistered ASNs: 860 Number of 32-bit ASNs allocated by the RIRs: 32127 Number of 32-bit ASNs visible in the Routing Table: 26466 Prefixes from 32-bit ASNs in the Routing Table: 121955 Number of bogon 32-bit ASNs visible in the Routing Table: 16 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 543 Number of addresses announced to Internet: 2843369216 Equivalent to 169 /8s, 122 /16s and 95 /24s Percentage of available address space announced: 76.8 Percentage of allocated address space announced: 76.8 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 99.5 Total number of prefixes smaller than registry allocations: 274961 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 214358 Total APNIC prefixes after maximum aggregation: 62454 APNIC Deaggregation factor: 3.43 Prefixes being announced from the APNIC address blocks: 207950 Unique aggregates announced from the APNIC address blocks: 86021 APNIC Region origin ASes present in the Internet Routing Table: 10638 APNIC Prefixes per ASN: 19.55 APNIC Region origin ASes announcing only one prefix: 2979 APNIC Region transit ASes present in the Internet Routing Table: 1588 Average APNIC Region AS path length visible: 4.7 Max APNIC Region AS path length visible: 27 Number of APNIC region 32-bit ASNs visible in the Routing Table: 5710 Number of APNIC addresses announced to Internet: 769610624 Equivalent to 45 /8s, 223 /16s and 83 /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-141625 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: 238135 Total ARIN prefixes after maximum aggregation: 109384 ARIN Deaggregation factor: 2.18 Prefixes being announced from the ARIN address blocks: 235455 Unique aggregates announced from the ARIN address blocks: 119632 ARIN Region origin ASes present in the Internet Routing Table: 18514 ARIN Prefixes per ASN: 12.72 ARIN Region origin ASes announcing only one prefix: 6782 ARIN Region transit ASes present in the Internet Routing Table: 1893 Average ARIN Region AS path length visible: 3.9 Max ARIN Region AS path length visible: 42 Number of ARIN region 32-bit ASNs visible in the Routing Table: 3284 Number of ARIN addresses announced to Internet: 1080206848 Equivalent to 64 /8s, 98 /16s and 166 /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-399260 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: 231929 Total RIPE prefixes after maximum aggregation: 107300 RIPE Deaggregation factor: 2.16 Prefixes being announced from the RIPE address blocks: 228468 Unique aggregates announced from the RIPE address blocks: 134263 RIPE Region origin ASes present in the Internet Routing Table: 27158 RIPE Prefixes per ASN: 8.41 RIPE Region origin ASes announcing only one prefix: 11750 RIPE Region transit ASes present in the Internet Routing Table: 3842 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 29 Number of RIPE region 32-bit ASNs visible in the Routing Table: 9239 Number of RIPE addresses announced to Internet: 709194112 Equivalent to 42 /8s, 69 /16s and 113 /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: 106782 Total LACNIC prefixes after maximum aggregation: 24901 LACNIC Deaggregation factor: 4.29 Prefixes being announced from the LACNIC address blocks: 107936 Unique aggregates announced from the LACNIC address blocks: 46455 LACNIC Region origin ASes present in the Internet Routing Table: 9958 LACNIC Prefixes per ASN: 10.84 LACNIC Region origin ASes announcing only one prefix: 2470 LACNIC Region transit ASes present in the Internet Routing Table: 1857 Average LACNIC Region AS path length visible: 5.1 Max LACNIC Region AS path length visible: 50 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 7540 Number of LACNIC addresses announced to Internet: 174401024 Equivalent to 10 /8s, 101 /16s and 38 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-272796 + ERX transfers LACNIC Address Blocks 177/8, 179/8, 181/8, 186/8, 187/8, 189/8, 190/8, 191/8, 200/8, 201/8, AfriNIC Region Analysis Summary ------------------------------- Prefixes being announced by AfriNIC Region ASes: 23090 Total AfriNIC prefixes after maximum aggregation: 4748 AfriNIC Deaggregation factor: 4.86 Prefixes being announced from the AfriNIC address blocks: 34802 Unique aggregates announced from the AfriNIC address blocks: 10205 AfriNIC Region origin ASes present in the Internet Routing Table: 1405 AfriNIC Prefixes per ASN: 24.77 AfriNIC Region origin ASes announcing only one prefix: 489 AfriNIC Region transit ASes present in the Internet Routing Table: 282 Average AfriNIC Region AS path length visible: 5.0 Max AfriNIC Region AS path length visible: 30 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 693 Number of AfriNIC addresses announced to Internet: 109444864 Equivalent to 6 /8s, 133 /16s and 255 /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 7545 5529 716 650 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4743 4192 73 ERX-CERNET-BKB China Education and Rese 7552 3428 1330 21 VIETEL-AS-AP Viettel Group, VN 45899 3153 1805 105 VNPT-AS-VN VNPT Corp, VN 7713 2713 828 514 TELKOMNET-AS-AP PT Telekomunikasi Indon 9808 2556 9043 61 CMNET-GD Guangdong Mobile Communication 4766 2284 11101 554 KIXS-AS-KR Korea Telecom, KR 9498 2278 434 225 BBIL-AP BHARTI Airtel Ltd., IN 4755 2132 441 193 TATACOMM-AS TATA Communications formerl 9394 2029 4914 20 CTTNET China TieTong Telecommunications 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 11492 4456 299 628 CABLEONE, US 7155 4036 264 27 VIASAT-SP-BACKBONE, US 16509 3972 8140 1786 AMAZON-02, US 22773 3566 2968 153 ASN-CXA-ALL-CCI-22773-RDC, US 6327 3350 1324 90 SHAW, CA 16625 3111 1622 2213 AKAMAI-AS, US 209 2429 5076 534 CENTURYLINK-US-LEGACY-QWEST, US 30036 2412 364 180 MEDIACOM-ENTERPRISE-BUSINESS, US 5650 2304 2981 1621 FRONTIER-FRTR, US 26484 2170 136 224 IKGUL-26484, US Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 12479 5807 1656 137 UNI2-AS, ES 31334 4923 484 13 KABELDEUTSCHLAND-AS, DE 39891 3265 187 20 ALJAWWALSTC-AS, SA 8551 3179 379 45 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 20940 3069 456 2076 AKAMAI-ASN1, EU 12389 2548 2255 760 ROSTELECOM-AS, RU 9009 2217 233 1211 M247, GB 34984 2146 353 564 TELLCOM-AS, TR 13188 1609 100 35 TRIOLAN, UA 61317 1330 144 560 ASDETUK http://www.heficed.com, GB 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 6725 3324 593 Uninet S.A. de C.V., MX 10620 3358 530 500 Telmex Colombia S.A., CO 11830 2666 369 63 Instituto Costarricense de Electricidad 6503 1718 326 387 Axtel, S.A.B. de C.V., MX 7303 1517 988 251 Telecom Argentina S.A., AR 13999 1419 511 334 Mega Cable, S.A. de C.V., MX 28573 1380 2245 214 CLARO S.A., BR 3816 1107 570 149 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6147 1088 379 39 Telefonica del Peru S.A.A., PE 11172 957 112 71 Alestra, S. de R.L. de C.V., MX Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24863 1488 393 22 LINKdotNET-AS, EG 36992 1089 1539 76 ETISALAT-MISR, EG 24835 1088 474 24 RAYA-AS, EG 36903 900 472 91 MT-MPLS, MA 29571 625 68 11 ORANGE-COTE-IVOIRE, CI 6713 552 1863 34 IAM-AS, MA 37342 481 32 1 MOVITEL, MZ 36935 429 522 42 Vodafone-, EG 15399 422 45 12 WANANCHI-, KE 23889 344 231 15 MauritiusTelecom, MU Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 6725 3324 593 Uninet S.A. de C.V., MX 12479 5807 1656 137 UNI2-AS, ES 7545 5529 716 650 TPG-INTERNET-AP TPG Telecom Limited, AU 31334 4923 484 13 KABELDEUTSCHLAND-AS, DE 4538 4743 4192 73 ERX-CERNET-BKB China Education and Rese 11492 4456 299 628 CABLEONE, US 7155 4036 264 27 VIASAT-SP-BACKBONE, US 16509 3972 8140 1786 AMAZON-02, US 22773 3566 2968 153 ASN-CXA-ALL-CCI-22773-RDC, US 7552 3428 1330 21 VIETEL-AS-AP Viettel Group, VN Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 12479 5807 5670 UNI2-AS, ES 31334 4923 4910 KABELDEUTSCHLAND-AS, DE 7545 5529 4879 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4743 4670 ERX-CERNET-BKB China Education and Research Net 7155 4036 4009 VIASAT-SP-BACKBONE, US 11492 4456 3828 CABLEONE, US 22773 3566 3413 ASN-CXA-ALL-CCI-22773-RDC, US 7552 3428 3407 VIETEL-AS-AP Viettel Group, VN 6327 3350 3260 SHAW, CA 39891 3265 3245 ALJAWWALSTC-AS, SA Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Net Originated Transit AS Transit AS Name 22357 UNALLOCATED 8.7.108.0/24 3356 LEVEL3, US 62828 UNALLOCATED 8.21.130.0/24 3356 LEVEL3, US 393266 UNALLOCATED 8.23.52.0/24 174 COGENT-174, US 62485 UNALLOCATED 8.23.229.0/24 3356 LEVEL3, US 32985 UNALLOCATED 8.28.31.0/24 3356 LEVEL3, US 394936 UNALLOCATED 8.33.224.0/24 174 COGENT-174, US 23061 UNALLOCATED 8.39.119.0/24 3356 LEVEL3, US 26584 UNALLOCATED 8.42.62.0/23 209 CENTURYLINK-US-LEGACY-QWEST, 395438 UNALLOCATED 8.42.206.0/24 3356 LEVEL3, US 46766 UNALLOCATED 8.44.208.0/24 3356 LEVEL3, US Complete listing at http://thyme.rand.apnic.net/current/data-badAS Prefixes from private and non-routed address space (Global) ----------------------------------------------------------- Prefix Origin AS Description 192.88.99.0/24 6939 HURRICANE, US Complete listing at http://thyme.rand.apnic.net/current/data-dsua Advertised Unallocated Addresses -------------------------------- Unassigned Network ASN Information AS Name 23.160.208.0/24 Origin: 398328 IAN-CARROLL, US Transit: 54825 PACKET, US 27.100.7.0/24 Origin: 56096 UNASSIGNED Transit: 45455 TH-2S1N-AP Two S One N Co Ltd, Internet 27.126.156.0/22 Origin: 55827 UNASSIGNED Transit: 9930 TTNET-MY TIME dotCom Berhad, MY 27.126.156.0/23 Origin: 55827 UNASSIGNED Transit: 9930 TTNET-MY TIME dotCom Berhad, MY 27.126.158.0/23 Origin: 55827 UNASSIGNED Transit: 9930 TTNET-MY TIME dotCom Berhad, MY 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:9 /9:11 /10:38 /11:100 /12:287 /13:578 /14:1171 /15:1912 /16:13346 /17:8219 /18:13966 /19:25888 /20:41197 /21:48384 /22:100886 /23:83557 /24:474326 /25:1279 /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 4824 5807 UNI2-AS, ES 31334 4769 4923 KABELDEUTSCHLAND-AS, DE 11492 3519 4456 CABLEONE, US 6327 3140 3350 SHAW, CA 7155 3128 4036 VIASAT-SP-BACKBONE, US 22773 2777 3566 ASN-CXA-ALL-CCI-22773-RDC, US 8551 2638 3179 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 39891 2609 3265 ALJAWWALSTC-AS, SA 8151 2408 6725 Uninet S.A. de C.V., MX 30036 2155 2412 MEDIACOM-ENTERPRISE-BUSINESS, US Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1769 2:1199 3:30 4:19 5:3574 6:52 8:1438 9:1 11:1 12:1777 13:512 14:2307 15:72 16:8 17:290 18:81 20:105 23:3719 24:2287 25:3 27:2544 31:3078 32:128 34:1 35:42 36:958 37:3390 38:1953 39:424 40:129 41:3680 42:901 43:2148 44:208 45:14428 46:3695 47:291 49:1458 50:1491 51:93 52:1086 54:227 55:672 56:6 57:51 58:1840 59:1171 60:747 61:2300 62:2097 63:1983 64:5223 65:2314 66:5014 67:2871 68:1183 69:3951 70:1407 71:679 72:2879 74:2577 75:1449 76:658 77:2928 78:1643 79:2375 80:1959 81:1659 82:1312 83:1308 84:1230 85:2614 86:542 87:1738 88:1135 89:2760 90:388 91:7947 92:1519 93:2511 94:2727 95:3924 96:1242 97:333 98:923 99:977 100:86 101:1006 102:969 103:23863 104:3440 105:397 106:882 107:1999 108:711 109:3667 110:1843 111:2047 112:1610 113:1362 114:1538 115:1841 116:1793 117:2101 118:2140 119:1693 120:836 121:1039 122:2443 123:2056 124:1568 125:2015 128:1381 129:1223 130:652 131:1867 132:749 133:302 134:1321 135:304 136:612 137:852 138:2164 139:995 140:678 141:996 142:929 143:1252 144:1019 145:310 146:1497 147:1022 148:2096 149:1187 150:874 151:1210 152:1495 153:397 154:4662 155:1059 156:3105 157:1129 158:847 159:1979 160:1926 161:1056 162:3094 163:822 164:1472 165:1294 166:560 167:1634 168:3541 169:553 170:4236 171:776 172:1938 173:2573 174:985 175:1053 176:2589 177:4182 178:3041 179:1463 180:2284 181:2463 182:3090 183:1145 184:2418 185:16486 186:3764 187:2862 188:4103 189:2377 190:8710 191:1335 192:10378 193:7538 194:6237 195:4403 196:3275 197:2003 198:6114 199:5893 200:7255 201:5249 202:10518 203:10270 204:4564 205:3099 206:3189 207:3275 208:4061 209:4451 210:4007 211:2017 212:3381 213:3231 214:1199 215:62 216:6024 217:2410 218:854 219:615 220:2015 221:943 222:998 223:1500 End of report

1 0

Xfinity (both ends) - can't ping from users home to office
by Spencer Coplin 19 Jun '20

19 Jun '20

Hey, is anyone on here able to check routing for Xfinity residential to Xfinity business? I have a client that is unable to ping his office Comcast Business connection from his home Xfinity connection. It was working a month ago and we can confirm that his connection works over his iphone's hotspot. I am able to ping from my own xfinity residential (same city) without issues. I suspect something in the routing from his home connection is messed up as tracert/ping can't even resolve his office's IP. The client called Xfinity residential support and they blamed the inability to ping the IP on his office vpn connection. Has anyone else his this and if so, how was it resolved? Thank you in advance! Thank you, Spencer Coplin

2 2

Issues with Verizon FiOS
by Dovid Bender 19 Jun '20

19 Jun '20

Can someone from Verizon contact me off the list. Our customers as well as many others are experiencing packet loss on our Voice products https://puck.nether.net/pipermail/outages/2020-June/013133.html https://puck.nether.net/pipermail/outages/2020-June/013136.html TIA

2 1

Re: [c-nsp] Devil's Advocate - Segment Routing, Why?
by Mark Tinka 19 Jun '20

19 Jun '20

I think it's less about just the forwarding chips and more about an entire solution that someone can go and buy without having to fiddle with it. You remember the saying, "Gone are the days when men were men and wrote their own drivers"? Well, running a network is a full-time job, without having to learn how to code for hardware and protocols. There are many start-ups that are working off of commodity chips and commodity face plates. Building software for those disparate hardware systems, and then developing the software so that it can be used in commercial deployments is non-trivial. That is the leverage Cisco, Juniper, Nokia... even Huawei, have, and they won't let us forget it. Then again, if one's vision is bold enough, they could play the long game, start now, patiently build, and then come at us in 8 or so years. Because the market, surely, can't continue at the rate we are currently going. Everything else around us is dropping in price and revenue, and yet traditional routing and switching equipment continues to stay the same, if not increase. That's broken!` Mark. On 19/Jun/20 13:25, Robert Raszuk wrote: > But talking about commodity isn't this mainly Broadcom ? And is there > single chip there which does not support line rate IP ? Or is there any > chip which supports MPLS and cost less then IP/MPLS one ? > > On Fri, Jun 19, 2020 at 1:22 PM Benny Lyne Amorsen via cisco-nsp < > cisco-nsp(a)puck.nether.net> wrote: > >> >> >> ---------- Forwarded message ---------- >> From: Benny Lyne Amorsen <benny+usenet(a)amorsen.dk> >> To: cisco-nsp(a)puck.nether.net >> Cc: >> Bcc: >> Date: Fri, 19 Jun 2020 13:12:06 +0200 >> Subject: Re: [c-nsp] Devil's Advocate - Segment Routing, Why? >> Saku Ytti <saku(a)ytti.fi> writes: >> >>> This is simply not fundamentally true, it may be true due to market >>> perversion. But give student homework to design label switching chip >>> and IPv6 switching chip, and you'll use less silicon for the label >>> switching chip. And of course you spend less overhead on the tunnel. >> What you say is obviously true. >> >> However, no one AFAIK makes an MPLS switch at prices comparable to basic >> layer 3 IPv6 switches. You can argue that it is a market failure as much >> as you want, but I can only buy what is on the market. According to the >> market, MPLS is strictly Service Provider, with the accompanying Service >> Provider markup (and then ridiculous discounts to make the prices seem >> reasonable). Enterprise and datacenter are not generally using MPLS, and >> I can only look on in envy at the prices of their equipment. >> >> There is room for a startup to rethink the service provider market by >> using commodity enterprise equipment. Right now that means dumping MPLS, >> since that is only available (if at all) at the most expensive license >> level. Meanwhile you can get get low-scale BGPv6 and line-speed GRE with >> commodity hardware without extra licenses. >> >> I am not saying that it will be easy to manage such a network, the >> tooling for MPLS is vastly superior. I am merely saying that with just a >> simple IPv6-to-the-edge network you can deliver similar services to an >> MPLS-to-the-edge network at lower cost, if you can figure out how to >> build the tooling. >> >> Per-packet overhead is hefty. Is that a problem today? >> >> >> >> >> ---------- Forwarded message ---------- >> From: Benny Lyne Amorsen via cisco-nsp <cisco-nsp(a)puck.nether.net> >> To: cisco-nsp(a)puck.nether.net >> Cc: >> Bcc: >> Date: Fri, 19 Jun 2020 13:12:06 +0200 >> Subject: Re: [c-nsp] Devil's Advocate - Segment Routing, Why? >> _______________________________________________ >> cisco-nsp mailing list cisco-nsp(a)puck.nether.net >> https://puck.nether.net/mailman/listinfo/cisco-nsp >> archive at http://puck.nether.net/pipermail/cisco-nsp/ >> > _______________________________________________ > cisco-nsp mailing list cisco-nsp(a)puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > .

3 7

Re: [c-nsp] Devil's Advocate - Segment Routing, Why?
by Mark Tinka 19 Jun '20

19 Jun '20

On 19/Jun/20 13:11, Saku Ytti wrote: > ASR9k also has low and high scale cards, we buy the low scale, even > for edge. But even low scale is pretty high scale in this context. You're probably referring to the TR vs. SE line cards, yes? We would also buy TR line cards for high-touch use-cases, because, as you say, that is pretty high scale as well, already :-). I think the SE line cards are meant for high-capacity BNG terminations in a single chassis, per line card. But with most IP traffic a network is carrying being best-effort and capacity available all over the place, what's the point anymore? > > I think there would be market for on-chip only LSR/core cards. > Ultimately if you design for that day1, it won't add lot of costs to > you. Yes the BOM difference may not be that great, because ultimately > silicon is cheap and costs are in NRE. But the on-chip only cards > would have bit more ports and they'd have better availability due to > less component failures. > I would fight very hard for us buy such cards in core, if vendor would > offer them. Same here. For now, we are exploring the PTX1000/10002 machinery. I know fixed form factor boxes for a core are a bit strange, but looking at how far the tech has come, I'm feeling a lot more bullish about having a core box that isn't redundant in control planes, data planes, and all the rest. Just power supplies :-). A lot of money to be saved if the idea works. > Like the trio-in-pci full open, I think this is just marketing > failure. Vendors are wearing their DC glasses and don't see anything > else. While the big-name DC are lost cause, AMZN employs more chip > designers than JNPR, matter of time before JNPR loses amzn edge too to > internal amzn product. > > Someone with bit bolder vision on what the market could be, may have > real opportunity here. This is what I've been telling the vendors since about 2017, both IP and Transport. It's only a matter of time before the level of development happening in the cloud + content houses far surpasses what the vendors are doing, if not already. Why spend all your time, energy and resources on a market that isn't going to find use for your NRE, and can probably out-code and out-research you with one hand tied behind their back, any day? The only reason they aren't building their own core routers yet is because that's an area where they can still afford to offload development time to the vendors. The edge is where they need to badly optimize, and they will do it a lot more efficiently than the vendors can, in time, if not already. When I saw one cloud provider present their idea on collapsing an entire DWDM line card into an optic that they can code for and stick into a server, I saw the DWDM's vendor's hearts sink right across the table where I sat. This was 3 years ago. The vendors need, as you say, someone with a bold enough vision to pivot the tradition. Mark.

2 1

Re: AS hijacking (Philosophy, rants, GeoMind)
by Sriram, Kotikalapudi (Fed) 18 Jun '20

18 Jun '20

Mike, >As our canned Email stated, AS2 (and many low digit AS') get hijacked and >often go on to hijack someone's prefix. AS2 (proper) is rarely changed and >the chances of an actual prefix hijack from it is extremely low. > >So as I've asked our peers, I'll ask here: What is expected of us to be good >"Net Citizens" with these hijacks? Thoughts on AS hijack prevention: With RPKI-based route origin validation (ROV), it turns out that incremental solution for prefix hijacking is also an incremental solution for AS hijacking. For example -- assuming Invalid routes will be dropped -- if 70% of the announced prefixes are protected by ROAs, then those 70% prefixes cannot be hijacked with a hijacked AS. (Note: An exception to this is -- a deliberate hijacker can still perform what is called forged-origin hijack [1], i.e., the attacker matches the hijacked prefix with a hijacked AS such that they both belong to the same ROA.) So, the community should keep pushing ahead with ROA and RPKI-based ROV deployments to achieve 100% ROA coverage for announced prefixes and also 100% dropping of Invalid. The above can also be said about “trusted” IRR-based (or IRR+RPKI based) ROV [1]. However, priority should be given to speedup the RPKI/ROA deployment towards full adoption. FYI... Worldwide ROA coverage is currently at 20% for globally routed prefixes. https://rpki-monitor.antd.nist.gov/ Security guidance regarding route objects in IRR, ROAs in RPKI, and ROV deployment can be found here: [1] “Resilient Interdomain Traffic Exchange: BGP Security and DDoS Mitigation,” NIST Special Publication, NIST SP 800-189, December 2019. https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-189.pdf Also, look up: [2] MANRS: https://www.manrs.org/ Thank you. Regards, Sriram

1 0

Network card with relay in case of power failure
by Dovid Bender 18 Jun '20

18 Jun '20

Hi, I am sorry if this is off topic.I was once demoed a network device that had two interfaces. The traffic would go through the device. If there was a power cut or some other malfunction there would be a relay that would physically bridge the two network interfaces so the traffic would flow as if it was just a network cable. Is anyone aware of such a network card or device? TIA.

8 9

Quality of the internet
by Dovid Bender 18 Jun '20

18 Jun '20

Hi, My 9-5 is working for a VoIP provider. When we started in 2006 we had a lot of issues with the quality of the internet in eastern europe and central Asia. It was not rare for us to have to play around with routing to get the quality that we needed. In a review of tickets for the last two years it seems as if we barely do any of that these days. Rarely do we get a quality complaint that comes back to an issue where a carrier or ISP dropping or mangling packets. Has anyone else observed this as well?

8 12