- Test - lists.nanog.org

Call for Papers: RIPE 66, 13-17 May 2013 in Dublin, Ireland
by Benno Overeinder 15 Feb '13

15 Feb '13

Call for Papers: RIPE 66 A RIPE Meeting is an open event where Internet Service Providers, network operators and other interested parties get together. Although the meeting is mostly technical, it is also a chance for people to meet and network with others in their field. RIPE 66 will take place on 13-17 May 2013 in Dublin, Ireland. The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the Plenary, BoF and Tutorial sessions at RIPE 66. The PC is looking for presentations covering topics of network engineering and operations, including but not limited to: - IPv6 deployment - Managing IPv4 scarcity in operations - Commercial transactions of IPv4 addresses - Data center technologies - Network and DNS operations - Internet governance and regulatory practices - Network and routing security - Content delivery - Internet peering and mobile data exchange Submissions Attendees of the RIPE meetings are quite sensitive to keeping presentations non-commercial, and product marketing talks are strongly discouraged. Repeated audience feedback shows that the most successful talks focus on operational experience, research results, or case studies. For example, presenters wishing to describe a commercial solution should focus on the underlying technology and not attempt a product demonstration. Presenters who are proposing a panel or BoF are encouraged to include speakers from several (perhaps even competing) companies and/or a neutral facilitator. In addition to presentations selected in advance for the Plenary, the RIPE PC also offers several time slots for “lightning talks” which are selected immediately before or during the conference. The following requirements apply: - Proposals for Plenary talks, BoFs, Panels and Tutorials must be submitted for full consideration no later than 24 February 2013, using the meeting submission system at: https://meetings.ripe.net/pc/ Proposals submitted after this date will be considered on a space-available basis. - Presenters should indicate how much time they will require (30 minutes for talks is a common maximum duration, although some talks can be longer). - Proposals for talks will only be considered by the PC if they contain at least draft presentation slides (slides may be updated later on). For BoFs and panels, proposals must contain a clear description as well as names of invited panelists/presenters. - Due to potential technical issues, it is expected that most if not all presenters/panelists will be physically present at the RIPE meeting. - Lightning talks should be submitted using the meeting submission system. They must be short (10 minutes maximum) and often involve more timely topics. They can be submitted at any time. The allocation of lightning talk slots will be announced one day prior to the relevant session. If you have any questions or requests concerning content submissions, please email pc [at] ripe [dot] net. -- Benno J. Overeinder NLnet Labs http://www.nlnetlabs.nl/

1 0

Weekly Routing Table Report
by Routing Analysis Role Account 15 Feb '13

