August 2014 - Test - lists.nanog.org

Weekly Routing Table Report
by Routing Analysis Role Account 29 Aug '14

29 Aug '14

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 04:00 +10GMT Sat 30 Aug, 2014 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 509487 Prefixes after maximum aggregation: 197642 Deaggregation factor: 2.58 Unique aggregates announced to Internet: 249829 Total ASes present in the Internet Routing Table: 47575 Prefixes per ASN: 10.71 Origin-only ASes present in the Internet Routing Table: 36092 Origin ASes announcing only one prefix: 16390 Transit ASes present in the Internet Routing Table: 6138 Transit-only ASes present in the Internet Routing Table: 181 Average AS path length visible in the Internet Routing Table: 4.6 Max AS path length visible: 53 Max AS path prepend of ASN ( 50404) 51 Prefixes from unregistered ASNs in the Routing Table: 1642 Unregistered ASNs in the Routing Table: 442 Number of 32-bit ASNs allocated by the RIRs: 7296 Number of 32-bit ASNs visible in the Routing Table: 5345 Prefixes from 32-bit ASNs in the Routing Table: 19533 Number of bogon 32-bit ASNs visible in the Routing Table: 619 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 347 Number of addresses announced to Internet: 2717084100 Equivalent to 161 /8s, 243 /16s and 105 /24s Percentage of available address space announced: 73.4 Percentage of allocated address space announced: 73.4 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 96.8 Total number of prefixes smaller than registry allocations: 175050 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 124591 Total APNIC prefixes after maximum aggregation: 36399 APNIC Deaggregation factor: 3.42 Prefixes being announced from the APNIC address blocks: 128175 Unique aggregates announced from the APNIC address blocks: 52441 APNIC Region origin ASes present in the Internet Routing Table: 4981 APNIC Prefixes per ASN: 25.73 APNIC Region origin ASes announcing only one prefix: 1226 APNIC Region transit ASes present in the Internet Routing Table: 865 Average APNIC Region AS path length visible: 4.8 Max APNIC Region AS path length visible: 24 Number of APNIC region 32-bit ASNs visible in the Routing Table: 1071 Number of APNIC addresses announced to Internet: 735509312 Equivalent to 43 /8s, 214 /16s and 251 /24s Percentage of available APNIC address space announced: 86.0 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: 169628 Total ARIN prefixes after maximum aggregation: 84831 ARIN Deaggregation factor: 2.00 Prefixes being announced from the ARIN address blocks: 171579 Unique aggregates announced from the ARIN address blocks: 80176 ARIN Region origin ASes present in the Internet Routing Table: 16344 ARIN Prefixes per ASN: 10.50 ARIN Region origin ASes announcing only one prefix: 6114 ARIN Region transit ASes present in the Internet Routing Table: 1690 Average ARIN Region AS path length visible: 4.0 Max ARIN Region AS path length visible: 22 Number of ARIN region 32-bit ASNs visible in the Routing Table: 177 Number of ARIN addresses announced to Internet: 1094318080 Equivalent to 65 /8s, 57 /16s and 248 /24s Percentage of available ARIN address space announced: 57.9 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: 125003 Total RIPE prefixes after maximum aggregation: 63089 RIPE Deaggregation factor: 1.98 Prefixes being announced from the RIPE address blocks: 129834 Unique aggregates announced from the RIPE address blocks: 82126 RIPE Region origin ASes present in the Internet Routing Table: 17709 RIPE Prefixes per ASN: 7.33 RIPE Region origin ASes announcing only one prefix: 8225 RIPE Region transit ASes present in the Internet Routing Table: 2887 Average RIPE Region AS path length visible: 5.0 Max RIPE Region AS path length visible: 53 Number of RIPE region 32-bit ASNs visible in the Routing Table: 2738 Number of RIPE addresses announced to Internet: 658843524 Equivalent to 39 /8s, 69 /16s and 39 /24s Percentage of available RIPE address space announced: 95.8 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-202239 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: 59604 Total LACNIC prefixes after maximum aggregation: 10545 LACNIC Deaggregation factor: 5.65 Prefixes being announced from the LACNIC address blocks: 67711 Unique aggregates announced from the LACNIC address blocks: 30158 LACNIC Region origin ASes present in the Internet Routing Table: 2256 LACNIC Prefixes per ASN: 30.01 LACNIC Region origin ASes announcing only one prefix: 608 LACNIC Region transit ASes present in the Internet Routing Table: 456 Average LACNIC Region AS path length visible: 4.6 Max LACNIC Region AS path length visible: 26 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 1306 Number of LACNIC addresses announced to Internet: 169664768 Equivalent to 10 /8s, 28 /16s and 225 /24s Percentage of available LACNIC address space announced: 101.1 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: 11032 Total AfriNIC prefixes after maximum aggregation: 2742 AfriNIC Deaggregation factor: 4.02 Prefixes being announced from the AfriNIC address blocks: 11841 Unique aggregates announced from the AfriNIC address blocks: 4626 AfriNIC Region origin ASes present in the Internet Routing Table: 735 AfriNIC Prefixes per ASN: 16.11 AfriNIC Region origin ASes announcing only one prefix: 217 AfriNIC Region transit ASes present in the Internet Routing Table: 157 Average AfriNIC Region AS path length visible: 4.8 Max AfriNIC Region AS path length visible: 25 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 53 Number of AfriNIC addresses announced to Internet: 58322688 Equivalent to 3 /8s, 121 /16s and 239 /24s Percentage of available AfriNIC address space announced: 57.9 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 2934 11591 919 Korea Telecom 17974 2808 900 74 PT Telekomunikasi Indonesia 7545 2333 336 120 TPG Telecom Limited 4755 1893 413 192 TATA Communications formerly 9829 1654 1307 32 National Internet Backbone 9583 1316 104 538 Sify Limited 9498 1301 317 92 BHARTI Airtel Ltd. 7552 1238 1098 14 Viettel Corporation 9808 1236 6639 15 Guangdong Mobile Communicatio 4808 1202 2158 369 CNCGROUP IP network China169 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 2928 2940 142 Cox Communications Inc. 6389 2896 3688 51 BellSouth.net Inc. 18566 2045 379 178 MegaPath Corporation 7029 1916 1957 305 Windstream Communications Inc 20115 1772 1756 524 Charter Communications 4323 1623 1055 407 tw telecom holdings, inc. 30036 1555 326 535 Mediacom Communications Corp 6983 1444 817 314 ITC^Deltacom 701 1437 11242 721 MCI Communications Services, 22561 1308 408 237 CenturyTel Internet Holdings, 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 34984 1743 298 281 TELLCOM ILETISIM HIZMETLERI A 20940 1474 570 1084 Akamai International B.V. 8402 1319 544 15 OJSC "Vimpelcom" 31148 1042 45 20 Freenet Ltd. 13188 1041 97 49 TOV "Bank-Inform" 8551 980 371 41 Bezeq International-Ltd 6849 807 356 27 JSC "Ukrtelecom" 12479 784 798 58 France Telecom Espana SA 6830 773 2335 428 Liberty Global Operations B.V 9198 648 346 28 JSC Kazakhtelecom 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 3357 2315 117 NET Serviços de Comunicação S 10620 2961 480 215 Telmex Colombia S.A. 18881 2084 1036 22 Global Village Telecom 7303 1768 1180 234 Telecom Argentina S.A. 6147 1739 374 30 Telefonica del Peru S.A.A. 8151 1467 2999 433 Uninet S.A. de C.V. 6503 1095 434 61 Axtel, S.A.B. de C.V. 7738 977 1882 41 Telemar Norte Leste S.A. 27947 902 130 51 Telconet S.A 26615 897 2325 35 Tim Celular 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 24863 941 280 26 Link Egypt (Link.NET) 6713 669 744 37 Office National des Postes et 8452 599 958 13 TE-AS 36992 315 816 27 ETISALAT MISR 24835 307 144 9 Vodafone Data 3741 249 920 212 Internet Solutions 29571 237 22 17 Cote d'Ivoire Telecom 37054 236 19 6 Data Telecom Service 15706 186 17 6 Sudatel (Sudan Telecom Co. Lt 12258 174 26 71 MWEB CONNECT (PROPRIETARY) LI 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 3357 2315 117 NET Serviços de Comunicação S 10620 2961 480 215 Telmex Colombia S.A. 4766 2934 11591 919 Korea Telecom 22773 2928 2940 142 Cox Communications Inc. 6389 2896 3688 51 BellSouth.net Inc. 17974 2808 900 74 PT Telekomunikasi Indonesia 7545 2333 336 120 TPG Telecom Limited 18881 2084 1036 22 Global Village Telecom 18566 2045 379 178 MegaPath Corporation 7029 1916 1957 305 Windstream Communications Inc 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 2896 2845 BellSouth.net Inc. 22773 2928 2786 Cox Communications Inc. 10620 2961 2746 Telmex Colombia S.A. 17974 2808 2734 PT Telekomunikasi Indonesia 7545 2333 2213 TPG Telecom Limited 18881 2084 2062 Global Village Telecom 4766 2934 2015 Korea Telecom 18566 2045 1867 MegaPath Corporation 6147 1739 1709 Telefonica del Peru S.A.A. 4755 1893 1701 TATA Communications formerly Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 30662 UNALLOCATED 8.2.129.0/24 3356 Level 3 Communicatio 53506 UNALLOCATED 8.17.102.0/23 2828 XO Communications 20260 UNALLOCATED 8.25.160.0/24 3356 Level 3 Communicatio 20260 UNALLOCATED 8.25.161.0/24 3356 Level 3 Communicatio 46473 UNALLOCATED 8.27.122.0/24 12180 Internap Network Ser 46473 UNALLOCATED 8.27.124.0/24 12180 Internap Network Ser 55020 UNALLOCATED 8.30.123.0/24 3356 Level 3 Communicatio 27205 UNALLOCATED 8.38.16.0/21 6461 Abovenet Communicati 15347 UNALLOCATED 8.224.147.0/24 12064 Cox Communications I 33628 UNALLOCATED 12.0.239.0/24 1239 Sprint 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.65.0.0/24 4826 Vocus Connect International B Complete listing at http://thyme.rand.apnic.net/current/data-dsua Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 5.100.241.0/24 23456 32bit Transition AS 24.231.96.0/24 21548 MTO Telecom Inc. 27.100.7.0/24 56096 >>UNKNOWN<< 41.73.1.0/24 37004 >>UNKNOWN<< 41.73.2.0/24 37004 >>UNKNOWN<< 41.73.10.0/24 37004 >>UNKNOWN<< 41.73.11.0/24 37004 >>UNKNOWN<< 41.73.12.0/24 37004 >>UNKNOWN<< 41.73.13.0/24 37004 >>UNKNOWN<< 41.73.14.0/24 37004 >>UNKNOWN<< 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:13 /10:30 /11:91 /12:261 /13:500 /14:982 /15:1705 /16:13031 /17:7045 /18:11746 /19:24647 /20:35359 /21:37764 /22:54294 /23:47822 /24:271327 /25:1091 /26:1039 /27:665 /28:15 /29:19 /30:10 /31:1 /32:14 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 22773 2164 2928 Cox Communications Inc. 18566 2000 2045 MegaPath Corporation 6389 1674 2896 BellSouth.net Inc. 30036 1404 1555 Mediacom Communications Corp 6147 1314 1739 Telefonica del Peru S.A.A. 7029 1158 1916 Windstream Communications Inc 6983 1150 1444 ITC^Deltacom 11492 1124 1173 CABLE ONE, INC. 34984 1064 1743 TELLCOM ILETISIM HIZMETLERI A 10620 1036 2961 Telmex Colombia S.A. Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1328 2:663 3:3 4:16 5:1081 6:21 8:732 12:1862 13:4 14:1110 15:15 16:2 17:39 18:21 20:50 23:904 24:1799 27:1777 31:1408 32:41 33:2 34:5 36:139 37:1846 38:967 39:12 40:220 41:2535 42:270 43:228 44:16 45:63 46:2144 47:24 49:733 50:820 52:12 54:49 55:5 56:4 57:32 58:1217 59:660 60:425 61:1688 62:1235 63:1836 64:4362 65:2292 66:4200 67:2030 68:1042 69:3252 70:864 71:478 72:2046 74:2575 75:370 76:420 77:1612 78:798 79:715 80:1324 81:1201 82:764 83:780 84:766 85:1324 86:441 87:1149 88:461 89:1793 90:138 91:5692 92:766 93:1782 94:2022 95:1591 96:421 97:344 98:1159 99:49 100:67 101:706 103:5469 104:207 105:37 106:179 107:602 108:566 109:1975 110:1027 111:1354 112:718 113:852 114:780 115:1186 116:1104 117:988 118:1546 119:1425 120:419 121:970 122:2167 123:1606 124:1427 125:1571 128:600 129:348 130:366 131:718 132:423 133:165 134:319 135:75 136:303 137:288 138:384 139:203 140:228 141:401 142:575 143:426 144:505 145:112 146:607 147:489 148:975 149:402 150:452 151:595 152:458 153:241 154:338 155:526 156:358 157:328 158:280 159:939 160:328 161:587 162:1729 163:340 164:702 165:645 166:361 167:673 168:1124 169:122 170:1394 171:183 172:63 173:1603 174:700 175:624 176:1475 177:3530 178:2090 179:774 180:1775 181:1596 182:1629 183:555 184:708 185:2008 186:2927 187:1669 188:2168 189:1473 190:7959 191:757 192:7503 193:5501 194:4049 195:3572 196:1442 197:682 198:5146 199:5469 200:6496 201:2868 202:9178 203:9011 204:4561 205:2643 206:2949 207:2910 208:3931 209:3733 210:3303 211:1836 212:2338 213:2126 214:865 215:88 216:5565 217:1688 218:617 219:406 220:1355 221:688 222:479 223:597 End of report

