- Test - lists.nanog.org

RE: Centurylink having a bad morning?
by Drew Weaver 30 Aug '20

30 Aug '20

That site seems to be just for their cloud products, is there one of these for their actual network? From: R. Leigh Hennig <leigh(a)regula.one> Sent: Sunday, August 30, 2020 8:54 AM To: Drew Weaver <drew.weaver(a)thenap.com>; nanog(a)nanog.org Subject: Re: Centurylink having a bad morning? Global impact with issues reported by Fastly, Cloudflare, OpenDNS. https://status.ctl.io/ STARTED Sun Aug 30 2020 08:13 (EDT) Sun Aug 30 2020 12:13 (UTC) AFFECTED SERVICES External Cloud Network (CA3) DATE LATEST UPDATE Sun Aug 30 2020 08:13 (EDT) Sun Aug 30 2020 12:13 (UTC) Our technical teams are investigating an issue affecting some services in the CA3 data center. Ensuring the reliability of our services is our top priority. We will continue to provide status updates as this incident progresses. If you need further support, please contact us at help(a)ctl.io<mailto:help@ctl.io>. Sent from ProtonMail Mobile On Sun, Aug 30, 2020 at 8:14 AM, Drew Weaver via NANOG <nanog(a)nanog.org<mailto:nanog@nanog.org>> wrote: Hello, Woke up this morning to a bunch of reports of issues with connectivity had to shut down some Level3/CTL connections to get it to return to normal. As of right now their support portal won’t load: https://www.centurylink.com/business/login/ Just wondering what others are seeing.

3 3

Re: Centurylink having a bad morning?
by Mel Beckman 30 Aug '20

30 Aug '20

I have checked all of our circuits in the LA area and are seeing no BGP issues, but we don’t provide transit for CL, only use them for DIA. Traffic flows appear normal, but early Sunday morning is normally the lowest time of the week. -mel beckman > On Aug 30, 2020, at 5:29 AM, Mel Beckman <mel(a)beckman.org> wrote: >

2 1

Ipv6 help
by Brian 30 Aug '20

30 Aug '20

Is there anyway to deploy ipv6 and push ipv4 traffic end to end across the ipv6 network. With out having an ipv4 address for everything that is ipv6? If someone could reach out off list if there is a real solution to deploy ipv6 as almost middleware.

15 84

Weekly Routing Table Report
by cscora＠apnic.net 28 Aug '20

