December 2011 - Test - lists.nanog.org

Re: IP addresses are now assets
by Scott Weeks 02 Dec '11

02 Dec '11

--- jsahala(a)gmail.com wrote: the speculative market exists and is growing, why do certain factions of the community keep trying to pretend that it doesn't? ------------------------------------------- Because they're busy getting ipv6 up and that will make these things less important? >;-) scott

1 0

Weekly Routing Table Report
by Routing Analysis Role Account 02 Dec '11

02 Dec '11

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, 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 03 Dec, 2011 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 383257 Prefixes after maximum aggregation: 167342 Deaggregation factor: 2.29 Unique aggregates announced to Internet: 188231 Total ASes present in the Internet Routing Table: 39463 Prefixes per ASN: 9.71 Origin-only ASes present in the Internet Routing Table: 32445 Origin ASes announcing only one prefix: 15489 Transit ASes present in the Internet Routing Table: 5326 Transit-only ASes present in the Internet Routing Table: 142 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 33 Max AS path prepend of ASN (48687) 24 Prefixes from unregistered ASNs in the Routing Table: 1825 Unregistered ASNs in the Routing Table: 938 Number of 32-bit ASNs allocated by the RIRs: 2031 Number of 32-bit ASNs visible in the Routing Table: 1692 Prefixes from 32-bit ASNs in the Routing Table: 4000 Special use prefixes present in the Routing Table: 2 Prefixes being announced from unallocated address space: 86 Number of addresses announced to Internet: 2497290368 Equivalent to 148 /8s, 217 /16s and 160 /24s Percentage of available address space announced: 67.4 Percentage of allocated address space announced: 67.4 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 91.7 Total number of prefixes smaller than registry allocations: 161883 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 95145 Total APNIC prefixes after maximum aggregation: 31175 APNIC Deaggregation factor: 3.05 Prefixes being announced from the APNIC address blocks: 91627 Unique aggregates announced from the APNIC address blocks: 38267 APNIC Region origin ASes present in the Internet Routing Table: 4600 APNIC Prefixes per ASN: 19.92 APNIC Region origin ASes announcing only one prefix: 1249 APNIC Region transit ASes present in the Internet Routing Table: 727 Average APNIC Region AS path length visible: 4.4 Max APNIC Region AS path length visible: 18 Number of APNIC region 32-bit ASNs visible in the Routing Table: 116 Number of APNIC addresses announced to Internet: 631205216 Equivalent to 37 /8s, 159 /16s and 109 /24s Percentage of available APNIC address space announced: 80.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, 131072-132095, 132096-133119 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, 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: 146116 Total ARIN prefixes after maximum aggregation: 74691 ARIN Deaggregation factor: 1.96 Prefixes being announced from the ARIN address blocks: 118285 Unique aggregates announced from the ARIN address blocks: 48671 ARIN Region origin ASes present in the Internet Routing Table: 14775 ARIN Prefixes per ASN: 8.01 ARIN Region origin ASes announcing only one prefix: 5644 ARIN Region transit ASes present in the Internet Routing Table: 1574 Average ARIN Region AS path length visible: 4.0 Max ARIN Region AS path length visible: 25 Number of ARIN region 32-bit ASNs visible in the Routing Table: 12 Number of ARIN addresses announced to Internet: 803370432 Equivalent to 47 /8s, 226 /16s and 117 /24s Percentage of available ARIN address space announced: 63.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, 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, 173/8, 174/8, 184/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: 92913 Total RIPE prefixes after maximum aggregation: 51424 RIPE Deaggregation factor: 1.81 Prefixes being announced from the RIPE address blocks: 85148 Unique aggregates announced from the RIPE address blocks: 54728 RIPE Region origin ASes present in the Internet Routing Table: 16155 RIPE Prefixes per ASN: 5.27 RIPE Region origin ASes announcing only one prefix: 7997 RIPE Region transit ASes present in the Internet Routing Table: 2543 Average RIPE Region AS path length visible: 4.7 Max RIPE Region AS path length visible: 33 Number of RIPE region 32-bit ASNs visible in the Routing Table: 1186 Number of RIPE addresses announced to Internet: 492772928 Equivalent to 29 /8s, 95 /16s and 30 /24s Percentage of available RIPE address space announced: 79.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 196608-198655 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, 176/8, 178/8, 185/8, 193/8, 194/8, 195/8, 212/8, 213/8, 217/8, LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 36582 Total LACNIC prefixes after maximum aggregation: 7943 LACNIC Deaggregation factor: 4.61 Prefixes being announced from the LACNIC address blocks: 36006 Unique aggregates announced from the LACNIC address blocks: 18774 LACNIC Region origin ASes present in the Internet Routing Table: 1554 LACNIC Prefixes per ASN: 23.17 LACNIC Region origin ASes announcing only one prefix: 442 LACNIC Region transit ASes present in the Internet Routing Table: 286 Average LACNIC Region AS path length visible: 4.5 Max LACNIC Region AS path length visible: 18 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 374 Number of LACNIC addresses announced to Internet: 94397312 Equivalent to 5 /8s, 160 /16s and 99 /24s Percentage of available LACNIC address space announced: 62.5 LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 262144-263167 plus ERX transfers LACNIC Address Blocks 177/8, 179/8, 181/8, 186/8, 187/8, 189/8, 190/8, 200/8, 201/8, AfriNIC Region Analysis Summary ------------------------------- Prefixes being announced by AfriNIC Region ASes: 8338 Total AfriNIC prefixes after maximum aggregation: 2041 AfriNIC Deaggregation factor: 4.09 Prefixes being announced from the AfriNIC address blocks: 6390 Unique aggregates announced from the AfriNIC address blocks: 2012 AfriNIC Region origin ASes present in the Internet Routing Table: 504 AfriNIC Prefixes per ASN: 12.68 AfriNIC Region origin ASes announcing only one prefix: 157 AfriNIC Region transit ASes present in the Internet Routing Table: 110 Average AfriNIC Region AS path length visible: 4.5 Max AfriNIC Region AS path length visible: 25 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 4 Number of AfriNIC addresses announced to Internet: 30034432 Equivalent to 1 /8s, 202 /16s and 74 /24s Percentage of available AfriNIC address space announced: 44.8 AfriNIC AS Blocks 36864-37887, 327680-328703 & ERX transfers AfriNIC Address Blocks 41/8, 102/8, 105/8, 197/8, APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 4766 2510 11105 973 Korea Telecom (KIX) 17974 1652 503 38 PT TELEKOMUNIKASI INDONESIA 7545 1626 303 87 TPG Internet Pty Ltd 4755 1511 381 157 TATA Communications formerly 7552 1386 1064 7 Vietel Corporation 9829 1166 989 28 BSNL National Internet Backbo 9583 1095 80 494 Sify Limited 4808 1079 2038 305 CNCGROUP IP network: China169 24560 985 390 151 Bharti Airtel Ltd., Telemedia 18101 958 121 155 Reliance Infocom Ltd Internet 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 3483 3814 218 bellsouth.net, inc. 7029 2912 1016 199 Windstream Communications Inc 18566 2093 383 177 Covad Communications 1785 1852 680 120 PaeTec Communications, Inc. 4323 1616 1073 386 Time Warner Telecom 20115 1603 1546 625 Charter Communications 22773 1507 2909 104 Cox Communications, Inc. 30036 1435 257 675 Mediacom Communications Corp 19262 1388 4683 401 Verizon Global Networks 7018 1314 7029 860 AT&T WorldNet Services 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 1552 480 15 Corbina telecom 6830 645 1927 412 UPC Distribution Services 34984 616 116 195 BILISIM TELEKOM 20940 546 174 437 Akamai Technologies European 3320 517 8168 390 Deutsche Telekom AG 12479 494 601 13 Uni2 Autonomous System 3292 480 2106 407 TDC Tele Danmark 8866 462 133 26 Bulgarian Telecommunication C 8551 451 366 45 Bezeq International 31148 413 22 115 FreeNet ISP 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 1702 315 180 TVCABLE BOGOTA 28573 1537 1059 72 NET Servicos de Comunicao S.A 8151 1334 2985 345 UniNet S.A. de C.V. 7303 1239 751 174 Telecom Argentina Stet-France 27947 606 72 89 Telconet S.A 22047 582 322 17 VTR PUNTO NET S.A. 7738 553 1050 31 Telecomunicacoes da Bahia S.A 6503 552 434 68 AVANTEL, S.A. 3816 547 237 89 Empresa Nacional de Telecomun 11172 527 85 95 Servicios Alestra S.A de C.V 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 8452 926 958 13 TEDATA 24863 785 146 35 LINKdotNET AS number 3741 281 939 230 The Internet Solution 15706 242 32 6 Sudatel Internet Exchange Aut 6713 235 519 14 Itissalat Al-MAGHRIB 33776 231 13 10 Starcomms Nigeria Limited 29571 217 17 13 Ci Telecom Autonomous system 12258 195 28 60 Vodacom Internet Company 24835 190 80 8 RAYA Telecom - Egypt 16637 160 662 82 MTN Network Solutions 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 6389 3483 3814 218 bellsouth.net, inc. 7029 2912 1016 199 Windstream Communications Inc 4766 2510 11105 973 Korea Telecom (KIX) 18566 2093 383 177 Covad Communications 1785 1852 680 120 PaeTec Communications, Inc. 10620 1702 315 180 TVCABLE BOGOTA 17974 1652 503 38 PT TELEKOMUNIKASI INDONESIA 7545 1626 303 87 TPG Internet Pty Ltd 4323 1616 1073 386 Time Warner Telecom 20115 1603 1546 625 Charter Communications Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 7029 2912 2713 Windstream Communications Inc 18566 2093 1916 Covad Communications 1785 1852 1732 PaeTec Communications, Inc. 17974 1652 1614 PT TELEKOMUNIKASI INDONESIA 7545 1626 1539 TPG Internet Pty Ltd 4766 2510 1537 Korea Telecom (KIX) 8402 1552 1537 Corbina telecom 10620 1702 1522 TVCABLE BOGOTA 28573 1537 1465 NET Servicos de Comunicao S.A 22773 1507 1403 Cox Communications, Inc. Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 15132 UNALLOCATED 12.9.150.0/24 7018 AT&T WorldNet Servic 32567 UNALLOCATED 12.14.170.0/24 4323 Time Warner Telecom 32567 UNALLOCATED 12.25.107.0/24 4323 Time Warner Telecom 25639 UNALLOCATED 12.41.169.0/24 7018 AT&T WorldNet Servic 13317 UNALLOCATED 12.44.10.0/24 7018 AT&T WorldNet Servic 23502 UNALLOCATED 12.44.44.0/24 7018 AT&T WorldNet Servic 17300 UNALLOCATED 12.45.103.0/24 7018 AT&T WorldNet Servic 17300 UNALLOCATED 12.45.110.0/24 701 UUNET Technologies, 16476 UNALLOCATED 12.46.27.0/24 7018 AT&T WorldNet Servic 14764 UNALLOCATED 12.108.237.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 128.0.0.0/21 12654 RIPE NCC RIS Project 128.0.24.0/24 12654 RIPE NCC RIS Project Complete listing at http://thyme.rand.apnic.net/current/data-dsua Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 41.222.79.0/24 37345 MEDALLION Communications 41.223.92.0/22 36936 >>UNKNOWN<< 62.61.220.0/24 24974 Tachyon Europe BV - Wireless 62.61.221.0/24 24974 Tachyon Europe BV - Wireless 64.21.192.0/20 11610 Internet Nebraska Corporation 64.21.212.0/22 11610 Internet Nebraska Corporation 64.21.216.0/21 11610 Internet Nebraska Corporation 66.171.32.0/20 705 UUNET Technologies, Inc. 66.175.222.0/23 30058 FDC Servers.net, LLC 66.180.239.0/24 35888 VIGNETTE CORPORATION 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:19 /9:12 /10:27 /11:81 /12:236 /13:463 /14:807 /15:1437 /16:12055 /17:6113 /18:10143 /19:20053 /20:27738 /21:28008 /22:38142 /23:35692 /24:198843 /25:1181 /26:1400 /27:785 /28:14 /29:3 /30:0 /31:0 /32:5 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 7029 2541 2912 Windstream Communications Inc 6389 2126 3483 bellsouth.net, inc. 18566 2042 2093 Covad Communications 10620 1597 1702 TVCABLE BOGOTA 8402 1527 1552 Corbina telecom 30036 1395 1435 Mediacom Communications Corp 11492 1119 1156 Cable One 1785 1058 1852 PaeTec Communications, Inc. 7011 1048 1165 Citizens Utilities 22773 967 1507 Cox Communications, Inc. Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:442 2:489 4:15 5:1 6:3 8:359 12:1947 13:1 14:548 15:11 16:3 17:7 20:9 23:69 24:1694 27:1059 31:717 32:67 33:2 34:2 36:4 38:770 39:1 40:114 41:2860 42:66 43:1 44:3 46:1111 47:3 49:292 50:450 52:13 55:6 56:2 57:49 58:939 59:486 60:358 61:1178 62:913 63:1968 64:4049 65:2308 66:4368 67:1998 68:1174 69:3147 70:904 71:361 72:1772 74:2641 75:430 76:320 77:907 78:890 79:438 80:1142 81:834 82:523 83:527 84:471 85:1164 86:410 87:907 88:341 89:1587 90:246 91:4314 92:532 93:1423 94:1327 95:1096 96:397 97:285 98:764 99:37 101:121 103:523 106:7 107:103 108:88 109:1120 110:668 111:818 112:367 113:487 114:622 115:700 116:896 117:708 118:870 119:1229 120:349 121:667 122:1567 123:1019 124:1348 125:1349 128:278 129:185 130:183 131:632 132:155 133:21 134:222 135:54 136:212 137:146 138:287 139:123 140:491 141:253 142:379 143:405 144:498 145:62 146:475 147:221 148:643 149:270 150:166 151:192 152:449 153:171 154:7 155:381 156:209 157:359 158:156 159:523 160:333 161:214 162:364 163:176 164:521 165:385 166:542 167:453 168:823 169:146 170:822 171:87 172:4 173:1767 174:586 175:418 176:329 177:411 178:1150 180:1178 181:39 182:669 183:242 184:399 185:1 186:1478 187:784 188:947 189:1164 190:5286 192:5965 193:5118 194:3555 195:3119 196:1283 197:169 198:3624 199:4235 200:5523 201:1696 202:8474 203:8494 204:4322 205:2409 206:2668 207:2839 208:4011 209:3551 210:2730 211:1473 212:1991 213:1804 214:813 215:92 216:4933 217:1486 218:577 219:340 220:1252 221:525 222:325 223:229 End of report

