- Test - lists.nanog.org

Weekly Routing Table Report
by cscora＠apnic.net 23 Jun '17

23 Jun '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, AusNOG, SANOG, PacNOG, MENOG, SAFNOG, SdNOG, BJNOG, CaribNOG 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 24 Jun, 2017 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 652252 Prefixes after maximum aggregation (per Origin AS): 253804 Deaggregation factor: 2.57 Unique aggregates announced (without unneeded subnets): 314199 Total ASes present in the Internet Routing Table: 57616 Prefixes per ASN: 11.32 Origin-only ASes present in the Internet Routing Table: 49870 Origin ASes announcing only one prefix: 22007 Transit ASes present in the Internet Routing Table: 7746 Transit-only ASes present in the Internet Routing Table: 221 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 41 Max AS path prepend of ASN ( 55644) 36 Prefixes from unregistered ASNs in the Routing Table: 50 Numnber of instances of unregistered ASNs: 54 Number of 32-bit ASNs allocated by the RIRs: 19170 Number of 32-bit ASNs visible in the Routing Table: 14928 Prefixes from 32-bit ASNs in the Routing Table: 60687 Number of bogon 32-bit ASNs visible in the Routing Table: 62 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 365 Number of addresses announced to Internet: 2850215268 Equivalent to 169 /8s, 226 /16s and 213 /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: 98.7 Total number of prefixes smaller than registry allocations: 217120 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 178941 Total APNIC prefixes after maximum aggregation: 51343 APNIC Deaggregation factor: 3.49 Prefixes being announced from the APNIC address blocks: 178085 Unique aggregates announced from the APNIC address blocks: 73610 APNIC Region origin ASes present in the Internet Routing Table: 8215 APNIC Prefixes per ASN: 21.68 APNIC Region origin ASes announcing only one prefix: 2309 APNIC Region transit ASes present in the Internet Routing Table: 1158 Average APNIC Region AS path length visible: 4.4 Max APNIC Region AS path length visible: 41 Number of APNIC region 32-bit ASNs visible in the Routing Table: 3044 Number of APNIC addresses announced to Internet: 763609444 Equivalent to 45 /8s, 131 /16s and 193 /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: 198554 Total ARIN prefixes after maximum aggregation: 94628 ARIN Deaggregation factor: 2.10 Prefixes being announced from the ARIN address blocks: 200377 Unique aggregates announced from the ARIN address blocks: 92081 ARIN Region origin ASes present in the Internet Routing Table: 17909 ARIN Prefixes per ASN: 11.19 ARIN Region origin ASes announcing only one prefix: 6615 ARIN Region transit ASes present in the Internet Routing Table: 1777 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: 2051 Number of ARIN addresses announced to Internet: 1110770080 Equivalent to 66 /8s, 53 /16s and 1 /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: 175121 Total RIPE prefixes after maximum aggregation: 85690 RIPE Deaggregation factor: 2.04 Prefixes being announced from the RIPE address blocks: 170888 Unique aggregates announced from the RIPE address blocks: 102704 RIPE Region origin ASes present in the Internet Routing Table: 24145 RIPE Prefixes per ASN: 7.08 RIPE Region origin ASes announcing only one prefix: 11099 RIPE Region transit ASes present in the Internet Routing Table: 3397 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 33 Number of RIPE region 32-bit ASNs visible in the Routing Table: 5946 Number of RIPE addresses announced to Internet: 712074880 Equivalent to 42 /8s, 113 /16s and 102 /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: 82434 Total LACNIC prefixes after maximum aggregation: 18319 LACNIC Deaggregation factor: 4.50 Prefixes being announced from the LACNIC address blocks: 83737 Unique aggregates announced from the LACNIC address blocks: 38492 LACNIC Region origin ASes present in the Internet Routing Table: 6049 LACNIC Prefixes per ASN: 13.84 LACNIC Region origin ASes announcing only one prefix: 1656 LACNIC Region transit ASes present in the Internet Routing Table: 1115 Average LACNIC Region AS path length visible: 5.4 Max LACNIC Region AS path length visible: 36 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 3566 Number of LACNIC addresses announced to Internet: 170779616 Equivalent to 10 /8s, 45 /16s and 227 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-266652 + 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: 17105 Total AfriNIC prefixes after maximum aggregation: 3779 AfriNIC Deaggregation factor: 4.53 Prefixes being announced from the AfriNIC address blocks: 18800 Unique aggregates announced from the AfriNIC address blocks: 6987 AfriNIC Region origin ASes present in the Internet Routing Table: 1049 AfriNIC Prefixes per ASN: 17.92 AfriNIC Region origin ASes announcing only one prefix: 327 AfriNIC Region transit ASes present in the Internet Routing Table: 202 Average AfriNIC Region AS path length visible: 4.9 Max AfriNIC Region AS path length visible: 21 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 321 Number of AfriNIC addresses announced to Internet: 92555264 Equivalent to 5 /8s, 132 /16s and 72 /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 5552 4190 74 ERX-CERNET-BKB China Education and Rese 7545 3933 404 358 TPG-INTERNET-AP TPG Telecom Limited, AU 17974 2976 902 73 TELKOMNET-AS2-AP PT Telekomunikasi Indo 4766 2809 11135 760 KIXS-AS-KR Korea Telecom, KR 9829 2749 1499 540 BSNL-NIB National Internet Backbone, IN 9808 2204 8699 34 CMNET-GD Guangdong Mobile Communication 4755 2087 422 221 TATACOMM-AS TATA Communications formerl 45899 2012 1407 107 VNPT-AS-VN VNPT Corp, VN 7552 1628 1105 71 VIETEL-AS-AP Viettel Corporation, VN 9498 1592 360 138 BBIL-AP BHARTI Airtel Ltd., IN 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 22773 3809 2953 160 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 6327 3395 1333 81 SHAW - Shaw Communications Inc., CA 6389 2064 3671 39 BELLSOUTH-NET-BLK - BellSouth.net Inc., 18566 2053 405 109 MEGAPATH5-US - MegaPath Corporation, US 20115 2009 2171 419 CHARTER-NET-HKY-NC - Charter Communicat 209 1825 5069 641 CENTURYLINK-US-LEGACY-QWEST - Qwest Com 16509 1808 3647 587 AMAZON-02 - Amazon.com, Inc., US 30036 1791 325 307 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 6983 1695 854 231 ITCDELTA - Earthlink, Inc., US 701 1563 10562 633 UUNET - MCI Communications Services, In 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 3338 187 22 ALJAWWALSTC-AS, SA 20940 2897 964 2086 AKAMAI-ASN1, US 8551 2892 377 40 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 34984 2026 329 393 TELLCOM-AS, TR 9121 1963 1691 17 TTNET, TR 12479 1610 1044 53 UNI2-AS, ES 13188 1601 99 55 TRIOLAN, UA 12389 1525 1408 627 ROSTELECOM-AS, RU 6849 1225 355 21 UKRTELNET, UA 8402 1155 544 15 CORBINA-AS OJSC "Vimpelcom", RU 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 10620 3548 546 153 Telmex Colombia S.A., CO 8151 2514 3402 576 Uninet S.A. de C.V., MX 11830 2086 369 57 Instituto Costarricense de Electricidad 7303 1571 1011 249 Telecom Argentina S.A., AR 6503 1542 437 53 Axtel, S.A.B. de C.V., MX 6147 1299 377 27 Telefonica del Peru S.A.A., PE 3816 1026 501 94 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 28573 968 2298 188 CLARO S.A., BR 11172 915 126 82 Alestra, S. de R.L. de C.V., MX 18881 896 1052 23 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 1254 398 48 LINKdotNET-AS, EG 37611 724 91 8 Afrihost, ZA 36903 712 358 126 MT-MPLS, MA 36992 643 1375 26 ETISALAT-MISR, EG 24835 498 850 15 RAYA-AS, EG 37492 407 320 75 ORANGE-, TN 29571 401 36 10 CITelecom-AS, CI 15399 353 35 7 WANANCHI-, KE 8452 345 1730 17 TE-AS TE-AS, EG 2018 300 327 74 TENET-1, ZA 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 5552 4190 74 ERX-CERNET-BKB China Education and Rese 7545 3933 404 358 TPG-INTERNET-AP TPG Telecom Limited, AU 22773 3809 2953 160 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 10620 3548 546 153 Telmex Colombia S.A., CO 6327 3395 1333 81 SHAW - Shaw Communications Inc., CA 39891 3338 187 22 ALJAWWALSTC-AS, SA 17974 2976 902 73 TELKOMNET-AS2-AP PT Telekomunikasi Indo 20940 2897 964 2086 AKAMAI-ASN1, US 8551 2892 377 40 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 4766 2809 11135 760 KIXS-AS-KR Korea Telecom, KR Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 22773 3809 3649 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 7545 3933 3575 TPG-INTERNET-AP TPG Telecom Limited, AU 10620 3548 3395 Telmex Colombia S.A., CO 39891 3338 3316 ALJAWWALSTC-AS, SA 6327 3395 3314 SHAW - Shaw Communications Inc., CA 17974 2976 2903 TELKOMNET-AS2-AP PT Telekomunikasi Indonesia, I 8551 2892 2852 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 9829 2749 2209 BSNL-NIB National Internet Backbone, IN 9808 2204 2170 CMNET-GD Guangdong Mobile Communication Co.Ltd. 4766 2809 2049 KIXS-AS-KR Korea Telecom, KR Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 65602 UNALLOCATED 8.225.192.0/24 30372 SUNESYS2 - Sunesys, LLC, US 65000 PRIVATE 31.219.177.0/25 8966 ETISALAT-AS P.O. Box 1150, Dub 65000 PRIVATE 31.219.177.128/25 8966 ETISALAT-AS P.O. Box 1150, Dub 65010 PRIVATE 46.56.192.0/21 42772 VELCOM-AS, BY 65010 PRIVATE 46.56.224.0/21 42772 VELCOM-AS, BY 65001 PRIVATE 46.237.40.0/21 13118 ASN-YARTELECOM PJSC Rostelecom 65538 DOCUMENT 64.27.253.0/24 1273 CW Vodafone Group PLC, GB 65346 PRIVATE 94.50.36.0/22 31094 TTKNET Tyumen, Russia, RU 64111 UNALLOCATED 98.159.5.0/24 19555 KMI-NETWORK - Kinder Morgan, I 64111 UNALLOCATED 98.159.7.0/24 19555 KMI-NETWORK - Kinder Morgan, I Complete listing at http://thyme.rand.apnic.net/current/data-badAS Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 14.192.48.0/24 134833 LIHGL-HK LANLIAN INTERNATIONAL HOLDING GROUP LIMITE 14.192.49.0/24 134833 LIHGL-HK LANLIAN INTERNATIONAL HOLDING GROUP LIMITE 14.192.50.0/24 134833 LIHGL-HK LANLIAN INTERNATIONAL HOLDING GROUP LIMITE 14.192.51.0/24 134833 LIHGL-HK LANLIAN INTERNATIONAL HOLDING GROUP LIMITE 23.226.112.0/20 62788 -Reserved AS-, ZZ 27.100.7.0/24 56096 UNKNOWN 36.255.250.0/24 64091 UNKNOWN 41.76.232.0/21 62878 XLITT - Xlitt, US 41.77.248.0/21 62878 XLITT - Xlitt, US 41.78.12.0/23 62878 XLITT - Xlitt, US 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:13 /10:36 /11:104 /12:280 /13:547 /14:1049 /15:1848 /16:13482 /17:7630 /18:13448 /19:24686 /20:38583 /21:41236 /22:77532 /23:64266 /24:365232 /25:875 /26:612 /27:643 /28:43 /29:34 /30:27 /31:3 /32:28 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 6327 3187 3395 SHAW - Shaw Communications Inc., CA 22773 2974 3809 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 39891 2898 3338 ALJAWWALSTC-AS, SA 8551 2357 2892 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 18566 1946 2053 MEGAPATH5-US - MegaPath Corporation, US 30036 1584 1791 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Communi 11830 1476 2086 Instituto Costarricense de Electricidad y Telec 10620 1473 3548 Telmex Colombia S.A., CO 11492 1373 1518 CABLEONE - CABLE ONE, INC., US 6389 1371 2064 BELLSOUTH-NET-BLK - BellSouth.net Inc., US Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1602 2:824 4:18 5:2437 6:34 8:1037 12:1834 13:120 14:1751 15:27 16:2 17:126 18:91 20:61 23:2373 24:1871 25:2 27:2445 31:1914 32:82 33:14 35:20 36:417 37:2346 38:1328 39:57 40:97 41:3026 42:483 43:1929 44:72 45:2820 46:2790 47:155 49:1233 50:989 51:18 52:830 54:362 55:7 56:4 57:42 58:1583 59:1052 60:391 61:1957 62:1603 63:1914 64:4547 65:2219 66:4550 67:2272 68:1241 69:3402 70:1149 71:586 72:2200 74:2687 75:386 76:432 77:1504 78:1462 79:2268 80:1407 81:1391 82:996 83:719 84:895 85:1750 86:478 87:1158 88:763 89:2101 90:176 91:6191 92:976 93:2384 94:2380 95:2710 96:632 97:354 98:1052 99:86 100:154 101:1198 103:15094 104:2935 105:182 106:503 107:1706 108:820 109:2903 110:1455 111:1726 112:1199 113:1255 114:1027 115:1720 116:1795 117:1702 118:2201 119:1608 120:1043 121:1109 122:2262 123:1827 124:1494 125:1898 128:791 129:648 130:431 131:1403 132:527 133:199 134:656 135:225 136:459 137:438 138:1941 139:494 140:395 141:592 142:759 143:892 144:795 145:182 146:1028 147:688 148:1436 149:573 150:700 151:978 152:707 153:304 154:815 155:751 156:604 157:645 158:453 159:1507 160:672 161:744 162:2526 163:537 164:799 165:1393 166:386 167:1249 168:2700 169:785 170:3400 171:319 172:1014 173:1931 174:809 175:749 176:1882 177:4064 178:2475 179:1144 180:2211 181:1898 182:2363 183:995 184:866 185:9985 186:3168 187:2232 188:2703 189:1805 190:8234 191:1366 192:9477 193:5789 194:4661 195:3914 196:2111 197:1295 198:5502 199:5897 200:7442 201:4319 202:10358 203:9980 204:4479 205:2821 206:3015 207:3112 208:3990 209:3928 210:3969 211:2145 212:2849 213:2497 214:879 215:66 216:5680 217:2110 218:861 219:600 220:1692 221:913 222:773 223:1178 End of report