15 Feb '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 04:00 +10GMT Sat 16 Feb, 2013 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 443072 Prefixes after maximum aggregation: 182226 Deaggregation factor: 2.43 Unique aggregates announced to Internet: 217209 Total ASes present in the Internet Routing Table: 43311 Prefixes per ASN: 10.23 Origin-only ASes present in the Internet Routing Table: 34169 Origin ASes announcing only one prefix: 15936 Transit ASes present in the Internet Routing Table: 5755 Transit-only ASes present in the Internet Routing Table: 141 Average AS path length visible in the Internet Routing Table: 4.6 Max AS path length visible: 29 Max AS path prepend of ASN ( 28730) 25 Prefixes from unregistered ASNs in the Routing Table: 384 Unregistered ASNs in the Routing Table: 139 Number of 32-bit ASNs allocated by the RIRs: 3756 Number of 32-bit ASNs visible in the Routing Table: 3387 Prefixes from 32-bit ASNs in the Routing Table: 9286 Special use prefixes present in the Routing Table: 17 Prefixes being announced from unallocated address space: 188 Number of addresses announced to Internet: 2616732428 Equivalent to 155 /8s, 248 /16s and 43 /24s Percentage of available address space announced: 70.7 Percentage of allocated address space announced: 70.7 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 94.3 Total number of prefixes smaller than registry allocations: 156364 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 106392 Total APNIC prefixes after maximum aggregation: 33093 APNIC Deaggregation factor: 3.21 Prefixes being announced from the APNIC address blocks: 107472 Unique aggregates announced from the APNIC address blocks: 43908 APNIC Region origin ASes present in the Internet Routing Table: 4816 APNIC Prefixes per ASN: 22.32 APNIC Region origin ASes announcing only one prefix: 1237 APNIC Region transit ASes present in the Internet Routing Table: 807 Average APNIC Region AS path length visible: 4.6 Max APNIC Region AS path length visible: 23 Number of APNIC region 32-bit ASNs visible in the Routing Table: 429 Number of APNIC addresses announced to Internet: 718760448 Equivalent to 42 /8s, 215 /16s and 106 /24s Percentage of available APNIC address space announced: 84.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-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, 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: 155600 Total ARIN prefixes after maximum aggregation: 78739 ARIN Deaggregation factor: 1.98 Prefixes being announced from the ARIN address blocks: 156259 Unique aggregates announced from the ARIN address blocks: 70972 ARIN Region origin ASes present in the Internet Routing Table: 15463 ARIN Prefixes per ASN: 10.11 ARIN Region origin ASes announcing only one prefix: 5840 ARIN Region transit ASes present in the Internet Routing Table: 1600 Average ARIN Region AS path length visible: 4.1 Max ARIN Region AS path length visible: 27 Number of ARIN region 32-bit ASNs visible in the Routing Table: 18 Number of ARIN addresses announced to Internet: 1076205440 Equivalent to 64 /8s, 37 /16s and 151 /24s Percentage of available ARIN address space announced: 56.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, 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: 113997 Total RIPE prefixes after maximum aggregation: 58785 RIPE Deaggregation factor: 1.94 Prefixes being announced from the RIPE address blocks: 117156 Unique aggregates announced from the RIPE address blocks: 74884 RIPE Region origin ASes present in the Internet Routing Table: 17064 RIPE Prefixes per ASN: 6.87 RIPE Region origin ASes announcing only one prefix: 8151 RIPE Region transit ASes present in the Internet Routing Table: 2778 Average RIPE Region AS path length visible: 5.0 Max RIPE Region AS path length visible: 29 Number of RIPE region 32-bit ASNs visible in the Routing Table: 2190 Number of RIPE addresses announced to Internet: 653473892 Equivalent to 38 /8s, 243 /16s and 56 /24s Percentage of available RIPE address space announced: 95.0 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, 196608-199679 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: 47136 Total LACNIC prefixes after maximum aggregation: 9119 LACNIC Deaggregation factor: 5.17 Prefixes being announced from the LACNIC address blocks: 50849 Unique aggregates announced from the LACNIC address blocks: 23570 LACNIC Region origin ASes present in the Internet Routing Table: 1810 LACNIC Prefixes per ASN: 28.09 LACNIC Region origin ASes announcing only one prefix: 526 LACNIC Region transit ASes present in the Internet Routing Table: 342 Average LACNIC Region AS path length visible: 4.8 Max LACNIC Region AS path length visible: 27 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 743 Number of LACNIC addresses announced to Internet: 123073832 Equivalent to 7 /8s, 85 /16s and 245 /24s Percentage of available LACNIC address space announced: 73.4 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, 191/8, 200/8, 201/8, AfriNIC Region Analysis Summary ------------------------------- Prefixes being announced by AfriNIC Region ASes: 10524 Total AfriNIC prefixes after maximum aggregation: 2437 AfriNIC Deaggregation factor: 4.32 Prefixes being announced from the AfriNIC address blocks: 11148 Unique aggregates announced from the AfriNIC address blocks: 3706 AfriNIC Region origin ASes present in the Internet Routing Table: 599 AfriNIC Prefixes per ASN: 18.61 AfriNIC Region origin ASes announcing only one prefix: 182 AfriNIC Region transit ASes present in the Internet Routing Table: 134 Average AfriNIC Region AS path length visible: 4.7 Max AfriNIC Region AS path length visible: 25 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 7 Number of AfriNIC addresses announced to Internet: 44860416 Equivalent to 2 /8s, 172 /16s and 132 /24s Percentage of available AfriNIC address space announced: 44.6 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 2938 11558 924 Korea Telecom (KIX) 17974 2486 824 85 PT TELEKOMUNIKASI INDONESIA 7545 1824 301 88 TPG Internet Pty Ltd 4755 1686 382 190 TATA Communications formerly 9829 1430 1144 44 BSNL National Internet Backbo 9583 1207 89 501 Sify Limited 7552 1161 1070 12 Vietel Corporation 4808 1109 2040 316 CNCGROUP IP network: China169 9498 1061 310 75 BHARTI Airtel Ltd. 24560 1044 385 160 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 3065 3696 101 bellsouth.net, inc. 7029 2170 1265 211 Windstream Communications Inc 18566 2080 382 185 Covad Communications 22773 1987 2931 128 Cox Communications, Inc. 1785 1955 677 125 PaeTec Communications, Inc. 20115 1692 1610 616 Charter Communications 4323 1603 1139 396 Time Warner Telecom 30036 1344 287 686 Mediacom Communications Corp 7018 1301 10552 856 AT&T WorldNet Services 11492 1197 217 334 Cable One 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 1858 544 16 Corbina telecom 2118 1115 97 13 EUnet/RELCOM Autonomous Syste 34984 1054 232 203 BILISIM TELEKOM 13188 850 99 26 Educational Network 12479 819 783 68 Uni2 Autonomous System 31148 758 39 18 FreeNet ISP 20940 750 255 592 Akamai Technologies European 6830 712 2313 433 UPC Distribution Services 8551 711 367 39 Bezeq International 34744 670 185 43 SC GVM SISTEM 2003 SRL 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 2381 1327 87 NET Servicos de Comunicao S.A 10620 2319 397 223 TVCABLE BOGOTA 7303 1679 1147 206 Telecom Argentina Stet-France 8151 1506 2824 396 UniNet S.A. de C.V. 6503 1445 435 67 AVANTEL, S.A. 14754 939 120 78 Telgua S. A. 27947 776 86 98 Telconet S.A 18881 771 716 18 Global Village Telecom 3816 686 306 87 Empresa Nacional de Telecomun 7738 613 1242 34 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 1286 80 4 MOBITEL 24863 898 275 36 LINKdotNET AS number 8452 542 958 13 TEDATA 6713 503 602 20 Itissalat Al-MAGHRIB 24835 329 80 8 RAYA Telecom - Egypt 3741 266 906 224 The Internet Solution 12258 193 28 67 Vodacom Internet Company 15706 191 32 6 Sudatel Internet Exchange Aut 29975 191 667 21 Vodacom 16637 189 696 90 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 3065 3696 101 bellsouth.net, inc. 4766 2938 11558 924 Korea Telecom (KIX) 17974 2486 824 85 PT TELEKOMUNIKASI INDONESIA 28573 2381 1327 87 NET Servicos de Comunicao S.A 10620 2319 397 223 TVCABLE BOGOTA 7029 2170 1265 211 Windstream Communications Inc 18566 2080 382 185 Covad Communications 22773 1987 2931 128 Cox Communications, Inc. 1785 1955 677 125 PaeTec Communications, Inc. 8402 1858 544 16 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 17974 2486 2401 PT TELEKOMUNIKASI INDONESIA 28573 2381 2294 NET Servicos de Comunicao S.A 10620 2319 2096 TVCABLE BOGOTA 4766 2938 2014 Korea Telecom (KIX) 7029 2170 1959 Windstream Communications Inc 18566 2080 1895 Covad Communications 22773 1987 1859 Cox Communications, Inc. 8402 1858 1842 Corbina telecom 1785 1955 1830 PaeTec Communications, Inc. 7545 1824 1736 TPG Internet Pty Ltd 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 30031 UNALLOCATED 12.27.122.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 209 Qwest 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 33649 UNALLOCATED 12.111.112.0/24 19029 New Edge Networks 26064 UNALLOCATED 12.149.37.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/24 2876 Jump Management SRL 128.0.16.0/21 43568 RIPE Network Coordination Cen 128.0.24.0/21 41794 Altline LLC 128.0.60.0/23 57417 INTERNET TASMANIA SRL 128.0.62.0/23 57417 INTERNET TASMANIA SRL 128.0.72.0/21 23456 32-bit ASN transition 128.0.80.0/20 52041 Timer LTD 128.0.96.0/21 12886 LEWTelNet GmbH 128.0.104.0/23 51848 FOP Gabidullina Ludmila Nikol 128.0.106.0/24 23456 32-bit ASN transition Complete listing at http://thyme.rand.apnic.net/current/data-dsua Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 41.138.95.0/24 36930 ZanZibar Telecom 41.222.80.0/21 37110 Moztel LDA 62.12.96.0/19 38478 SunnyVision Limited 62.61.220.0/24 24974 Tachyon Europe BV - Wireless 62.61.221.0/24 24974 Tachyon Europe BV - Wireless 64.185.224.0/24 27431 JTL Networks Inc. 64.185.225.0/24 27431 JTL Networks Inc. 64.185.226.0/24 27431 JTL Networks Inc. 64.185.227.0/24 27431 JTL Networks Inc. 64.185.228.0/24 27431 JTL Networks Inc. 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:17 /9:13 /10:29 /11:88 /12:246 /13:483 /14:865 /15:1553 /16:12565 /17:6594 /18:11003 /19:21737 /20:31235 /21:33357 /22:45541 /23:41171 /24:232283 /25:1389 /26:1750 /27:859 /28:182 /29:75 /30:16 /31:0 /32:21 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 18566 2030 2080 Covad Communications 6389 1758 3065 bellsouth.net, inc. 8402 1585 1858 Corbina telecom 7029 1554 2170 Windstream Communications Inc 22773 1303 1987 Cox Communications, Inc. 36998 1280 1286 MOBITEL 30036 1235 1344 Mediacom Communications Corp 11492 1160 1197 Cable One 1785 1035 1955 PaeTec Communications, Inc. 6503 965 1445 AVANTEL, S.A. Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:672 2:747 3:3 4:13 5:760 6:3 8:499 12:1935 13:3 14:741 15:11 16:3 17:8 20:24 23:240 24:1798 27:1445 31:1131 32:54 33:2 34:5 36:11 37:1288 38:847 39:2 40:141 41:2713 42:179 44:4 46:1743 47:1 49:579 50:654 52:12 54:28 55:9 57:28 58:1079 59:560 60:251 61:1321 62:1027 63:2027 64:4308 65:2147 66:4263 67:2046 68:1125 69:3267 70:856 71:525 72:1875 74:2531 75:421 76:289 77:1078 78:1036 79:542 80:1215 81:972 82:627 83:538 84:558 85:1155 86:475 87:929 88:382 89:1746 90:278 91:5412 92:622 93:1693 94:2056 95:1589 96:506 97:336 98:1037 99:52 100:30 101:315 103:2122 105:519 106:131 107:206 108:511 109:1764 110:855 111:1014 112:487 113:739 114:684 115:920 116:876 117:787 118:984 119:1272 120:377 121:701 122:1738 123:1183 124:1320 125:1310 128:541 129:202 130:316 131:641 132:328 133:143 134:259 135:62 136:222 137:236 138:342 139:159 140:216 141:316 142:519 143:369 144:478 145:88 146:525 147:335 148:720 149:349 150:156 151:400 152:400 153:191 154:28 155:367 156:242 157:387 158:260 159:712 160:333 161:422 162:361 163:203 164:577 165:450 166:436 167:572 168:1010 169:131 170:940 171:164 172:4 173:1548 174:586 175:417 176:1166 177:1670 178:1742 180:1384 181:231 182:1153 183:321 184:635 185:236 186:2260 187:1427 188:1936 189:1539 190:6638 192:6322 193:5654 194:4643 195:3678 196:1290 197:891 198:4154 199:5221 200:6025 201:2146 202:8887 203:8759 204:4470 205:2544 206:2803 207:2810 208:4059 209:3508 210:2920 211:1565 212:1937 213:1904 214:901 215:93 216:5095 217:1586 218:594 219:328 220:1263 221:549 222:329 223:421 End of report