1 0

Recent DNS attacks from China?
by Leland Vandervort 02 Dec '11

02 Dec '11

Hi All, I am wondering if anyone else is seeing a sudden increase in DNS attacks emanating from chinese IP addresses? Over the past 24 hours we've seen a sudden rash of chinese IPs attacking our DNS servers in the order of 5 to 10 million PPS for periods of 5 to 10 mins, repeated every 20 to 30 minutes. This anomalous traffic started roughly 24 hours ago, and while we've had occasions of anomalous chinese traffic, never anything of this type. Anyone else? Regards, Leland

11 13

IPv6 prefixes longer then /64: are they possible in DOCSIS networks?
by Dmitry Cherkasov 02 Dec '11

02 Dec '11

Hello everybody, It is commonly agreed that /64 is maximal length for LANs because if we use longer prefix we introduce conflict with stateless address autoconfiguration (SLAAC) based on EUI-64 spec. But SLAAC is not used in DOCSIS networks. So there seems to be no objections to use smaller networks per cable interfaces of CMTS. I was not able to find any recommendations anywhere including Cable Labs specs for using prefixes not greater then /64 in DOCSIS networks. Some tech from ISP assumed that DHCPv6 server may generate interface ID part of IPv6 address similarly to EUI-64 so MAC address of the device can easily be obtained from its IPv6 address, but this does not seem like convincing argument. What do you think? Dmitry Cherkasov