28 Aug '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 29 Aug, 2020 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 819897 Prefixes after maximum aggregation (per Origin AS): 312416 Deaggregation factor: 2.62 Unique aggregates announced (without unneeded subnets): 395832 Total ASes present in the Internet Routing Table: 69169 Prefixes per ASN: 11.85 Origin-only ASes present in the Internet Routing Table: 59425 Origin ASes announcing only one prefix: 24673 Transit ASes present in the Internet Routing Table: 9744 Transit-only ASes present in the Internet Routing Table: 303 Average AS path length visible in the Internet Routing Table: 4.4 Max AS path length visible: 45 Max AS path prepend of ASN ( 37385) 42 Prefixes from unregistered ASNs in the Routing Table: 855 Number of instances of unregistered ASNs: 872 Number of 32-bit ASNs allocated by the RIRs: 33235 Number of 32-bit ASNs visible in the Routing Table: 27393 Prefixes from 32-bit ASNs in the Routing Table: 127300 Number of bogon 32-bit ASNs visible in the Routing Table: 33 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 436 Number of addresses announced to Internet: 2850601216 Equivalent to 169 /8s, 232 /16s and 185 /24s Percentage of available address space announced: 77.0 Percentage of allocated address space announced: 77.0 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: 274044 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 216901 Total APNIC prefixes after maximum aggregation: 63329 APNIC Deaggregation factor: 3.42 Prefixes being announced from the APNIC address blocks: 210716 Unique aggregates announced from the APNIC address blocks: 86746 APNIC Region origin ASes present in the Internet Routing Table: 10831 APNIC Prefixes per ASN: 19.45 APNIC Region origin ASes announcing only one prefix: 3025 APNIC Region transit ASes present in the Internet Routing Table: 1590 Average APNIC Region AS path length visible: 4.5 Max APNIC Region AS path length visible: 28 Number of APNIC region 32-bit ASNs visible in the Routing Table: 5919 Number of APNIC addresses announced to Internet: 769812864 Equivalent to 45 /8s, 226 /16s and 105 /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: 240385 Total ARIN prefixes after maximum aggregation: 110557 ARIN Deaggregation factor: 2.17 Prefixes being announced from the ARIN address blocks: 237925 Unique aggregates announced from the ARIN address blocks: 116401 ARIN Region origin ASes present in the Internet Routing Table: 18565 ARIN Prefixes per ASN: 12.82 ARIN Region origin ASes announcing only one prefix: 6777 ARIN Region transit ASes present in the Internet Routing Table: 1902 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: 3385 Number of ARIN addresses announced to Internet: 1086994688 Equivalent to 64 /8s, 202 /16s and 57 /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: 227825 Total RIPE prefixes after maximum aggregation: 107550 RIPE Deaggregation factor: 2.12 Prefixes being announced from the RIPE address blocks: 224132 Unique aggregates announced from the RIPE address blocks: 135611 RIPE Region origin ASes present in the Internet Routing Table: 27323 RIPE Prefixes per ASN: 8.20 RIPE Region origin ASes announcing only one prefix: 11790 RIPE Region transit ASes present in the Internet Routing Table: 3857 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 35 Number of RIPE region 32-bit ASNs visible in the Routing Table: 9437 Number of RIPE addresses announced to Internet: 709090688 Equivalent to 42 /8s, 67 /16s and 221 /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: 110441 Total LACNIC prefixes after maximum aggregation: 25555 LACNIC Deaggregation factor: 4.32 Prefixes being announced from the LACNIC address blocks: 111580 Unique aggregates announced from the LACNIC address blocks: 47385 LACNIC Region origin ASes present in the Internet Routing Table: 10351 LACNIC Prefixes per ASN: 10.78 LACNIC Region origin ASes announcing only one prefix: 2581 LACNIC Region transit ASes present in the Internet Routing Table: 1943 Average LACNIC Region AS path length visible: 5.0 Max LACNIC Region AS path length visible: 28 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 7936 Number of LACNIC addresses announced to Internet: 174593280 Equivalent to 10 /8s, 104 /16s and 21 /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: 23489 Total AfriNIC prefixes after maximum aggregation: 4753 AfriNIC Deaggregation factor: 4.94 Prefixes being announced from the AfriNIC address blocks: 35108 Unique aggregates announced from the AfriNIC address blocks: 9341 AfriNIC Region origin ASes present in the Internet Routing Table: 1421 AfriNIC Prefixes per ASN: 24.71 AfriNIC Region origin ASes announcing only one prefix: 500 AfriNIC Region transit ASes present in the Internet Routing Table: 288 Average AfriNIC Region AS path length visible: 5.1 Max AfriNIC Region AS path length visible: 45 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 716 Number of AfriNIC addresses announced to Internet: 109668864 Equivalent to 6 /8s, 137 /16s and 106 /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 5651 763 673 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4741 4192 73 ERX-CERNET-BKB China Education and Rese 7552 3506 1330 22 VIETEL-AS-AP Viettel Group, VN 45899 3460 1896 52 VNPT-AS-VN VNPT Corp, VN 7713 2732 829 553 TELKOMNET-AS-AP PT Telekomunikasi Indon 9808 2521 9043 60 CMNET-GD Guangdong Mobile Communication 4766 2348 11103 555 KIXS-AS-KR Korea Telecom, KR 9498 2284 450 223 BBIL-AP BHARTI Airtel Ltd., IN 4755 2142 441 193 TATACOMM-AS TATA Communications formerl 9394 2038 4914 18 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 4540 304 647 CABLEONE, US 16509 4191 8247 1923 AMAZON-02, US 7155 4034 264 32 VIASAT-SP-BACKBONE, US 22773 3624 2984 173 ASN-CXA-ALL-CCI-22773-RDC, US 6327 3365 1323 84 SHAW, CA 16625 3147 1664 2255 AKAMAI-AS, US 30036 2454 367 112 MEDIACOM-ENTERPRISE-BUSINESS, US 26484 2449 153 333 IKGUL-26484, US 209 2448 5073 521 CENTURYLINK-US-LEGACY-QWEST, US 5650 2309 2981 1625 FRONTIER-FRTR, 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 5958 1652 135 UNI2-AS, ES 20940 3180 2217 1027 AKAMAI-ASN1, EU 8551 3159 379 45 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 39891 3073 179 21 ALJAWWALSTC-AS, SA 12389 2664 2271 836 ROSTELECOM-AS, RU 34984 2167 354 565 TELLCOM-AS, TR 9009 2148 224 1169 M247, GB 13188 1609 100 35 TRIOLAN, UA 61317 1359 162 609 ASDETUK http://www.heficed.com, GB 58224 1256 832 518 TCI, IR 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 7487 3306 602 Uninet S.A. de C.V., MX 10620 3366 530 530 Telmex Colombia S.A., CO 11830 2582 369 63 Instituto Costarricense de Electricidad 6503 1625 323 414 Axtel, S.A.B. de C.V., MX 7303 1483 954 263 Telecom Argentina S.A., AR 13999 1440 483 378 Mega Cable, S.A. de C.V., MX 28573 1361 2246 216 CLARO S.A., BR 3816 1135 574 157 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6147 1115 379 39 Telefonica del Peru S.A.A., PE 11172 957 111 69 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 1496 393 22 LINKdotNET-AS, EG 24835 1122 474 25 RAYA-AS, EG 36992 1121 1539 75 ETISALAT-MISR, EG 36903 917 480 93 MT-MPLS, MA 29571 670 68 10 ORANGE-COTE-IVOIRE, CI 6713 553 1863 34 IAM-AS, MA 15399 492 46 14 WANANCHI-, KE 36935 485 522 40 Vodafone-, EG 37342 481 32 1 MOVITEL, MZ 23889 345 232 16 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 7487 3306 602 Uninet S.A. de C.V., MX 12479 5958 1652 135 UNI2-AS, ES 7545 5651 763 673 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4741 4192 73 ERX-CERNET-BKB China Education and Rese 11492 4540 304 647 CABLEONE, US 16509 4191 8247 1923 AMAZON-02, US 7155 4034 264 32 VIASAT-SP-BACKBONE, US 22773 3624 2984 173 ASN-CXA-ALL-CCI-22773-RDC, US 7552 3506 1330 22 VIETEL-AS-AP Viettel Group, VN 45899 3460 1896 52 VNPT-AS-VN VNPT Corp, 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 5958 5823 UNI2-AS, ES 7545 5651 4978 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4741 4668 ERX-CERNET-BKB China Education and Research Net 7155 4034 4002 VIASAT-SP-BACKBONE, US 11492 4540 3893 CABLEONE, US 7552 3506 3484 VIETEL-AS-AP Viettel Group, VN 22773 3624 3451 ASN-CXA-ALL-CCI-22773-RDC, US 45899 3460 3408 VNPT-AS-VN VNPT Corp, VN 6327 3365 3281 SHAW, CA 8551 3159 3114 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 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 36270 UNALLOCATED 8.24.66.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 395438 UNALLOCATED 8.42.206.0/24 3356 LEVEL3, US 46766 UNALLOCATED 8.44.208.0/24 3356 LEVEL3, US 40544 UNALLOCATED 12.0.33.0/24 6461 ZAYO-6461, 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 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 No. 14, Jala 27.126.156.0/23 Origin: 55827 UNASSIGNED Transit: 9930 TTNET-MY TIME dotCom Berhad No. 14, Jala 27.126.158.0/23 Origin: 55827 UNASSIGNED Transit: 9930 TTNET-MY TIME dotCom Berhad No. 14, Jala 41.78.164.0/24 Origin: 328013 ISPAfrika, ZA Transit: 37179 AFRICAINX, ZA 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:39 /11:100 /12:286 /13:576 /14:1174 /15:1933 /16:13463 /17:8266 /18:14024 /19:25889 /20:41063 /21:49236 /22:102034 /23:85048 /24:475471 /25:1275 /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 4982 5958 UNI2-AS, ES 11492 3607 4540 CABLEONE, US 6327 3160 3365 SHAW, CA 7155 3122 4034 VIASAT-SP-BACKBONE, US 22773 2803 3624 ASN-CXA-ALL-CCI-22773-RDC, US 8551 2618 3159 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 39891 2609 3073 ALJAWWALSTC-AS, SA 8151 2593 7487 Uninet S.A. de C.V., MX 30036 2197 2454 MEDIACOM-ENTERPRISE-BUSINESS, US 5650 1994 2309 FRONTIER-FRTR, US Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1614 2:1127 3:33 4:19 5:3407 6:54 8:1474 9:1 11:1 12:1780 13:466 14:2302 15:72 16:8 17:292 18:85 20:110 23:3916 24:2335 25:3 27:2565 31:2164 32:121 34:1 35:42 36:983 37:3333 38:1893 39:450 40:128 41:3674 42:635 43:2156 44:219 45:14826 46:3659 47:320 49:1530 50:1627 51:90 52:1104 54:225 55:642 56:6 57:52 58:1773 59:1196 60:787 61:2309 62:2150 63:2016 64:5224 65:2344 66:5063 67:2893 68:1180 69:4044 70:1401 71:677 72:2902 74:2583 75:1457 76:670 77:1955 78:1655 79:2413 80:2055 81:1594 82:1304 83:1252 84:1230 85:2675 86:559 87:1745 88:938 89:2792 90:359 91:7103 92:1556 93:2499 94:2764 95:3262 96:1255 97:338 98:925 99:979 100:87 101:1009 102:1066 103:24284 104:3538 105:404 106:905 107:2114 108:728 109:3671 110:1974 111:2056 112:1656 113:1392 114:1519 115:1839 116:1794 117:2085 118:2151 119:1732 120:826 121:1056 122:2534 123:2043 124:1637 125:2128 128:1390 129:1217 130:717 131:1914 132:759 133:306 134:1368 135:300 136:644 137:864 138:2266 139:1040 140:707 141:1090 142:957 143:1224 144:1160 145:364 146:1376 147:1015 148:2123 149:1254 150:916 151:1075 152:1554 153:425 154:4548 155:1218 156:2995 157:1118 158:867 159:1967 160:1960 161:1061 162:3162 163:899 164:1510 165:1313 166:583 167:1659 168:3522 169:597 170:4286 171:775 172:1982 173:2673 174:975 175:1056 176:2681 177:4775 178:2692 179:1693 180:2288 181:2525 182:3114 183:1165 184:2425 185:16898 186:3915 187:2951 188:3328 189:2587 190:8934 191:1524 192:10384 193:7642 194:6276 195:4456 196:3134 197:2050 198:6113 199:5914 200:7300 201:5216 202:10573 203:10205 204:4614 205:3125 206:3165 207:3245 208:4007 209:4484 210:4164 211:2038 212:3483 213:3147 214:1170 215:62 216:6087 217:2433 218:847 219:614 220:2055 221:910 222:997 223:1667 End of report