1 0

puck.nether.net outage?
by Brian Dickson 14 Feb '13

14 Feb '13

Anyone know about puck.nether.net? I read the "outages" list via web archive there, but can't connect currently. (I know - irony or what.) If you know what's going on, please post on NANOG? kthanks, Brian

5 6

Re: NANOG Digest, Vol 61, Issue 88
by Courtney Smith 14 Feb '13

14 Feb '13

On Feb 13, 2013, at 4:00 PM, nanog-request(a)nanog.org wrote: > ------------------------------ > > Message: 3 > Date: Wed, 13 Feb 2013 10:50:50 -0800 > From: Sean Lazar <knife(a)toaster.net> > To: Michael Thomas <mike(a)mtcc.com> > Cc: NANOG list <nanog(a)nanog.org> > Subject: Re: home network monitoring and shaping > Message-ID: <511BE08A.4020506(a)toaster.net> > Content-Type: text/plain; charset=ISO-8859-1 > > I've had good luck with a via mini ITX board and http://ipcop.org/ > > Anyone have good experience addressing this with TomatoUSB's QoS features? Specifically the Toastman builds. Courtney Smith courtneysmith(a)comcast.net () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments

1 0

NOC display software
by JoeSox 13 Feb '13

13 Feb '13

Just wondering if anyone can recommend Windows software (it could be Linux too but I might need to create a separate host for that configuration) that enables rotating [on one monitor] several webpages (dashboards) or windows (application dashboards). It would be nice if it was freeware or open source but whatever works best is what I am looking for. For example, if I wanted one monitor to cycle thru my local SolarWinds Orion, Office 365 Health Status, and anyother webdashboards. -- Thank You, Joe