1 0

GoDaddy Contact
by D'Alleva, Ron 29 Aug '14

29 Aug '14

Greetings, Can someone from GoDaddy please contact me off list? Two of our name servers have been block from making DNS lookups against your hosted domains. Many Thanks, -- Ronald D'Alleva Email: rdalleva(a)constantcontact.com<mailto:rdalleva@constantcontact.com>

1 0

Re: Prefix hijacking, how to prevent and fix currently
by Brandon Butterworth 29 Aug '14

29 Aug '14

> From: Saku Ytti <saku(a)ytti.fi> > I feel RPKI would be much more marketable if vendors would implement 'loose' > mode. > Loose mode would drop failing routes, iff there is covering (i.e. less > specific is ok) route already in RIB. +10 > And it would completely remove false-positive blackholing. This is why I don't want strict. That and true-positives, I don't think having a switch that allows courts/rir finger trouble etc to take out global routing is sensible. Too many others would start using it. However loose mode could be abused in the same way, they just invalidate your key and advertise a covering route to give themselves effective strict over you. Admittedly there is collateral damage to adjacent address space incurred in doing this but we know there are hijack techniques they could use to mitigate that brandon

1 0

JANOG 34 Meeting Report
by MAWATARI Masataka 29 Aug '14

29 Aug '14