1 0

Reliability of Juniper MIC3-3D-1X100GE-CFP and CFP in general
by Eric Dugas 22 Jun '17

22 Jun '17

Hello, We're planning to phase out some 10G link-aggregations in favor of 100G interfaces. We've been looking at buying MIC3-3D-1X100GE-CFP, MPC3E and Fiberstore CFPs. I've been told that CFPs (in general) weren't that reliable. They were kinda "replaced" almost a year and a half or so after its introduction by CFP2 and then by CFP4 and so on. Size and power consumption aside, are the MIC3-3D-1X100GE-CFP and CFP modules reliable at all? Are they the SFP-TX of the 100GBase? Eric

2 1

Re: Long AS Path
by Jakob Heitz (jheitz) 22 Jun '17

22 Jun '17

23456 is AS_TRANS. Either your router does not support 4 byte AS or there is a bug at AS 12956 or AS 12956 is intentionally prepending 23456. Thanks, Jakob. > > Date: Tue, 20 Jun 2017 23:12:45 +0000 > From: James Braunegg <james.braunegg(a)micron21.com> > To: "nanog(a)nanog.org" <nanog(a)nanog.org> > Subject: Long AS Path > Message-ID: <e679487be750411a874b7376a7037aa9(a)EX-01.m21.local> > Content-Type: text/plain; charset="us-ascii" > > Dear All > > Just wondering if anyone else saw this yesterday afternoon ? > > Jun 20 16:57:29:E:BGP: From Peer 38.X.X.X received Long AS_PATH= AS_SEQ(2) 174 12956 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 ... attribute length (567) More than configured MAXAS-LIMIT > > Jun 20 16:15:26:E:BGP: From Peer 78.X.X.X received Long AS_PATH= AS_SEQ(2) 5580 3257 12956 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 ... attribute length (568) More than configured MAXAS-LIMIT > > Someone is having fun, creating weird and wonderful long AS paths based around AS 23456, we saw the same pattern of data from numerous upstream providers. > > Kindest Regards, > > James Braunegg > >