24 69

APRICOT-2012: Call for Papers
by Mark Tinka 02 Dec '11

02 Dec '11

Asia Pacific Regional Internet Conference on Operational Technologies (APRICOT) 21 February - 2 March 2012, New Delhi, India http://www.apricot2012.net CALL FOR PAPERS =============== The APRICOT 2012 Programme Committee is now seeking contributions for Presentations and Tutorials for APRICOT 2012. We are looking for people and proposals that would: - Offer a technical tutorial on an appropriate topic; and/or - Participate in the technical conference sessions as a speaker; and/or - Convene and chair a Birds of a Feather (BOF) session. Please submit proposals on-line at: http://submission.apnic.net/ CONFERENCE MILESTONES --------------------- Call for Papers Opens: 22 November 2011 First Draft Program Published: 19 December 2011 Final Deadline for Submissions: 10 February 2012 Final Program Published: 17 February 2012 Final Slides Received: 25 February 2012 PROGRAM MATERIAL ---------------- The APRICOT Programme is organised in three parts, including workshops, tutorials and the conference. The APNIC Policy SIG and Annual Members Meeting will be held during the APRICOT conference. Topics for tutorials and conference would include amongst others relevant to Internet Operations and Technologies: - IPv4 / IPv6 Routing and operations - IPv4 address runout / IPv6 deployment and transition technologies - Backbone operations - ISP and Carrier services - Network security issues (NSP-SEC, DDoS Anti-Spam, Anti-Malware) - Peering / IXPs - DNS / DNSSEC - Internet policy (Security, Regulation, Content Management, Addressing, etc) - Access and Transport Technologies, including broadband deployment, Cable/DSL, wireless, WiMax, metro ethernet, fiber network, MPLS - Content & Service Delivery (Multicast, Voice, Video, "telepresence", Gaming) CfP SUBMISSION -------------- All draft and complete slides must be submitted in PDF format only. Draft slides for both tutorials and conference sessions MUST be provided with CfP submissions otherwise the Programme Committee will be unable to review the submission. For work in progress, the most current information available at time of submission is acceptable. Final slides are to be provided by the specified deadline for publication on the APRICOT website. While the majority of speaking slots will be filled by the first submission deadline, a limited number of slots may be available up to the final submission deadline for presentations that are exceptionally timely, important, or of critical operational importance. Please submit on-line at: http://submission.apnic.net/ Any questions or concerns should be addressed to the Programme Committee by e-mail at: pc-chairs at apricot.net We look forward to receiving your presentation proposals. Mark Tinka & Jonny Martin Co-Chairs, APRICOT Programme Committee program(a)apricot.net