1 0

BGP route hijack by AS10990
by Clinton Work 27 Aug '20

27 Aug '20

We saw a bunch of our IP blocks hijacked by AS10990 from 19:15 MDT until 20:23 MDT. Anybody else have problems with that. ASpath: 1299 7219 10990 50.92.0.0/17 AS10990 198.166.0.0/17 AS10990 198.166.128.0/17 AS10990 162.157.128.0/17 AS10990 162.157.0.0/17 AS10990 50.92.128.0/17 AS10990 -- Clinton Work Airdrie, AB

30 88

Re: TCP and UDP Port 0 - Should an ISP or ITP Block it?
by K. Scott Helms 26 Aug '20

26 Aug '20

To be clear, UDP port 0 is not and probably shouldn't be blocked because some network gear and reporting tools may mistake a fragmented UDP PDU for port 0. That's an implementation error, but one that may be common enough to create issues for users. Blocking inbound TCP port 0 is something that I've personally done in dozens of ISP networks over more than a decade without a single reported issue. Scott Helms On Tue, Aug 25, 2020 at 7:39 PM narhiro <blackperl.narita9(a)gmail.com> wrote: > > > > "Port 0 is a reserved port, which means it should not be used by > > applications. Network abuse has prompted the need to block this port." > > > > "What about UDP IP fragmentation?" > > > > I'm not sure I follow this. The IP packet will be fragmented with UDP > > inside it. When the IP packet gets put together the UDP PDU will have > > a port number. It's possible that some packet analyzers or network > > gear will improperly "see" a partial UDP flow as port 0 but that's a > > mischaracterization of the flow. > > > > > > Scott Helms > > > > Scott Helms > > > > > > > >>> On Tue, Aug 25, 2020 at 8:17 AM Job Snijders <job(a)ntt.net> wrote: > >>> > >>>> On Tue, Aug 25, 2020 at 07:27:33AM -0400, K. Scott Helms wrote: > >>> I think a fairly easy thing to do is see what other large retail ISPs > >>> have done. Comcast, as an example, lists all of the ports they block > >>> and 0 is blocked. I do recommend that port 0 be blocked by all of the > >>> ISPs I work with and frankly Comcast's list is a pretty good one to > >>> use in general, though you will get some pushback on things like SMTP. > >>> https://www.xfinity.com/support/articles/list-of-blocked-ports > >> > >> I may be reading the table incorrectly, but it seems to me Comcast is > >> *not* blocking UDP port 0 according to the above URL? > >> > >>> Transit providers are a little bit different, but then again port 0 is > >>> also different since AFAIK it's never had a legitimate use case. It's > >>> always been a reserved port. I'd personally block it if I ran a > >>> transit, but I'd be more willing to open it up for one of my large > >>> customers (in a limited way) than I would on the retail side. > >>> https://www.iana.org/assignments/service-names-port-numbers/service-names-p… > >> > >> What about UDP IP fragmentation? > >> > >> Kind regards, > >> > >> Job

