December 2011 - Test - lists.nanog.org

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

23 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 24 Dec, 2011 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 387081 Prefixes after maximum aggregation: 168128 Deaggregation factor: 2.30 Unique aggregates announced to Internet: 189666 Total ASes present in the Internet Routing Table: 39672 Prefixes per ASN: 9.76 Origin-only ASes present in the Internet Routing Table: 32553 Origin ASes announcing only one prefix: 15517 Transit ASes present in the Internet Routing Table: 5339 Transit-only ASes present in the Internet Routing Table: 141 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: 1962 Unregistered ASNs in the Routing Table: 1019 Number of 32-bit ASNs allocated by the RIRs: 2123 Number of 32-bit ASNs visible in the Routing Table: 1780 Prefixes from 32-bit ASNs in the Routing Table: 4232 Special use prefixes present in the Routing Table: 2 Prefixes being announced from unallocated address space: 127 Number of addresses announced to Internet: 2503477552 Equivalent to 149 /8s, 56 /16s and 9 /24s Percentage of available address space announced: 67.5 Percentage of allocated address space announced: 67.5 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 91.8 Total number of prefixes smaller than registry allocations: 163949 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 95769 Total APNIC prefixes after maximum aggregation: 31336 APNIC Deaggregation factor: 3.06 Prefixes being announced from the APNIC address blocks: 92133 Unique aggregates announced from the APNIC address blocks: 38669 APNIC Region origin ASes present in the Internet Routing Table: 4619 APNIC Prefixes per ASN: 19.95 APNIC Region origin ASes announcing only one prefix: 1249 APNIC Region transit ASes present in the Internet Routing Table: 729 Average APNIC Region AS path length visible: 4.3 Max APNIC Region AS path length visible: 18 Number of APNIC region 32-bit ASNs visible in the Routing Table: 125 Number of APNIC addresses announced to Internet: 632233600 Equivalent to 37 /8s, 175 /16s and 30 /24s Percentage of available APNIC address space announced: 80.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, 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: 146693 Total ARIN prefixes after maximum aggregation: 74924 ARIN Deaggregation factor: 1.96 Prefixes being announced from the ARIN address blocks: 118806 Unique aggregates announced from the ARIN address blocks: 48828 ARIN Region origin ASes present in the Internet Routing Table: 14819 ARIN Prefixes per ASN: 8.02 ARIN Region origin ASes announcing only one prefix: 5672 ARIN Region transit ASes present in the Internet Routing Table: 1566 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: 14 Number of ARIN addresses announced to Internet: 804598720 Equivalent to 47 /8s, 245 /16s and 51 /24s Percentage of available ARIN address space announced: 63.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, 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: 94898 Total RIPE prefixes after maximum aggregation: 51720 RIPE Deaggregation factor: 1.83 Prefixes being announced from the RIPE address blocks: 86897 Unique aggregates announced from the RIPE address blocks: 55306 RIPE Region origin ASes present in the Internet Routing Table: 16209 RIPE Prefixes per ASN: 5.36 RIPE Region origin ASes announcing only one prefix: 7986 RIPE Region transit ASes present in the Internet Routing Table: 2575 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: 1239 Number of RIPE addresses announced to Internet: 494850504 Equivalent to 29 /8s, 126 /16s and 209 /24s Percentage of available RIPE address space announced: 79.7 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: 36823 Total LACNIC prefixes after maximum aggregation: 8014 LACNIC Deaggregation factor: 4.59 Prefixes being announced from the LACNIC address blocks: 36312 Unique aggregates announced from the LACNIC address blocks: 18904 LACNIC Region origin ASes present in the Internet Routing Table: 1559 LACNIC Prefixes per ASN: 23.29 LACNIC Region origin ASes announcing only one prefix: 451 LACNIC Region transit ASes present in the Internet Routing Table: 287 Average LACNIC Region AS path length visible: 4.5 Max LACNIC Region AS path length visible: 27 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 398 Number of LACNIC addresses announced to Internet: 94882952 Equivalent to 5 /8s, 167 /16s and 204 /24s Percentage of available LACNIC address space announced: 62.8 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: 8506 Total AfriNIC prefixes after maximum aggregation: 2063 AfriNIC Deaggregation factor: 4.12 Prefixes being announced from the AfriNIC address blocks: 6551 Unique aggregates announced from the AfriNIC address blocks: 2036 AfriNIC Region origin ASes present in the Internet Routing Table: 503 AfriNIC Prefixes per ASN: 13.02 AfriNIC Region origin ASes announcing only one prefix: 159 AfriNIC Region transit ASes present in the Internet Routing Table: 111 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: 30835968 Equivalent to 1 /8s, 214 /16s and 133 /24s Percentage of available AfriNIC address space announced: 45.9 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 2488 11102 967 Korea Telecom (KIX) 17974 1716 503 38 PT TELEKOMUNIKASI INDONESIA 7545 1629 303 86 TPG Internet Pty Ltd 4755 1515 385 157 TATA Communications formerly 7552 1420 1064 7 Vietel Corporation 9829 1168 989 28 BSNL National Internet Backbo 9583 1101 81 494 Sify Limited 4808 1076 2036 307 CNCGROUP IP network: China169 24560 1012 385 167 Bharti Airtel Ltd., Telemedia 18101 974 131 157 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 3473 3814 219 bellsouth.net, inc. 7029 2910 1017 200 Windstream Communications Inc 18566 2093 383 177 Covad Communications 1785 1860 680 122 PaeTec Communications, Inc. 4323 1621 1065 385 Time Warner Telecom 20115 1612 1549 622 Charter Communications 22773 1515 2909 107 Cox Communications, Inc. 30036 1466 260 686 Mediacom Communications Corp 19262 1389 4683 401 Verizon Global Networks 7018 1302 7012 854 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 1617 480 15 Corbina telecom 15557 1092 2161 64 LDCOM NETWORKS 2118 672 99 14 EUnet/RELCOM Autonomous Syste 6830 648 1928 413 UPC Distribution Services 34984 628 132 197 BILISIM TELEKOM 20940 555 179 441 Akamai Technologies European 12479 551 636 53 Uni2 Autonomous System 3320 532 8162 398 Deutsche Telekom AG 3292 480 2106 407 TDC Tele Danmark 8866 464 134 27 Bulgarian Telecommunication C 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 1719 318 157 TVCABLE BOGOTA 28573 1574 1064 75 NET Servicos de Comunicao S.A 8151 1452 2960 356 UniNet S.A. de C.V. 7303 1249 752 174 Telecom Argentina Stet-France 27947 631 73 94 Telconet S.A 22047 582 322 17 VTR PUNTO NET S.A. 7738 551 1050 31 Telecomunicacoes da Bahia S.A 3816 547 237 90 Empresa Nacional de Telecomun 6503 539 434 67 AVANTEL, S.A. 11172 530 102 97 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 1036 958 13 TEDATA 24863 790 146 36 LINKdotNET AS number 3741 280 939 229 The Internet Solution 6713 243 647 17 Itissalat Al-MAGHRIB 15706 242 32 6 Sudatel Internet Exchange Aut 33776 240 13 8 Starcomms Nigeria Limited 29571 217 17 13 Ci Telecom Autonomous system 12258 195 28 60 Vodacom Internet Company 24835 188 80 8 RAYA Telecom - Egypt 16637 160 664 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 3473 3814 219 bellsouth.net, inc. 7029 2910 1017 200 Windstream Communications Inc 4766 2488 11102 967 Korea Telecom (KIX) 18566 2093 383 177 Covad Communications 1785 1860 680 122 PaeTec Communications, Inc. 10620 1719 318 157 TVCABLE BOGOTA 17974 1716 503 38 PT TELEKOMUNIKASI INDONESIA 7545 1629 303 86 TPG Internet Pty Ltd 4323 1621 1065 385 Time Warner Telecom 8402 1617 480 15 Corbina telecom 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 2910 2710 Windstream Communications Inc 18566 2093 1916 Covad Communications 1785 1860 1738 PaeTec Communications, Inc. 17974 1716 1678 PT TELEKOMUNIKASI INDONESIA 8402 1617 1602 Corbina telecom 10620 1719 1562 TVCABLE BOGOTA 7545 1629 1543 TPG Internet Pty Ltd 4766 2488 1521 Korea Telecom (KIX) 28573 1574 1499 NET Servicos de Comunicao S.A 7552 1420 1413 Vietel Corporation 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 32873 UNALLOCATED 12.46.100.0/23 10912 InterNAP Network Ser 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 14.192.0.0/22 45464 Room 201, TGU Bldg 14.192.4.0/22 45464 Room 201, TGU Bldg 14.192.8.0/22 45464 Room 201, TGU Bldg 14.192.12.0/22 45464 Room 201, TGU Bldg 14.192.16.0/22 45464 Room 201, TGU Bldg 14.192.20.0/22 45464 Room 201, TGU Bldg 14.192.24.0/22 45464 Room 201, TGU Bldg 14.192.28.0/22 45464 Room 201, TGU Bldg 37.19.72.0/21 42322 Zhanr Ltd. 37.25.64.0/21 33828 iptoX GmbH 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:237 /13:465 /14:814 /15:1448 /16:12072 /17:6121 /18:10183 /19:20111 /20:27962 /21:28218 /22:38383 /23:35824 /24:201495 /25:1182 /26:1403 /27:771 /28:166 /29:55 /30:14 /31:0 /32:18 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 7029 2538 2910 Windstream Communications Inc 6389 2118 3473 bellsouth.net, inc. 18566 2042 2093 Covad Communications 10620 1614 1719 TVCABLE BOGOTA 8402 1596 1617 Corbina telecom 30036 1426 1466 Mediacom Communications Corp 11492 1115 1152 Cable One 1785 1063 1860 PaeTec Communications, Inc. 7011 1051 1168 Citizens Utilities 15557 1042 1092 LDCOM NETWORKS Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:470 2:427 4:15 5:1 6:3 8:366 12:1946 13:1 14:576 15:11 16:3 17:7 20:9 23:79 24:1716 27:1129 31:734 32:67 33:2 34:2 36:4 37:6 38:774 40:115 41:2978 42:78 43:1 44:3 46:1142 47:3 49:280 50:471 52:13 55:6 56:2 57:42 58:924 59:488 60:342 61:1172 62:937 63:1963 64:4137 65:2303 66:4372 67:1989 68:1167 69:3134 70:924 71:410 72:1787 74:2640 75:431 76:320 77:941 78:871 79:469 80:1167 81:839 82:524 83:529 84:577 85:1162 86:743 87:905 88:353 89:1585 90:249 91:4375 92:533 93:1525 94:1333 95:1051 96:398 97:286 98:785 99:38 100:2 101:130 103:582 106:11 107:118 108:100 109:1404 110:675 111:827 112:432 113:494 114:591 115:707 116:873 117:713 118:891 119:1272 120:359 121:671 122:1600 123:1029 124:1329 125:1347 128:554 129:189 130:185 131:586 132:163 133:21 134:226 135:54 136:213 137:151 138:285 139:126 140:492 141:256 142:382 143:389 144:501 145:67 146:475 147:222 148:634 149:269 150:165 151:191 152:445 153:170 154:7 155:383 156:210 157:365 158:154 159:504 160:358 161:221 162:333 163:186 164:522 165:389 166:544 167:455 168:816 169:146 170:830 171:95 172:4 173:1803 174:602 175:400 176:323 177:425 178:1148 180:1207 181:39 182:674 183:265 184:408 185:1 186:1398 187:780 188:1003 189:1174 190:5316 192:5979 193:5439 194:3781 195:3182 196:1291 197:170 198:3615 199:4233 200:5523 201:1681 202:8489 203:8524 204:4344 205:2419 206:2681 207:2819 208:4010 209:3563 210:2746 211:1476 212:1956 213:1800 214:796 215:93 216:4919 217:1473 218:569 219:336 220:1255 221:529 222:323 223:265 End of report