Dear Colleagues, We'd like to share some of the discussions from JANOG 34 held in Takamatsu-city, from 17-18 July with over 500 participants. While our discussions are in Japanese, we believe there are issues in common with operators outside Japan. An english version of the Summary Report and a report on anti-spam measures session is be made available this time, below. JANOG 34 Summary Report and "Let's talk about IP anycast" : http://goo.gl/IbKzkQ Pick up Session: "Measures against Spam after OP25B" : http://goo.gl/uY4lxk The topics discussed are not limited to these two topics of course. Please see the translated overview of the program and the presentation slides (in Japanese but some have visual images and data). Program Overview (English): http://goo.gl/KhrpRZ Program and Slides (Japanese): http://goo.gl/Q61oeh Here are some examples of the topics covered: * Use of technologies - Visualising network events - Advantages and disadvantages of "white box networking" * Operational issues - Blind spots of IPv6 PMTU Blackhole Discovery - NTP attacks: "NTP Talk WG": http://goo.gl/5RL50v - OpenSSL heartbleed bug - Stopping full table routing changed my life @ AS55394 * Social aspects - Seeking change in the cost structure of content delivery - Balance of outreach on security issues - What is good higher education for future engineers - Cultural differences in software and network engineers At the meeting, we ran the JANOG 34 network with IPv6 ULA-only and ULA + GUA SSIDs, which was presented at the IPv6 Operations session @ IETF90 in Toronto. ULA Experience at JANOG 34 http://tools.ietf.org/agenda/90/slides/slides-90-v6ops-1.pdf Positive findings - GUA + IPv4 (Private) and ULA is harmless (at least for MAC OS) - SLAAC/ULA and DHCPv6/ULA works well - ULA operation/configuration is not hard Challenges - Android devices did not come up without IPv4 - IPv4 only applications still exist (Skype/dropbox) - NAT66 on ULA only network should not be recommended , but it worked If you have any feedback, we welcome comments or questions on JANOG mailing list "janog(a)janog.gr.jp": https://www.janog.gr.jp/mailman/listinfo/janog/ * Subscription page first appears in Japanese but it's possible to switch to English from pull-down menu options on the top right The coming meeting, JANOG 35 will be from 14-16 Jan 2015 in Shizuoka Prefecture. We'll update you with more details through our SNS accounts as the date gets closer. Masataka Mawatari, Izumi Okutani JANOG Internationalization(i18n) team http://www.janog.gr.jp/en/index.php?i18n-team Facebook: https://www.facebook.com/janogmeetingi18n Twitter : https://twitter.com/janog_i18n ------------------------------------------------------------------- -- Japan Internet Exchange MAWATARI Masataka <mawatari(a)jpix.ad.jp>