8 7

IPv6 support by wifi systems
by Brandon Ross 13 Feb '13

13 Feb '13

Like so many things IPv6, many of the wifi vendors seem to lack decent support for IPv6 clients. I'm not sure why I thought the situation was better than it seems to be, I guess I'm just an optimist. Anyway, what wifi vendors provide the best support for IPv6? I don't really care too much about management, but to deploy wifi in a service provider environment with IPv6, it would seem that you'd want at least: RA Guard DHCPv6 Shield (unless you just do SLAAC, I guess) IPv6 Source Address Guard Am I missing anything critical? -- Brandon Ross Yahoo & AIM: BrandonNRoss +1-404-635-6667 ICQ: 2269442 Schedule a meeting: https://doodle.com/bross Skype: brandonross

6 10

home network monitoring and shaping
by Michael Thomas 13 Feb '13

13 Feb '13

O oracle of nanog: unlike things like rogue processes eating tons of CPU, it seems to me that network monitoring is essentially a black art for the average schmuck home network operator (of which I count myself). That is: if the "network is slow", it's really hard to tell why that might be and who of the eleventy seven devices on my wifi is sucking the life out of my bandwidth. And then even if I get an idea of who the perp is, my remediation choice seems to be "find that device, smash it with sledge hammer". It seems that there really ought to be a better way here to manage my home network. Like, for example, the ability to get stats from router and tell it to shape various devices/flows to play nice. Right now, it seems to me that the state of the art is pretty bad -- static-y kinds of setups for static-y kinds of flows that people-y kind of users don't understand or touch on their home routers. The ob-nanog is that "my intertoobs r slow" is most likely a call to your support desks which is expensive, of course. Is anything happening on this front? Is openwrt, for example, paying much attention to this problem? Mike

