November 2013 - Test - lists.nanog.org

TW Telecom Latency
by Babak Pasdar 26 Nov '13

26 Nov '13

Can someone from TW Telecom IP services connect with us to work through an issue. We are seeing ~90ms latency between LA and New Mexico with the most notable time being from San Jose to Albuquerque within the TW Telecom network. 1 74.123.203.137 (74.123.203.137) 4.661 ms 4.602 ms 4.570 ms 2 xe-8-3-1.er1.lax112.us.above.net (209.66.118.225) 15.129 ms 15.143 ms 15.150 ms 3 xe-1-1-0.cr1.lax112.us.above.net (64.125.30.246) 0.936 ms 0.930 ms 0.920 ms 4 xe-0-2-0.cr1.sjc2.us.above.net (64.125.26.26) 9.219 ms 9.186 ms 9.212 ms 5 ae1.mpr3.sjc7.us.above.net (64.125.24.2) 9.208 ms 12.212 ms 12.274 ms 6 snjs.equinix.twtelecom.net (206.223.116.36) 12.036 ms 11.132 ms 11.112 ms 7 abq1-ar4-ge-1-0-0-0.us.twtelecom.net (66.192.249.58) 81.883 ms 81.889 ms 81.868 ms 8 10.208.169.222 (10.208.169.222) 87.492 ms 87.037 ms 87.456 ms 9 speedy.bbbnm.org (207.201.250.86) 89.671 ms 90.753 ms 90.740 ms Thanks, Babak

1 0

Weekly Routing Table Report
by Routing Analysis Role Account 26 Nov '13