1 0

Broken IPv6 firmware on U-Verse 3801HGV
by Ivan Kozik 28 Aug '14

28 Aug '14

I noticed that AT&T released some firmware with IPv6 support back in May for their 3801HGV (and related) gateways. To try this out, I factory-reset my 3801HGV (still on version 6.9) and it installed the 6.11 firmware about 10 minutes later. I then used the obscure page at https://esupport.att3.2wire.com/online-tool/compat-index.jsp to request an IPv6 address ("wait 48 hours" it said) and got a routable IPv6 address in just a few minutes. All for naught, though. With IPv6 enabled, the 3801HGV crashed and rebooted about once an hour. After unchecking "IPv6 LAN Enabled" in http://192.168.1.254/xslt?PAGE=C_2_6 everything went back to normal. If anyone from AT&T is listening, I'm happy to help diagnose your firmware problems. Ivan

3 2

Verizon connectivity issues
by Ryan Ruuska 28 Aug '14

28 Aug '14

Hello all, We have heard from many of our customers in the Northeast region, specifically PA, MD, and VA who have difficulty connecting to our website (very slow loading times). We have noticed that if our data center provider specifically routes our outbound traffic over Hurricane Electric rather than XO Communications, that connectivity is restored to normal for our customers. The HE path goes from Salt Lake City to Denver where it is handed off to TeliaSonera, and they send it to Chicago where it gets handed off to Verizon. This works great and generally has a ping response of 20-25ms less than the bad route as posted below from one of our servers: Tracing route to pool-108-52-xxx-xxx.phlapa.fios.verizon.net [108.52.xxx.xxx] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 172.xxx.xxx.xxx (Internal IP) 2 <1 ms 10 ms <1 ms 209-41-xxx-xxx.c7dc.com [209.41.xxx.xxx] 3 <1 ms <1 ms <1 ms e1-5.rt08.gp1.c7dc.com [192.41.0.97] 4 2 ms 1 ms 1 ms ip65-46-51-113.z51-46-65.customer.algx.net [65.46.51.113] 5 19 ms 18 ms 19 ms vb1611.rar3.sanjose-ca.us.xo.net [216.156.0.5] 6 21 ms 18 ms 18 ms 207.88.14.226.ptr.us.xo.net [207.88.14.226] 7 18 ms 18 ms 18 ms 206.111.6.122.ptr.us.xo.net [206.111.6.122] >>>> Verizon owned device with an XO IP address 8 87 ms 86 ms 87 ms b100.phlapa-lcr-22.verizon-gni.net [130.81.209.187] >>>> Next hop goes from CA to PA, probably just hidden routing info 9 * * * Request timed out. 10 88 ms 89 ms 90 ms pool-108-52-xxx-xxx.phlapa.fios.verizon.net [108.52.xxx.xxx] As you can see, XO sends this traffic from Salt Lake City to San Jose where it is handed off to Verizon. We've worked with XO and determined that there are no connectivity issues along their path, which seems to point to an issue within Verizon's network. I have a couple of tickets open with Verizon at the moment on behalf of some of our customers, but we have had trouble breaking through Tier 1. Our first thought was saturation of the peering point, but XO states that the link between hops 6 and 7 is using 5Gbps out of 20Gbps capacity, and the latency on hop 7 (the Verizon owned device with an XO IP) seems normal whenever we test. Any Verizon engineers out there willing to take a quick peek at this route for any obvious issues? It would be a lot easier for us if Verizon provided Looking Glass servers, but alas... Thank you, Ryan