1 0

Re: PCIe adapters supporting long distance 10GB fiber?
by Jason Alderfer 21 Jun '17

21 Jun '17

On Tue, Jun 20, 2017 at 11:15 AM, Baldur Norddahl <baldur.norddahl(a)gmail.com > wrote: > The real question here is: will my NIC support other SFP+ modules than the > few options carried by the NIC vendor? Has anyone tried changing the vendor ID of an SFP+ with one of these? https://sfptotal.com/ I am highly intrigued and skeptical. Jason

1 0

Re: Vendors spamming NANOG attendees
by Anne P. Mitchell Esq. 21 Jun '17

21 Jun '17

> On 6/13/17 10:28 PM, Mel Beckman wrote: >> But as I said, harvesting emails is not illegal under can spam. But it is illegal under the laws of nearly every other technology-enabled developed country. And there are at least a few people on this list who are in those countries. And once GDPR goes into effect there will be even more available remedies. Anne* *Dictated due to broken wrist, please forgive top posting and any weird grammar or typos. Anne P. Mitchell, Attorney at Law Legislative Consultant CEO/President, Institute for Social Internet Public Policy Member, Cal. Bar Cyberspace Law Committee Member, Colorado Cyber Committee Member, Elevations Credit Union Member Council Member, Board of Directors, Asilomar Microcomputer Workshop Member, Board of Directors, Greenwood Wildlife Rehabilitation Author: Section 6 of the CAN-SPAM Act of 2003 (the Federal anti-spam law) Ret. Professor of Law, Lincoln Law School of San Jose Ret. Chair, Asilomar Microcomputer Workshop