1 0

bgp update destroying transit on redback routers ?
by Igor Ybema 02 Dec '11

02 Dec '11

Hi there, Since about 15:00u GMT we receive bgp updates from our transit which destroys the bgp sessions with them with message: send NOTIFICATION: 3/9 (update: optional attribute error) with 11 byte data. mxReadMs=610 We use redback smartedge routers (SE100) currently for BGP. Anyone who have seen this also? regards, Igor

7 11

Link local for P-t-P links? (Was: IPv6 prefixes longer then /64: are they possible in DOCSIS networks?)
by Mike Jones 02 Dec '11

02 Dec '11

On 1 December 2011 00:55, Jimmy Hess <mysidia(a)gmail.com> wrote: > Please explain. What are the better ways that you would propose > of mitigating ND table overflows? > If you can show a rational alternative, then it would be persuasive as > a better option. > Link-Local? For "true" P-t-P links I guess you don't need any addresses on the interfaces (I don't on my 6in4 tunnels), but I assume most people are referring to ethernet type cross connects, so Link-Local addresses. As long as each device has at least 1 address assigned somewhere (loopback?) that it can use for management/packet generation purposes you don't need an address on every link like you used to do with IPv4. Now that there are plenty of addresses you don't need as many :) I suspect there are probably some practical issues with link-local on some kit and some network configurations due to lack of people doing it this way, but in theory there shouldn't be any reason that you couldn't use link-local for all your links then just have a /128 assigned to each routers loopback for management/packet generation purposes. This could remove overheads of worrying about address assignment for those links, you just need a single /128 per router. Depending on the network it might be better to statically set link locals rather than using automatic ones (fe80::1 and fe80::2 for 'upstream' and 'downstream' or whatever rules you currently use for deciding which end is 1 and which is 2) You could also do something similar for datacentres assigning blocks to customer servers, instead of configuring a /64 for each customer, or a /48 then giving customers blocks inside that to use, just configure a single /64 and give each customer a single address from that block with unassigned ones filtered, then route a /64 to them for any "extra addresses" they might want. Chances are if they need more than a couple of addresses they probably want them routed to them anyway rather than using ND for them all. The issue of dynamic assignments to end customers in a non-datacentre setting is a little more difficult, but I wonder how badly CPEs would break if you tried using DHCPv6 to give them back their link-local addresses, then DHCPv6-PD delegating by routing to their link local address, probably a lot worse than if you just used a /112 of global space. I don't think this area has too many issues though because DHCP ensures that the actual addresses on the links are all known, so this just needs to be used for filtering unknown addresses. Then there's just the question of what to do about the edge networks where SLAAC might be used and where you don't have such strict control over address assignment, i'll pass on that one for now. Link locals aren't as useful nearer to the edges, but for the backbones and datacentre networks they should be able to solve most of the biggest problems with ND attacks. The edge networks where just using link locals isn't really an option you can probably put a stateful firewall in quite easily, as these will be the edge default gateways that clients are sending their traffic directly to rather than needing to be done in the core. Although there really should be an option for users to open the firewall for inbound connections. Am I a complete idiot missing some obvious major issues with link locals, or am i just the only one not thinking IPv4-think? Opinions? :) - Mike