3 3

Request for Verizon Engineer regarding 206.111.6.122 (San Jose)
by Ryan Ruuska 27 Aug '14

27 Aug '14

Can someone contact me regarding an issue with connectivity from this hop in San Jose to customers in Maryland, Virginia, and Pennsylvania? The DNS says it is an XO IP but it is actually a Verizon owned device. Thank you, Ryan

1 0

Ebay/Paypal blocking HTTP access based on SORBS DUHL / Spamhaus PBL
by Tarko Tikan 27 Aug '14

27 Aug '14

hey, For a while now, we have been getting complains from our broadband customers about not being able to reach ebay.com/paypal.com We have nailed it down to some small prefixes and they are all listed in SORBS DUHL / Spamhaus PBL and have been listed for ages. These are indeed dynamic IP pools and should not send any email (not that SMTP has anything to do with HTTP). For some reason, it looks like ebay/paypal is now blocking HTTP access based on these blacklists. Does anyone have working contact in their NOC or with security people? All emails to public contacts have not been answered to. -- tarko

4 6

centurylink chi2 and level3 -- network issues
by Nick 27 Aug '14

27 Aug '14

Is anyone else having network issue over the past week with centurylink and their peer level3? I spoke with centurylinks noc team. They are not being helpful and blame level3. I'm seeing period of high packet loss and poor throughput speeds. From what I can tell. Its a problem between qwest and level3 border routers. Host Loss% Snt Last Avg Best Wrst StDev .... 2. cer-core-02.inet.qwest.net 0.0% 663 0.5 0.8 0.4 35.0 2.9 3. vlan52.ebr2.Chicago2.Level3.net 2.7% 662 196.0 196.5 192.2 209.2 1.5 4. ??? 5. ae-46-46.ebr2.Washington1.Level3 1.8% 662 196.8 196.0 191.2 201.1 1.1 .... [not the complete traceroute] At the moment, I moved most of my traffic from centurylink. The remaining services are being greatly impacted by the poor network performance. What do you think my next steps should be? Any advice would be greatly appreciated. - Nick