26 Nov '13

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, LacNOG, TRNOG, CaribNOG and the RIPE Routing Working Group. 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 0400 +10GMT Sat 23 Nov, 2013 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 472996 Prefixes after maximum aggregation: 189628 Deaggregation factor: 2.49 Unique aggregates announced to Internet: 234531 Total ASes present in the Internet Routing Table: 41350 Prefixes per ASN: 11.44 Origin-only ASes present in the Internet Routing Table: 35408 Origin ASes announcing only one prefix: 16278 Transit ASes present in the Internet Routing Table: 5942 Transit-only ASes present in the Internet Routing Table: 166 Average AS path length visible in the Internet Routing Table: 4.6 Max AS path length visible: 103 Max AS path prepend of ASN ( 50404) 101 Prefixes from unregistered ASNs in the Routing Table: 985 Unregistered ASNs in the Routing Table: 282 Number of 32-bit ASNs allocated by the RIRs: 5399 Number of 32-bit ASNs visible in the Routing Table: 0 Prefixes from 32-bit ASNs in the Routing Table: 13142 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 1166 Number of addresses announced to Internet: 2654800220 Equivalent to 158 /8s, 61 /16s and 9 /24s Percentage of available address space announced: 71.7 Percentage of allocated address space announced: 71.7 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 95.3 Total number of prefixes smaller than registry allocations: 165017 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 111990 Total APNIC prefixes after maximum aggregation: 34022 APNIC Deaggregation factor: 3.29 Prefixes being announced from the APNIC address blocks: 114240 Unique aggregates announced from the APNIC address blocks: 47745 APNIC Region origin ASes present in the Internet Routing Table: 4875 APNIC Prefixes per ASN: 23.43 APNIC Region origin ASes announcing only one prefix: 1219 APNIC Region transit ASes present in the Internet Routing Table: 835 Average APNIC Region AS path length visible: 4.6 Max APNIC Region AS path length visible: 35 Number of APNIC region 32-bit ASNs visible in the Routing Table: 0 Number of APNIC addresses announced to Internet: 728686528 Equivalent to 43 /8s, 110 /16s and 223 /24s Percentage of available APNIC address space announced: 85.2 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-63999, 131072-133631 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: 162923 Total ARIN prefixes after maximum aggregation: 81714 ARIN Deaggregation factor: 1.99 Prefixes being announced from the ARIN address blocks: 163759 Unique aggregates announced from the ARIN address blocks: 75912 ARIN Region origin ASes present in the Internet Routing Table: 15939 ARIN Prefixes per ASN: 10.27 ARIN Region origin ASes announcing only one prefix: 6003 ARIN Region transit ASes present in the Internet Routing Table: 1658 Average ARIN Region AS path length visible: 4.1 Max ARIN Region AS path length visible: 24 Number of ARIN region 32-bit ASNs visible in the Routing Table: 0 Number of ARIN addresses announced to Internet: 1073967232 Equivalent to 64 /8s, 3 /16s and 112 /24s Percentage of available ARIN address space announced: 56.8 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, 393216-394239 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: 119427 Total RIPE prefixes after maximum aggregation: 61061 RIPE Deaggregation factor: 1.96 Prefixes being announced from the RIPE address blocks: 123136 Unique aggregates announced from the RIPE address blocks: 78812 RIPE Region origin ASes present in the Internet Routing Table: 17527 RIPE Prefixes per ASN: 7.03 RIPE Region origin ASes announcing only one prefix: 8293 RIPE Region transit ASes present in the Internet Routing Table: 2826 Average RIPE Region AS path length visible: 5.1 Max RIPE Region AS path length visible: 103 Number of RIPE region 32-bit ASNs visible in the Routing Table: 0 Number of RIPE addresses announced to Internet: 656226532 Equivalent to 39 /8s, 29 /16s and 56 /24s Percentage of available RIPE address space announced: 95.4 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, 196608-200191 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: 53080 Total LACNIC prefixes after maximum aggregation: 10038 LACNIC Deaggregation factor: 5.29 Prefixes being announced from the LACNIC address blocks: 58307 Unique aggregates announced from the LACNIC address blocks: 27085 LACNIC Region origin ASes present in the Internet Routing Table: 2040 LACNIC Prefixes per ASN: 28.58 LACNIC Region origin ASes announcing only one prefix: 553 LACNIC Region transit ASes present in the Internet Routing Table: 390 Average LACNIC Region AS path length visible: 4.9 Max LACNIC Region AS path length visible: 35 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 0 Number of LACNIC addresses announced to Internet: 143625784 Equivalent to 8 /8s, 143 /16s and 142 /24s Percentage of available LACNIC address space announced: 85.6 LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 262144-263679 plus 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: 11750 Total AfriNIC prefixes after maximum aggregation: 2600 AfriNIC Deaggregation factor: 4.52 Prefixes being announced from the AfriNIC address blocks: 12388 Unique aggregates announced from the AfriNIC address blocks: 4039 AfriNIC Region origin ASes present in the Internet Routing Table: 689 AfriNIC Prefixes per ASN: 17.98 AfriNIC Region origin ASes announcing only one prefix: 210 AfriNIC Region transit ASes present in the Internet Routing Table: 139 Average AfriNIC Region AS path length visible: 4.7 Max AfriNIC Region AS path length visible: 24 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 0 Number of AfriNIC addresses announced to Internet: 48324352 Equivalent to 2 /8s, 225 /16s and 95 /24s Percentage of available AfriNIC address space announced: 48.0 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 4766 2931 11557 940 Korea Telecom (KIX) 17974 2714 902 88 PT TELEKOMUNIKASI INDONESIA 7545 2111 319 111 TPG Internet Pty Ltd 4755 1792 392 190 TATA Communications formerly 9829 1543 1245 45 BSNL National Internet Backbo 9583 1246 95 509 Sify Limited 9498 1210 309 73 BHARTI Airtel Ltd. 7552 1165 1080 13 Vietel Corporation 4808 1144 2119 337 CNCGROUP IP network: China169 24560 1095 380 166 Bharti Airtel Ltd., Telemedia 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 6389 3042 3688 53 BellSouth.net Inc. 22773 2208 2941 141 Cox Communications, Inc. 1785 2058 686 145 PaeTec Communications, Inc. 18566 2055 379 178 MegaPath Corporation 20115 1681 1655 598 Charter Communications 4323 1641 1098 419 Time Warner Telecom 701 1509 11162 784 MCI Communications Services, 30036 1388 313 578 Mediacom Communications Corp 7018 1331 17778 870 AT&T WorldNet Services 6983 1294 756 580 ITC^Deltacom 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 8402 1923 544 16 OJSC "Vimpelcom" 34984 1367 244 223 TELLCOM ILETISIM HIZMETLERI A 20940 1164 437 871 Akamai Technologies European 31148 1009 45 19 FreeNet ISP 13188 895 99 48 TOV "Bank-Inform" 6849 869 363 39 JSC UKRTELECOM, 8551 787 370 41 Bezeq International 6830 773 2327 425 UPC Distribution Services 12479 679 797 57 Uni2 Autonomous System 35228 548 246 16 Avatar Broadband Limited 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 28573 3306 1781 123 NET Servicos de Comunicao S.A 10620 2670 433 213 Telmex Colombia S.A. 7303 1729 1151 232 Telecom Argentina Stet-France 18881 1647 908 20 Global Village Telecom 8151 1358 2850 419 UniNet S.A. de C.V. 11830 866 364 15 Instituto Costarricense de El 27947 819 94 92 Telconet S.A 6503 793 434 62 AVANTEL, S.A. 6147 790 373 27 Telefonica Del Peru 7738 780 1498 36 Telecomunicacoes da Bahia S.A 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 36998 1864 112 5 Sudanese Mobile Telephone (ZA 24863 888 338 26 LINKdotNET AS number 6713 554 633 26 Itissalat Al-MAGHRIB 8452 411 956 9 TEDATA 24835 297 144 9 RAYA Telecom - Egypt 3741 256 921 214 The Internet Solution 29571 226 17 13 Ci Telecom Autonomous system 15706 221 32 6 Sudatel Internet Exchange Aut 36992 219 501 29 Etisalat MISR 29975 192 668 21 Vodacom 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 28573 3306 1781 123 NET Servicos de Comunicao S.A 6389 3042 3688 53 BellSouth.net Inc. 4766 2931 11557 940 Korea Telecom (KIX) 17974 2714 902 88 PT TELEKOMUNIKASI INDONESIA 10620 2670 433 213 Telmex Colombia S.A. 22773 2208 2941 141 Cox Communications, Inc. 7545 2111 319 111 TPG Internet Pty Ltd 1785 2058 686 145 PaeTec Communications, Inc. 18566 2055 379 178 MegaPath Corporation 8402 1923 544 16 OJSC "Vimpelcom" Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 6389 3042 2989 BellSouth.net Inc. 17974 2714 2626 PT TELEKOMUNIKASI INDONESIA 10620 2670 2457 Telmex Colombia S.A. 22773 2208 2067 Cox Communications, Inc. 7545 2111 2000 TPG Internet Pty Ltd 4766 2931 1991 Korea Telecom (KIX) 1785 2058 1913 PaeTec Communications, Inc. 8402 1923 1907 OJSC "Vimpelcom" 18566 2055 1877 MegaPath Corporation 36998 1864 1859 Sudanese Mobile Telephone (ZA Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 62828 UNALLOCATED 8.21.130.0/24 4323 Time Warner Telecom 62850 UNALLOCATED 8.25.147.0/24 3356 Level 3 Communicatio 62734 UNALLOCATED 8.31.128.0/24 6939 Hurricane Electric 62773 UNALLOCATED 8.35.180.0/22 3356 Level 3 Communicatio 65160 PRIVATE 12.1.58.0/24 17361 Sungard Trading Syst 65160 PRIVATE 12.1.59.0/24 17361 Sungard Trading Syst 15132 UNALLOCATED 12.9.150.0/24 7018 AT&T WorldNet Servic 62719 UNALLOCATED 12.27.130.0/24 4323 Time Warner Telecom 62861 UNALLOCATED 12.37.197.0/24 7018 AT&T WorldNet Servic 13317 UNALLOCATED 12.44.10.0/24 7018 AT&T WorldNet Servic Complete listing at http://thyme.rand.apnic.net/current/data-badAS Prefixes from private and non-routed address space (Global) ----------------------------------------------------------- Prefix Origin AS Description 100.100.0.0/24 4847 China Networks Inter-Exchange Complete listing at http://thyme.rand.apnic.net/current/data-dsua Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 23.90.128.0/18 27418 OUTOFWALL INC. 23.91.0.0/19 40676 Psychz Networks 23.91.4.0/24 40676 Psychz Networks 23.91.14.0/24 40676 Psychz Networks 23.91.21.0/24 40676 Psychz Networks 23.91.32.0/19 36315 Servpac Inc. 23.91.80.0/20 21560 Capital Technology Services G 23.91.96.0/20 37958 ChinaCache Networks ASN 23.91.112.0/21 32475 MidPhase Inc. 23.91.160.0/22 36493 3757277 Canada Inc. (oa 295.c 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:16 /9:11 /10:31 /11:92 /12:253 /13:474 /14:924 /15:1625 /16:12820 /17:6775 /18:11309 /19:23082 /20:32928 /21:35636 /22:49999 /23:43870 /24:250678 /25:871 /26:993 /27:467 /28:42 /29:69 /30:17 /31:0 /32:14 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 18566 2009 2055 MegaPath Corporation 36998 1829 1864 Sudanese Mobile Telephone (ZA 6389 1700 3042 BellSouth.net Inc. 8402 1594 1923 OJSC "Vimpelcom" 22773 1463 2208 Cox Communications, Inc. 30036 1232 1388 Mediacom Communications Corp 11492 1195 1233 Cable One 1785 1095 2058 PaeTec Communications, Inc. 6983 1035 1294 ITC^Deltacom 22561 964 1241 Digital Teleport, Inc Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:899 2:825 3:3 4:17 5:1027 6:21 8:624 12:1880 13:3 14:900 15:11 16:3 17:18 18:19 20:21 23:585 24:1757 27:1625 31:1506 32:45 33:2 34:5 36:86 37:1936 38:916 39:5 40:182 41:3235 42:290 44:14 46:2034 47:10 49:695 50:861 52:12 54:44 55:5 56:4 57:26 58:1165 59:575 60:368 61:1476 62:1247 63:1987 64:4325 65:2348 66:4160 67:2114 68:1093 69:3301 70:889 71:488 72:2012 74:2577 75:325 76:303 77:1158 78:1073 79:662 80:1272 81:1049 82:648 83:682 84:588 85:1260 86:375 87:1021 88:557 89:1562 90:152 91:5690 92:615 93:1611 94:2075 95:1554 96:515 97:348 98:1041 99:41 100:32 101:653 103:3675 105:527 106:141 107:218 108:536 109:1981 110:979 111:1119 112:597 113:812 114:753 115:1062 116:990 117:822 118:1184 119:1281 120:338 121:754 122:1872 123:1266 124:1397 125:1437 128:674 129:229 130:353 131:665 132:361 133:158 134:303 135:72 136:284 137:250 138:352 139:298 140:201 141:331 142:547 143:400 144:495 145:90 146:532 147:412 148:775 149:361 150:153 151:665 152:412 153:205 154:54 155:500 156:295 157:421 158:284 159:783 160:361 161:458 162:867 163:225 164:622 165:592 166:263 167:634 168:1043 169:125 170:1126 171:185 172:27 173:1591 174:694 175:526 176:1321 177:2472 178:1864 179:297 180:1597 181:859 182:1379 183:468 184:630 185:1057 186:2642 187:1484 188:1875 189:1265 190:7310 192:7078 193:5434 194:4026 195:3366 196:1340 197:1041 198:4766 199:5491 200:6055 201:2524 202:8976 203:8897 204:4546 205:2649 206:2833 207:2837 208:3985 209:3653 210:3047 211:1577 212:2151 213:1998 214:898 215:91 216:5423 217:1694 218:627 219:323 220:1277 221:585 222:328 223:509 End of report

1 0

BGP neighbor/configuration testing
by Eric A Louie 26 Nov '13

26 Nov '13

Scenario: a regional ISP preparing to cutover to a new upstream BGP provider at one of my POPs. Want minimal or no network disruption, and want to ensure everything is ready to go prior to the cutover. I'm planning to use the following order of operations: 1. Establish IP connectivity to the new ISP (already done) 2. Configure my BGP router and shutdown the new neighbor (ISP says their side is already configured and ready) 3. During the maintenance window for this change, activate the new BGP connection (remove neighbor shutdown) 4. Do the appropriate tests (sh bgp nei, login to my upstream's route server and check route advertisements, sign in to looking glass and/or route servers from other providers to see if my routes from the new ISP are being advertised, and I'm open to any other tests) 5. Turn down the old connection (neighbor shutdown) 6. Watch the old connection get removed from route servers/looking glasses from step 4 A. Does that order make sense or does it need some tweaking, additions, or "other"? B. I'd like to test the new upstream BGP configuration without passing traffic to and through it. What can I do (if anything) on my configuration end to put up the BGP configuration, establish a neighbor connection, and NOT actually pass any traffic through it? After putting my configuration up, I'd like to do a show bgp nei 1.1.1.1 advertised-routes to ensure my routes are going out, and then shut the neighbor down until the cutover. thanks for your input Eric

7 12

CenturyLink IP NOC Contact for BGP Changes
by Jawaid Desktop 26 Nov '13

26 Nov '13

Hello NANOGers, We're a regional CLEC and I've had a BGP filter change request in to CenturyLink for 3 days. I've had no luck trying to get this processed. I tried calling in tonight because, you know, my expectation these days is that every serious internet backbone company staffs a 24/7/365 NOC capable of dealing with IP and BGP routing issues / changes. I managed to escalate to a "TAC supervisor" who assures me that they in fact have nobody staffed after-hours who can do this kind of work. *boggles* I had no trouble getting the exact same request processed by XO, Cogent, Level3, Comcast, Cogent, and TWTelecom in anywhere from minutes to a few hours, many of them at night (you know, when it's kind of like better to do such changes anyway). So does anyone have the contact for a real, honest-to-god IP NOC engineer at CenturyLink? Or did I make a mistake assuming CenturyLink is a serious, carrier-class player? Thanks for any help. Jawaid

3 2

RE: telnet into a netgear switch?
by Jason Pope 26 Nov '13

26 Nov '13

------------------------------ Message: 2 Date: Sun, 24 Nov 2013 18:47:09 -0800 From: David Birdsong <david(a)imgix.com> To: nanog(a)nanog.org Subject: telnet into a netgear switch? Message-ID: <CAOMvUQfeM_Wnc=eS1vz0Gh_pp-vZ+sPRk9Td-1U0A34c3A6jdQ(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Hey all, last night while at the datacenter I was in a pinch to extend a rack's LAN. I compromised and ran out to the local Fry's to buy whatever switch I could find so as to allow some configuration to happen while we wait for the real network gear to show up. I left before confirming I could access the switch remotely; it was very late and I was pretty groggy and hey, any network gear has to be telnet'table this day and age. Of course I was mostly wrong. The switch expects some signed payload before allowing a telnet through. I found this: https://code.google.com/p/netgear-telnetenable/...but I'm having a hell of a time getting anything to respond. The most confounding part is the switch doesn't respond to a single SYN packet on low ports. I'm scanning all the ports now, but if nothing shows up, I'm not sure what a payload is good for if the switch doesn't ACK a single SYN. I'm curious if anybody's got any tips besides not using Netgear in the datacenter. I have the MAC, I've IP'd it via DHCP, and the model number: JGS524E and I can power cycle the switch as much as needed. P.S. long time listener, first time caller. i'm more of a sysadmin dangerously standing in for a proper network person. ------------------------------ Seems to me that you need to use their "Switch Configuration Utility" to manage the switch. I didn't read all the documentation, but that is what jumps out at me after a brief look. Maybe it will allow you to enable telnet or ssh from there. See the following link: http://downloadcenter.netgear.com/en/product/JGS524E Jason

4 5

Meraki
by Hank Disuko 26 Nov '13

26 Nov '13

Hi folks, I've traditionally been a Cisco Catalyst shop for my switching gear. I am doing a significant hardware refresh in one of my offices, which will entail replacing about 20 access switches and a couple core devices. Pretty simple L3 VLAN environment with VRRP/HSRP, on the physical end I have 1G fibre/copper and 10G fibre. My core switch of choice will likely be the Cat 4500 series. I'm considering Cisco's Meraki platform for my access layer and I'm looking for deployment stories of folks that have deployed Meraki in the past...good/bad/ugly kinda stuff. I know Meraki hardcores were upset when Cisco acquired them, but not exactly sure why. Anyway, any thoughts would be useful. Thanks! -Hank

22 31

telnet into a netgear switch?
by David Birdsong 25 Nov '13

25 Nov '13

Hey all, last night while at the datacenter I was in a pinch to extend a rack's LAN. I compromised and ran out to the local Fry's to buy whatever switch I could find so as to allow some configuration to happen while we wait for the real network gear to show up. I left before confirming I could access the switch remotely; it was very late and I was pretty groggy and hey, any network gear has to be telnet'table this day and age. Of course I was mostly wrong. The switch expects some signed payload before allowing a telnet through. I found this: https://code.google.com/p/netgear-telnetenable/...but I'm having a hell of a time getting anything to respond. The most confounding part is the switch doesn't respond to a single SYN packet on low ports. I'm scanning all the ports now, but if nothing shows up, I'm not sure what a payload is good for if the switch doesn't ACK a single SYN. I'm curious if anybody's got any tips besides not using Netgear in the datacenter. I have the MAC, I've IP'd it via DHCP, and the model number: JGS524E and I can power cycle the switch as much as needed. P.S. long time listener, first time caller. i'm more of a sysadmin dangerously standing in for a proper network person.

3 3

Re: AT&T UVERSE Native IPv6, a HOWTO
by Brzozowski, John 25 Nov '13

25 Nov '13

Andrew, Question is this native or 6rd? According to my ARIN WHOIS query it looks like 6rd. Definitely great news that you were able to acquire IPv6. John Date: Sat, 23 Nov 2013 01:22:02 -0500 From: Andrew D Kirch <trelane(a)trelane.net> To: nanog(a)nanog.org Subject: AT&T UVERSE Native IPv6, a HOWTO Message-ID: <5290498A.6040405(a)trelane.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Special thanks to Alexander from AT&T's "Tier-2" dept, though my suspicion is that that is not where he works, as he seems exceptionally clueful. Additional thanks to Owen DeLong who finally got me off my ass to actually do this, I'll see you in the sky! Ok, is this core routing? not really, but it's nice to see a major clue injection over at AT&T Uverse. I'm using this to document the MASSIVE bureaucratic PITA which is getting native IPv6 on uverse. You'll start from the default service on a 2wire "modem" (for values of modem that equate to profanity). If you have the Motorola NVG589, count yourself lucky and skip most of these steps. Abandon all hope ye who enter here.... Step 1: contact AT&T Uverse support and complain that you need IPv6 (because we all need it, I in fact do for work). Step 2: general confusion as the level 1 droid doesn't know what IPv6 is, politely request to be transferred to tier 2 step 3: you will be told that tier 2 is a paid service, invoke the almighty FCC and ask to speak with a supervisor, expect a long hold here. step 4: you arrive at tier 2, mention that IPv6 won't work on your 2wire and that AT&T has broken your protocol 41 tunnel with <insert tunnel broker here, usually HE> step 5: you'll need to get your 2wire replaced with a Motorola NVG589. Again you will be threatened with a cost to upgrade, mine was waived due to the work requirement. I'd guess some additional complaining and escalation will get this fee waived. My recollection was it was $100. The new modem is good news for quite a few reasons, the 2wire sucks, the Motorola sucks significantly less, and has a built in battery backup, but mine lacked the battery. step 6: you'll receive the motorola by mail, or have a tech install it, they actually had a tech in my area and I had an AT&T tech at my door in less than 20 minutes from when I got off the phone with tier-2 (I about died from the shock). step 7: configure the motorola (192.168.1.254) for passthrough, DHCPS-dynamic, disable the firewall, the "advanced" firewall, hpna, wireless, etc. Step 8: reboot to push the public IP to your real router. step 9: head over to the Motorola's home network tab, and in the status window you'll see: IPv6 Status Available Global IPv6 Address 2602:306:cddd:xxxx::1/64 Link-local IPv6 Address fe80::923e:abff:xxxx:7e40 Router Advertisement Prefix 2602:306:cddd:xxxx::/64 IPV6 Delegated LAN Prefix 2602:306:cddd:xxxx:: 2602:306:cddd:xxxx:: In reality additional poking leads me to believe AT&T gives you a rather generous /60, but how to use it? step 10: set up dhcpv6, example for mikrotik follows (but should be easily convertible to nearly any router): /ipv6> export # dec/31/2001 20:26:03 by RouterOS 6.6 # software id = 5F2Y-X73L # /ipv6 address add address=2602:306:cddd:xxxx::1 from-pool=AT&T interface=bridge1 /ipv6 dhcp-client add add-default-route=yes interface=ether10 pool-name=AT&T I hope that this is of help to someone. Andrew ========================================= John Jason Brzozowski Comcast Cable m) 609-377-6594 o) 484-962-0060 w) www.comcast6.net e) john_brzozowski(a)cable.comcast.com =========================================

1 0

Policy-based routing is evil? Discuss.
by William Waites 25 Nov '13

25 Nov '13

I'm having a discussion with a small network in a part of the world where bandwidth is scarce and multiple DSL lines are often used for upstream links. The topic is policy-based routing, which is being described as "load balancing" where end-user traffic is assigned to a line according to source address. In my opinion the main problems with this are: - It's brittle, when a line fails, traffic doesn't re-route - None of the usual debugging tools work properly - Adding a new user is complicated because it has to be done in (at least) two places But I'm having a distinct lack of success locating rants and diatribes or even well-reasoned articles supporting this opinion. Am I out to lunch? -w -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.

17 20

NAT64 and matching identities
by Justin M. Streiner 23 Nov '13

23 Nov '13

It's looking more and more like NAT64 will be in our future. One of the valid concerns for NAT64 - much like NAT44 - is being able to determine the identity of a given user through the NAT at a given point in time. How feasible this is depends on how robust/scalable $XYZ's translation logging capabilities are, and possibly how easily that data can be matched against a source of identify information, such as RADIUS accounting logs, DHCP lease logs, etc. Other IPv6 transition mechanisms appear to be no less thorny than NAT64 for a variety of reasons. I'm curious to see how others are planning to tackle (or already have tacked) this issue. Discussing vendor-specific solutions is fine, but I think keeping things as platform/vendor agnostic as possible for the time being would allow this thread to be more beneficial to a wider audience. The floor is open... jms

15 22