6 7

[NANOG-announce] NANOG54 (San Diego, Feb 5-8, 2012): Early Bird Registration Expiring on Sunday, 12/4
by Dave Temkin 01 Dec '11

01 Dec '11

Please note that the Early Bird registration for NANOG54 expires on Sunday, 12/4. Register now and save $75 off the regular registration fee! Also, as a reminder, the Call for Presentations is still open! Have something that you think is relevant to the NANOG community and would like to have the chance to present it? Please see http://www.nanog.org/meetings/nanog54/callforpresentations.html for more information. Looking forward to seeing you in sunny San Diego! -Dave (For the NANOG Program Committee) _______________________________________________ NANOG-announce mailing list NANOG-announce(a)nanog.org https://mailman.nanog.org/mailman/listinfo/nanog-announce

1 0

MPLS based routing
by Meftah Tayeb 01 Dec '11

01 Dec '11

hello guys, if i want to label my routes in a cisco router i did run through ldp configuration step now i see that labels are distributed, but if i traceroute it from another router i didn't see the icmp arg for the mpls label did i miss anything? atached my configuration :) Meftah Tayeb IT Consulting http://www.tmvoip.com/ phone: +21321656139 Mobile: +213660347746 __________ Information from ESET NOD32 Antivirus, version of virus signature database 6678 (20111202) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com