2 1

RPKI
by Pelsser Cristel 27 Aug '14

27 Aug '14

Hi, With Daniele Iamartino, we are validating BGP routes with the objects stored in the RPKI. On 2014/07/26, for the routes at the LINX RouteViews monitor, we observe the following set of prefixes that are announced both with the correct origin AS and a wrong origin AS. There are very few of them. We believe they could be anycast where there is no ROA for some origin ASs or they could be misconfiguration/attacks. RIB Dump time: 2014/08/26 08:00 UTC prefix,valid AS,invalid AS 5.128.0.0/14,31200,50923 37.19.8.0/21,49964,198585 94.199.232.0/21,49413,5089 179.61.194.0/23,61440,37692 190.94.182.0/24,262195,18678 193.42.215.0/24,30880,50827 193.227.174.0/24,9051,24634 195.69.144.0/22,1200,41313 200.35.183.0/24,26617,27742 213.192.242.0/23,8903,12541 217.113.242.0/24,197860,20721 217.113.244.0/24,197860,20721 217.113.245.0/24,20721,197860 2a02:2928::/32,39288,197530 Prefixes containing private AS numbers prefix,valid AS,invalid AS 176.56.192.0/19,8426,65489 185.36.76.0/22,8426,65489 194.45.46.0/24,286,64951 2a00:fd00::/32,29695,65026 Any feedback is welcome, Cristel

1 0