9 10

The 100 Gbit/s problem in your network
by fredrik danerklint 13 Feb '13

13 Feb '13

- Well, as it turns out, we don't have that kind of a problem. - You don't? - No, we do not have that kind of a problem in our network. We have plenty of bandwidth available to our customers, thank-you-every-much. - Do you have, just to make an example, about 10 000 customers in a specific area, like an city/county or part of a city/county? - Yes, of course! - Does these customers have at least 10 Mbit/s connection to the Internet? - Yes! Who do you think we are, like stupid! Haha! - Could all those 10 000 customers, just to make it theoretical, hit the 'play'-button on their Internet-connected-TV, at the same time, to watch the latest Quad-HD movie? - Yes. Oh wait a minute now! This is not fair! Damn. We're toast. -- //fredan

24 55

Re: Muni fiber: L1 or L2?
by Jay Ashworth 12 Feb '13

12 Feb '13

----- Original Message ----- > From: "Owen DeLong" <owen(a)delong.com> > On Feb 11, 2013, at 19:24 , Frank Bulk <frnkblk(a)iname.com> wrote: > > > Not if the ONT is mounted on the outside of the home, and just > > copper services brought into the home. > Who cares whether it's copper or fiber you push through the > penetration. What I care about is not that it's optical -- it's that *it's a patchcord*. If the ONT is per ISP, and the patchpoint is an *external* jackbox, then that thru-wall cable has to be a patchcord, not drop cable -- and the ISP field tech will have to work it. *This* *will* cause the installation reliability problems that Scott is scared of. No, either the ONT goes on the outside wall and we poke cat 6, or the drop cable goes inside to a jack box for an interior ONT. > I see no reason not to have the residential install tech that normally > extends the demarc and/or installs whatever required IW (IF?) solution > shouldn't do this. Hopefully that explains my concern. > As others have pointed out, I see good reason for the muni to operate the > L1 plant as a natural monopoly. Time and time again, we've seen that an > L1 plant requires very high density or nearly 100% market share to be > economically viable. Even in the case of very high density you still usually > only get a minute number of L1 providers and almost never more than 2 > per media type (rarely even more than 1). I honestly don't actually expect any L1 providers. But that doesn't mean I'm willing to foreclose the possibility. > However, when it comes to inside wiring (or fiber), I see no benefit to not > leaving that to the first service provider to install each residence and > possibly even being redone for every install. Some providers may use > ONTs, others may not. (ONT is, after all AE/PON specific and there's no > reason a provider couldn't drop a 24 port Gig-E switch in the colo with > a 10G uplink (or a stack of them) and sell Gig connections on regular > 1000baseFX (or LX or SX or whatever) service. Sure. > I'm not saying that's necessarily a good business model, but, I'm saying > that the muni really should avoid encumbering its L1 offering with > any additional technologies anywhere. Yup; I've been saying that right along. That's why I'd prefer to do the install as optical patch/interior, if I can sell it. Doesn't mean I don't understand why that might be troublesome. That, in turn doesn't mean I can't coil the tail in a box, and poke it through on order. > If they want to run L2 or L3 service of last resort, I have no problem with > that, but, it should be completely separate from their L1 offering and should > avoid any blurring of the lines. I believe, Owen, that that's the first time I've heard you extend that opinion to L2; everyone had me pretty much convinced that my plan to offer L2 was not likely to cause competitive pressure in the way the L3 service would. Had I misunderstood you? Cheers, -- jra -- Jay R. Ashworth Baylink jra(a)baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII St Petersburg FL USA #natog +1 727 647 1274

4 4

Reachability problem with AS8388 [194.63.246.0/23]
by Carlos Friacas 12 Feb '13

12 Feb '13

Hello, Does anyone has reachability issues with AS8388? It seems i'm unable to get packets back from 194.63.246.0/23, but only if the source is my 193.136.0.0/15 block, at AS1930. It works well from my other netblocks. I'm basically performing a (non-recursive) DNS query to DNS servers within 194.63.246.0/23. I've been trying to involve upstream providers to take a deeper look at this problem, but i haven't had any luck so far. I can't even get a traceroute back to my network from anyone at AS8388. Any suggestions? Best Regards, Carlos Friaças

2 3