1 0

Why the internal network delays, Gmail?
by Nate Metheny 21 Jun '17

21 Jun '17

Help (and hi)! I work in higher education and we've been experiencing problems with Google delaying or queuing email for delivery to our domain. Here's some truncated email headers: ** Example 1: X-Received: by 10.237.55.65 with SMTP id i59mr10986018qtb.62.1472137448952; Thu, 25 Aug 2016 08:04:08 -0700 (PDT) Received: by mail-qt0-f175.google.com with SMTP id u25so27419242qtb.1 for <@***>; Thu, 25 Aug 2016 12:05:46 -0700 (PDT) ** Example 2: X-Received: by 10.36.1.75 with SMTP id 72mr5275579itk.40.1472130531887; Thu, 25 Aug 2016 06:08:51 -0700 (PDT) Received: by mail-it0-f48.google.com with SMTP id x131so289116132ite.0 for <@***>; Thu, 25 Aug 2016 11:50:42 -0700 (PDT) In both of these examples, these emails haven't even left Google's internal network yet; I'm getting blamed for these delays, however there is no delay in receiving these emails after they leave Google's network. Are other people having this same problem? I've tested delivery to my network from many outside sources and all SMTP requests go through without delay; this issue seems be exclusive to Google-hosted and Gmail accounts and domains. -- Nate <natemetheny(a)gmail.com>nate(a)dopedesign.com