2 2

RPKI chain of trust
by Fabiano D'Agostino 26 Aug '20

26 Aug '20

Good morning everyone, I have a doubt about RPKI chain of trust. The 5 RIRs hold a self-signed root certificate for all the resources they have in the registry. The root certificate is used to sign the LIR's certificates that lists LIR's resources. LIRs use their private key to sign ROAs. LIR's public key is used to verify ROAs signatures and RIRs public key is used to verify LIR's signatures. Is this correct? Thanks in advance, Fabiano

2 3

TCP and UDP Port 0 - Should an ISP or ITP Block it?
by Douglas Fischer 26 Aug '20

26 Aug '20

I think that the subject of the e-mail is very self-explanatory. With some analysis of what is running over our network, ISP or ITP, we will be able to see some TCP/UDP(mostly UDP) packets with source or destination to port 0. I can think of a genuine use of it. (Maybe someone cloud help me see what I'm not seen.) So I have two questions: a) Should an ISP block that Kind of traffic? (like anti-spoofing on BNG/B-RAS) b) Should a Transit Provider block that Kind of traffic? -- Douglas Fernando Fischer Engº de Controle e Automação

13 18

Re: TCP and UDP Port 0 - Should an ISP or ITP Block it?
by John Kristoff 25 Aug '20

25 Aug '20

On Tue, 25 Aug 2020 12:40:43 +0000 Pim van Stam <pim(a)vanstam-ict.nl> wrote: > Ohter opinions on this? IETF RFC 768 - User Datagram Protocol weighs in: "Source Port is an optional field, when meaningful, it indicates the port of the sending process, and may be assumed to be the port to which a reply should be addressed in the absence of any other information. If not used, a value of zero is inserted." In practice however, most applications I've seen that do not expect a response still set a non-zero value (e.g. flow-export, syslog). John

2 1

Recently Completed BGP Study on "Peerlock" Defensive Filtering
by Tyler McDaniel 25 Aug '20

25 Aug '20

Hello! My colleagues and I at the University of Tennessee recently completed a study on the “Peerlock” route leak protection system ( https://archive.nanog.org/sites/default/files/Snijders_Everyday_Practical_B…) and related defensive filtering techniques. Specifically, we probed for evidence of these systems on the control plane and attempted to locate filtering sites. Additionally, we evaluated the system's effectiveness in simulation. The pre-print of this paper is available at: https://arxiv.org/abs/2006.06576. While this work was previously mentioned here by Job Snijders, we want to make an additional push for comments from network operators. Our experimental design and findings in Section 3 may be of some interest. Most importantly, if any of the Tier 1 networks could confirm or challenge our findings with respect to their filter placement, that would be enormously helpful! We realize that this information is often secret/under NDA, but providing some element of ground truth would assist us in correctly evaluating our work. Thank you! Tyler McDaniel Graduate Research Assistant/PhD Candidate Computer Security Laboratory Department of Electrical Engineering and Computer Science University of Tennessee, Knoxville

1 0