1 0

RE: Speed Test Results
by Frank A. Coluccio 23 Dec '11

23 Dec '11

1 0

MPLS IPVPN “pipe mode” tunneling
by Ruben Tripiana Martin 23 Dec '11

23 Dec '11

Hi all First of all I'm new to this list, so although I've checked the Mailing list FAQs, I apologize if my post is not appropriate. I decided to post these questions here as I think is one of the biggest networks engineering communities, and therefore with the biggest gained experience... and the questions are basically about that... experience. To get to the point, my questions are: Does anyone have any input regarding if a majority of global carriers offers “pipe mode” tunneling as regular feature in their MPLS IP-VPN services? According to your experience do you feel is fairly common? Thanks a lot in advance Ruben Tripiana

1 0

what if...?
by Eduardo A. Suárez 23 Dec '11

23 Dec '11

Hi, what if evil guys hack my mom ISP DNS servers and use RPZ to redirect traffic from mom_bank.com to evil.com? How can she detect this? Eduardo.- -- Eduardo A. Suarez Facultad de Ciencias Astronómicas y Geofísicas - UNLP FCAG: (0221)-4236593 int. 172/Cel: (0221)-15-4557542/Casa: (0221)-4526589 ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

12 11

Help with quagga BGP config for ipv6 route-server
by David Waitzman 22 Dec '11