14 21

Google Cloud and IX - Traffic behavior
by Alain Hebert 21 Jun '17

21 Jun '17

Hi, Anyone aware of different traffic behavior depending if the target goes through normal peering than through an exchanges google exists in? We're facing a weird issue where the same GCLD Instance can upload up to 200Mbps (Ref 1) if the target path goes through, lets say TorIX, but cannot get more than 20Mbps on similar hosts (8 of them) sittings on our peering links. PS; Those sames hosts get up to their link limit ( 1Gbps ) between each others and others test points we have; PS: Wireshark capture show nothing abnormal; PS: Links aren't congested, and so on... Ref 1 - 200Mbps is on a link rate-limited to 300Mbps. Its my only test point with a TorIX access -- ----- Alain Hebert ahebert(a)pubnix.net PubNIX Inc. 50 boul. St-Charles P.O. Box 26770 Beaconsfield, Quebec H9W 6G7 Tel: 514-990-5911 http://www.pubnix.net Fax: 514-990-9443

4 7

Re: PCIe adapters supporting long distance 10GB fiber?
by Baldur Norddahl 21 Jun '17

21 Jun '17

But what foundation do you have for asserting that switch hardware is any different in this regard? I can say that we are using 80 km modules in various hardware without any issues. I admittedly do not use any high power modules in servers, but I will need better evidence than this to assume that it would not work just fine. Den 20. jun. 2017 22.24 skrev "Denys Fedoryshchenko" <denys(a)visp.net.lb>: On 2017-06-20 22:07, Baldur Norddahl wrote: > I would expect anything mounted in a computer to have all the power you > could want. It is not like the ATX power supply cares about an extra watt > or two. > > As I understand the issue it is more about cooling than power and is > primarly a concern in high density switches were you could have 48 or more > to power and cool. > SFP needs 3.3V, it might be supplied from regulator on the card or directly PCI-Express, can't be absolutely sure, in reference design it is just 3.3V_NIA and then filter, also reference design SFP power circuit define max 750mA/3.3V max to SFP, thats only 2.475W. FTLX1471D3BCV (10km SM) - up to 285mA FTLX1671D3BCL (40km SM) - up to 400mA, and thumb rule in electronics it is better to not exceed 50% of max specs of designed max current, as for many parts it is stated for 25C & etc operating conditions. I expect it might work, but noone knows how long, and how reliable, if it is not cooled very well. And 82599 sensitive to cooling(it is very old card after all), as soon as it is not enough, it starts to glitch. > > Den 20. jun. 2017 18.09 skrev "Denys Fedoryshchenko" <denys(a)visp.net.lb>: > > I guess it depends on NIC, there is many spinoffs of Intel X520 with much >> weaker power supply circuitry. >> It might work with good NIC, but you can't rely on it on long term, IMHO. >> Even 40km Finisar SFP+ has Pdiss 1.5W. Also they mention: "The typical >> power consumption of the FTLX1672D3BTL may exceed the limit of 1.5W >> specified for the Power Level II transceivers" >> If we talk about 80km, Pdiss is 1.8W. >> While 10GBASE-LR is <1W >> >> On 2017-06-20 16:30, Max Tulyev wrote: >> >> We use Intel NICs with SFP+ holes. It works good with long and short >>> range SFP+ modules, including CWDM/DWDM. >>> >>> On 15.06.17 12:10, chiel wrote: >>> >>> Hello, >>>> >>>> We are deploying more and more server based routers (based on BSD). We >>>> have now come to the point where we need to have 10GB uplinks one these >>>> devices and I prefer to plug in a long range 10GB fiber straight into >>>> the server without it going first into a router/switch from vendor x. It >>>> seems to me that all the 10GB PCIe cards only support either copper >>>> 10GBASE-T, short range 10GBASE-SR or the 10 Km 10GBASE-LR (but only very >>>> few). Are there any PCIe cards that support 10GBASE-ER and 10GBASE-ZR? I >>>> can't seem to find any. >>>> >>>> Chiel >>>> >>>> >>>>