1 0

Re: bgp update destroying transit on redback routers ?
by Olivier Benghozi 01 Dec '11

01 Dec '11

Alexandre Snarskii <snar(a)snar.spb.ru> wrote: > AGGREGATOR is an optional transitive attribute of length 6. > The attribute contains the last AS number that formed the > aggregate route (encoded as 2 octets), followed by the IP > address of the BGP speaker that formed the aggregate route > (encoded as 4 octets). Usage of this attribute is described > in 5.1.7 > > And what to do with 4-byte AS-numbers then? That would explain the 8 bytes. Hi, we also have some issues with this here, the update message the Redback logged is: ffff ffff ffff ffff ffff ffff ffff ffff 0049 02 0000 002e 4001 01 00 4002 12 02 04 00000513 00000d1c 0000b611 0000b611 4003 04 50ef82c1 4006 00 c007 08 00 0000 0000 0000 00 16 ce7d a4 The prefix is 206.125.164.0/22, AS-PATH is 1299 3356 46609 46609 (Telia, Level3, and finally Hostlogistic with one prepend). The AGGREGATOR is full of 0. I guess this could be what bothers the Redback/Ericsson code. I see the same route by other sessions, and the aggregator looks OK, since the sh bgp says: 206.125.164.0/22 [...] 8218 4436 46609 46609 [...] Origin incomplete, localpref 100, med 100, weight 100, external, best aggregator: 206.125.165.242, AS 46609, atomic-aggregate So Hostlogistic route to Level3 is malformed (according to the RFC, the AGGREGATOR content is mandatory if the attribute is present), but their route to NLayer is OK. Or maybe a Level3 router has a problem? Anyway, our Redback/Ericsson routers are the problem now, since the other vendors don't throw away the BGP sessions... I've opened a case at Ericsson, still waiting for an answer :-/ regards, Olivier Benghozi Wifirst

2 1