22 Dec '11

I am trying to set up BGP peering with a route-server, concurrently dual-stack. BGP 4 over an IPv4 connection works fine. A separate BGP 6 over IPv6 fails: with an "[Error] No common capability". I am using quagga 0.99.20 on ubuntu 10.04.03. I don't know what the route-server is. I have tried to tell both quagga to not be strict about capabilities or not negotiate them at all. My quagga config includes: router bgp XX no bgp enforce-first-as no bgp default ipv4-unicast !! tried with and without this bgp router-id XX network XY/24 route-map SetAttr neighbor XX4 remote-as XX neighbor XX4 activate neighbor XX4 next-hop-self neighbor XX4 send-community address-family ipv6 network XY6/48 route-map SetAttr neighbor XX6 remote-as XX neighbor XX6 activate neighbor XX6 next-hop-self neighbor XX6 send-community neighbor XX6 soft-reconfiguration inbound The code, I think, that's triggering the error is: /* Check there is no common capability send Unsupported Capability error. */ if (*capability && ! CHECK_FLAG (peer->flags, PEER_FLAG_OVERRIDE_CAPABILITY)) { if (! peer->afc_nego[AFI_IP][SAFI_UNICAST] && ! peer->afc_nego[AFI_IP][SAFI_MULTICAST] && ! peer->afc_nego[AFI_IP][SAFI_MPLS_VPN] && ! peer->afc_nego[AFI_IP6][SAFI_UNICAST] && ! peer->afc_nego[AFI_IP6][SAFI_MULTICAST]) From tcpdump, my side's open message includes: Open Message (1), length: 57 Version 4, my AS XX, Holdtime 180s, ID XX4 !! XX4 is my V4 address Optional parameters, length: 28 Option Capabilities Advertisement (2), length: 6 Multiprotocol Extensions (1), length: 4 AFI IPv4 (1), SAFI Unicast (1) 0x0000: 0001 0001 Option Capabilities Advertisement (2), length: 2 Route Refresh (Cisco) (128), length: 0 Option Capabilities Advertisement (2), length: 2 Route Refresh (2), length: 0 Option Capabilities Advertisement (2), length: 6 32-Bit AS Number (65), length: 4 no decoder for Capability 65 0x0000: 0000 e0c5 Option Capabilities Advertisement (2), length: 2 Unknown (66), length: 0 no decoder for Capability 66 The route-server's response is: Open Message (1), length: 45 Version 4, my AS XX, Holdtime 240s, ID XY4 !! XY4 is his V4 address Optional parameters, length: 16 Option Capabilities Advertisement (2), length: 14 Multiprotocol Extensions (1), length: 4 AFI IPv6 (2), SAFI Unicast (1) 0x0000: 0002 0001 To which I respond: Notification Message (3), length: 27, OPEN Message Error (2), subcode Capability Message Error (7) When I add "dont-capability-negotiate" to the config, I send: Open Message (1), length: 29 Version 4, my AS 57541, Holdtime 180s, ID XX4 Optional parameters, length: 0 I get back: Open Message (1), length: 45 Version 4, my AS XX, Holdtime 240s, ID XY4 Optional parameters, length: 16 Option Capabilities Advertisement (2), length: 14 Multiprotocol Extensions (1), length: 4 AFI IPv6 (2), SAFI Unicast (1) 0x0000: 0002 0001 I respond: Notification Message (3), length: 27, OPEN Message Error (2), subcode Capability Message Error (7) I'm a developer and former rfc writer, not a network operator. thanks nanog, -- David Waitzman BBN Technologies

1 1

RE: bgp update destroying transit on redback routers ?
by Jeff Tantsura 22 Dec '11

22 Dec '11

Hi, Let me take it over from now on, I'm the IP Routing/MPLS Product Manager at Ericsson responsible for all routing protocols. There's nothing wrong in checking ASN in AGGREGATOR, we don't really want see ASN 0 anywhere, that's how draft-wkumari-idr-as0 (draft-ietf-idr-as0-00) came into the worlds. To my knowledge - the only vendor which allows changing ASN in AGGREGATOR is Juniper, see "no-aggregator-id", in the past I've tried to talk to Yakov about it, without any results though. So for those who have it configured - please rethink whether you really need it. As for SEOS - understanding that this badly affects our customers and not having draft-ietf-idr-error-handling fully implemented yet, we will temporarily disable this check in our code. Patch will be made available. Please contact me for any further clarifications. Regards, Jeff P.S. Warren has recently included AGGREGATOR in the draft, please see 2. Behavior This document specifies that a BGP speaker MUST NOT originate or propagate a route with an AS number of zero. If a BGP speaker receives a route which has an AS number of zero in the AS_PATH (or AS4_PATH) attribute, it SHOULD be logged and treated as a WITHDRAW. This same behavior applies to routes containing zero as the Aggregator or AS4 Aggregator.

6 8

BGP noob needs monitoring advice
by Dave Pooser 21 Dec '11

21 Dec '11

Earlier this year I got a /24 of PA space, set up our shiny new router, got BGP working with both my upstreams, and heaved a sigh of relief: "I'll never have to think about THAT again!" (Okay, quit laughing; I SAID I was a noob!) Now, I discover that one of my upstreams quit announcing our route in November (fortunately the provider who assigned us the /24, so we're still covered in their /18) and the other upstream apparently started filtering our announcements last week. I'm working with both of them to get that fixed, but it's made it clear to me that I need to be monitoring this. My question for the group is, how? I can and do monitor my own router, and I can see that I'm receiving full routes from both ISPs. I am capable of manually accessing route servers and looking glass servers to check if they're receiving routes to me, but I'd like something more automated. Free is nice, $$ is not a problem, $$$$ might become a problem. Thanks in advance for any suggestions. -- Dave Pooser Manager of Information Services Alford Media http://www.alfordmedia.com

9 10

Level3 AWS network issues?
by Rob Smith 21 Dec '11

21 Dec '11

Is anyone else seeing issues connecting to the different Amazon AWS products from the east coast via Level3? I'm very high latency once I hit Amazon's network on Level3 for the last day and a half: me@computer:~/$ tracepath s3.amazonaws.com 1: computer.local 0.136ms pmtu 1500 1: XXXXXXXX 6.495ms 1: XXXXXXXX 2.091ms 2: 10.68.96.1 8.933ms 3: gig-2-18-nycmnyr-rtr02.nyc.rr.com 12.440ms 4: tenge-0-4-0-6-nyquny91-rtr001.nyc.rr.com 12.296ms 5: bun6-nyquny91-rtr002.nyc.rr.com 13.894ms 6: ae-3-0.cr0.nyc20.tbone.rr.com 16.869ms 7: 107.14.17.169 10.200ms 8: xe-9-3-0.edge2.Newark1.Level3.net 12.215ms 9: ae-32-52.ebr2.Newark1.Level3.net 12.380ms 10: ae-4-4.ebr2.Washington1.Level3.net 20.277ms 11: ae-92-92.csw4.Washington1.Level3.net 15.482ms 12: ae-2-70.edge3.Washington1.Level3.net 15.972ms asymm 13 *13: AMAZON.COM.edge3.Washington1.Level3.net 277.609ms asymm 16 * *14: 72.21.220.129 311.718ms asymm 17 * *15: 72.21.222.139 325.718ms * *16: 72.21.218.201 279.354ms asymm 17 * *17: 72.21.218.207 276.793ms asymm 15 * I've heard from a few other folks that they're experiencing this as well, but only if they're traversing the Level3 network. I've tried contacting Amazon and tried going through my own provider but haven't been able to get anywhere. Can anyone forward this to the appropriate Amazon/Level3 contacts or provide contact information for someone that I can relay this information to?

1 0

Any tools to help network security
by Deric Kwok 21 Dec '11

21 Dec '11

Hi We discover there are so many (source) ip not belonging to our network to go to outside. We can block it but don't know how to locate the source. Any tools can be easily found out. Thank you

4 3

BGPmon regex
by Christopher J. Pilkington 21 Dec '11

21 Dec '11

I'm trying to edit my prefixes' AS path regex in BGPmon, and when I add a '\s' in the Regular expression field, upon save, the '\' is stripped. Is this expected behavior? The workaround is to insert a '\\s' instead, but one needs to remember to do this on every edit, and I tend to forget which results in panicking the others on our team with false positives. -cjp

3 2