3 2

Re: Vendors spamming NANOG attendees
by Scott Weeks 20 Jun '17

20 Jun '17

--- nanog(a)nanog.org wrote: From: i mawsog via NANOG <nanog(a)nanog.org> :: Agree, this thread has generated more "spam" or noise :: for all of us collectively. It's not spam. Look up the definition of spam. Also, just block the thread in your email client. :: Some amount of relevant "spam" has to be tolerated for :: vendor to continue supporting NANOG. No, that is absolutely wrong! :: Also relevant "spam" or sales call is a good way to find :: out about new technologies , that one may not have heard :: about otherwise. No, wrong again. One of the most attractive things about NANOG is learning these things from **peers**, not spam. :: Another tip, just ignore, the "spammer" will go away :: eventually. If they're not named-n-shamed they will continue. I have had quite a few go after me aggressively to sell me something after a NANOG post. They didn't stop until I named-n-shamed them. Their supervisors wrote me, personally apologized and, due to that, I put their companies back on my list of companies to do business with. I write this not just to you, but as an explanation to other new folks why the old schoolers name-n-shame. scott

1 0

Re: Vendors spamming NANOG attendees
by tim＠pelican.org 20 Jun '17

20 Jun '17

On Tuesday, 20 June, 2017 14:26, "Rod Beck" <rod.beck(a)unitedcablecompany.com> said: > And how do you tell if an address was scraped or not? There are databases and > zillions of other ways of gaining addresses. > > > I doubt you can distinguish the source with any real reliability. Depending on whether you're registered with personal or corporate email, and how much control you have over the platform in question, you can distinguish the source with fairly high reliability. Just generate a new 'bob+nanog70(a)bobsdomain.org' style address for every event you register for, every website that requires a contact address, every mailing list, ... If you're concerned that people will twig, and use the naked 'bob@' address, you could work with multiple names including a hash that look like internal nonsense, e.g. 'bob34adf@', or block the un-plussed 'bob@' entirely and use e.g. 'robert@' for people you trust to have your real, non-circumstance-specific email address. I know people who do this, it really depends how much you care about being able to trace and block people who are either scraping or re-selling your details. Regards, Tim.

4 4