April 2009 - Test - lists.nanog.org

Re: Important New Requirement for IPv4 Requests
by Roger Marquis 25 Apr '09

25 Apr '09

Rich Kulawiec wrote: > If the effort that will go into administering this went instead > into reclaiming IPv4 space that's obviously hijacked and/or being > used by abusive operations, we'd all benefit. But they can't do that without impacting revenue. In order to continue charging fees that are wholly out of proportion to their cost ARIN must: A) ignore all the unneeded legacy /16 allocations, even those owned by organizations with fewer than 300 employees (like net.com) who could easily get by with a /24 B) do nothing while IPv6 languishes due to the absence of a standard for one-to-many NAT and NAPT for v6 and v4/v6 C) periodically raise fees and implement minimal measures like requiring someone to sign a statement of need, so they can at least appear to have been proactive when the impacts of this artificial shortage really begin to impact communications Bottom line: it's about the money. Money and short-term self-interest, same as is causing havoc in other sectors of the economy. Nothing new here. IMO, Roger Marquis

26 42

Config Backup / Inventory
by Joshua Eyres 25 Apr '09

25 Apr '09

Hi, I am looking for a bit of advice around configuration backup / inventory. We currently have a large multi-vendor network which is currently managed through two separate tools (rancid - http://www.shrubbery.net/rancid and ns4 - http://www.noodles.org.uk/ns4.html) Both tools do the job very well, but management have asked that we look for commercial alternatives that have a proper support organisation looking after them. IP Service Activator has been mentioned as something which can fit this role, but I haven't had any experience and I haven't heard a lot of good things about it. We are looking for a tool which is flexible that allows configuration backup to textual form for easy restoration as well as the ability to deploy scripted changes to the network quickly. Do people generally use free tools for network management or are there viable commercial alternatives? Thanks, Josh

9 8

Broadband Subscriber Management
by Sherwin Ang 25 Apr '09

25 Apr '09

Hello Nanog! i just would like to see how other operators are handling broadband/DSL subscribers in their BRAS. Currently, we are implementing PPPoE with AAA on our Redback SE's and Cisco boxes. As our subscriber base grows and grows, management of user logins, passwords, password resets, password changes are getting really huge. Some customers also complains about the method of logging in, asking for an easier way to do it or dump logins altogether. We're looking at DHCP/CLIPS for Redback but haven't really tested it since it requires a new license for it. For Cisco, we've been empty so far in looking for a solution wherein we still have accounting and rate-limiting on subscriber vc's. how are network operators in your areas do it? DHCP? if i do DHCP, will i still have the flexibility of sending a radius reply attribute so i could rate-limit the subscribers speed? or still offer speed on demand via radius/time-based upgrade of their rate-limits during off-peak hours? thank you for any insights that you may share. -Sherwin

13 18

RE: Important New Requirement for IPv4 Requests
by Skywing 24 Apr '09

24 Apr '09

Keep in mind that you also need to patch your clients for perf improvements bidirectionally. As well as patching locally means you must assume responsibility for custom builds for security fixes on all of your clients and servers. - S -----Original Message----- From: Kevin Oberman <oberman(a)es.net> Sent: Friday, April 24, 2009 13:39 To: Skywing <Skywing(a)valhallalegends.com> Cc: Jo Rhett <jrhett(a)netconsonance.com>; Joe Greco <jgreco(a)ns.sol.net>; bmanning(a)vacation.karoshi.com <bmanning(a)vacation.karoshi.com>; nanog(a)nanog.org <nanog(a)nanog.org> Subject: Re: Important New Requirement for IPv4 Requests > From: Skywing <Skywing(a)valhallalegends.com> > Date: Fri, 24 Apr 2009 10:55:07 -0500 > > Of course, sftp and other ssh-based protocols are *still* hamstrung to > a maximum of 32k data outstanding due to hardcoded SSH channel window > sizes by default for most people, unless you're patching up both your > clients and servers. > > Sadly, this blows ssh out of the water for anything with even modest > high-bitrate requirements over moderate-BDP links. The HPN patches for OpenSSH are readily available and, at least on FreeBSD, including them is just a single checkbox when you install. That said, I have been told that there is a corner case where a transfer using the HPN patches will lock up. I have never seen it, but that is purported to be the reason that OpenBSD has not accepted the patches for the base OpenSSH software. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman(a)es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751

1 0

IXP
by Sharlon R. Carty 24 Apr '09

24 Apr '09

Hello NANOG, I like would to know what are best practices for an internet exchange. I have some concerns about the following; Can the IXP members use RFC 1918 ip addresses for their peering? Can the IXP members use private autonomous numbers for their peering? Maybe the answer is obviuos, but I like to know from any IXP admins what their setup/experiences have been. -- --sharlon

40 86

RE: Important New Requirement for IPv4 Requests
by Skywing 24 Apr '09

24 Apr '09

Of course, sftp and other ssh-based protocols are *still* hamstrung to a maximum of 32k data outstanding due to hardcoded SSH channel window sizes by default for most people, unless you're patching up both your clients and servers. Sadly, this blows ssh out of the water for anything with even modest high-bitrate requirements over moderate-BDP links. - S -----Original Message----- From: Jo Rhett <jrhett(a)netconsonance.com> Sent: Thursday, April 23, 2009 23:27 To: Joe Greco <jgreco(a)ns.sol.net> Cc: bmanning(a)vacation.karoshi.com <bmanning(a)vacation.karoshi.com>; nanog(a)nanog.org <nanog(a)nanog.org> Subject: Re: Important New Requirement for IPv4 Requests On Apr 22, 2009, at 7:42 AM, Joe Greco wrote: > While HTTP remains popular as a way to interact with humans, > especially if > you want to try to do redirects, acknowledge license agreements, > etc., FTP > is the file transfer protocol of choice for basic file transfer Speak for yourself. I haven't used FTP to transfer files in 10 years now. About 7 years ago I turned off FTP support for all of our webhosting clients, and forced them to use SFTP. 3 left, for a net loss of $45/month. And we stopped having to deal with the massive undertaking that supporting FTP properly chrooted and capable of dealing with all parts of the multi-mount web platform required. We've never looked back. Ever once in a while I find someone who's offering a file I want only via FTP, and I chide them and they fix it ;-) -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness

2 1

Weekly Routing Table Report
by Routing Analysis Role Account 24 Apr '09

24 Apr '09

This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. Daily listings are sent to bgp-stats(a)lists.apnic.net For historical data, please see http://thyme.apnic.net. If you have any comments please contact Philip Smith <pfs(a)cisco.com>. Routing Table Report 04:00 +10GMT Sat 25 Apr, 2009 Report Website: http://thyme.apnic.net Detailed Analysis: http://thyme.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 286265 Prefixes after maximum aggregation: 135384 Deaggregation factor: 2.11 Unique aggregates announced to Internet: 141034 Total ASes present in the Internet Routing Table: 31102 Prefixes per ASN: 9.20 Origin-only ASes present in the Internet Routing Table: 27064 Origin ASes announcing only one prefix: 13174 Transit ASes present in the Internet Routing Table: 4038 Transit-only ASes present in the Internet Routing Table: 94 Average AS path length visible in the Internet Routing Table: 3.6 Max AS path length visible: 33 Max AS path prepend of ASN (43683) 31 Prefixes from unregistered ASNs in the Routing Table: 456 Unregistered ASNs in the Routing Table: 152 Number of 32-bit ASNs allocated by the RIRs: 141 Prefixes from 32-bit ASNs in the Routing Table: 25 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 208 Number of addresses announced to Internet: 2035527744 Equivalent to 121 /8s, 83 /16s and 176 /24s Percentage of available address space announced: 54.9 Percentage of allocated address space announced: 64.2 Percentage of available address space allocated: 85.5 Percentage of address space in use by end-sites: 76.5 Total number of prefixes smaller than registry allocations: 141104 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 66477 Total APNIC prefixes after maximum aggregation: 23664 APNIC Deaggregation factor: 2.81 Prefixes being announced from the APNIC address blocks: 63236 Unique aggregates announced from the APNIC address blocks: 28895 APNIC Region origin ASes present in the Internet Routing Table: 3607 APNIC Prefixes per ASN: 17.53 APNIC Region origin ASes announcing only one prefix: 974 APNIC Region transit ASes present in the Internet Routing Table: 548 Average APNIC Region AS path length visible: 3.5 Max APNIC Region AS path length visible: 18 Number of APNIC addresses announced to Internet: 411598112 Equivalent to 24 /8s, 136 /16s and 125 /24s Percentage of available APNIC address space announced: 81.8 APNIC AS Blocks 4608-4864, 7467-7722, 9216-10239, 17408-18431 (pre-ERX allocations) 23552-24575, 37888-38911, 45056-46079 APNIC Address Blocks 58/8, 59/8, 60/8, 61/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, 202/8, 203/8, 210/8, 211/8, 218/8, 219/8, 220/8, 221/8, 222/8, ARIN Region Analysis Summary ---------------------------- Prefixes being announced by ARIN Region ASes: 124769 Total ARIN prefixes after maximum aggregation: 65935 ARIN Deaggregation factor: 1.89 Prefixes being announced from the ARIN address blocks: 93936 Unique aggregates announced from the ARIN address blocks: 36650 ARIN Region origin ASes present in the Internet Routing Table: 12944 ARIN Prefixes per ASN: 7.26 ARIN Region origin ASes announcing only one prefix: 4998 ARIN Region transit ASes present in the Internet Routing Table: 1253 Average ARIN Region AS path length visible: 3.3 Max ARIN Region AS path length visible: 24 Number of ARIN addresses announced to Internet: 427360000 Equivalent to 25 /8s, 120 /16s and 255 /24s Percentage of available ARIN address space announced: 82.2 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 ARIN Address Blocks 24/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, 108/8, 173/8, 174/8, 184/8, 199/8, 204/8, 205/8, 206/8, 207/8, 208/8, 209/8, 216/8, RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 65947 Total RIPE prefixes after maximum aggregation: 38185 RIPE Deaggregation factor: 1.73 Prefixes being announced from the RIPE address blocks: 60269 Unique aggregates announced from the RIPE address blocks: 40136 RIPE Region origin ASes present in the Internet Routing Table: 12930 RIPE Prefixes per ASN: 4.66 RIPE Region origin ASes announcing only one prefix: 6763 RIPE Region transit ASes present in the Internet Routing Table: 1952 Average RIPE Region AS path length visible: 4.0 Max RIPE Region AS path length visible: 33 Number of RIPE addresses announced to Internet: 393057312 Equivalent to 23 /8s, 109 /16s and 148 /24s Percentage of available RIPE address space announced: 83.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 RIPE Address Blocks 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, 178/8, 193/8, 194/8, 195/8, 212/8, 213/8, 217/8, LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 23764 Total LACNIC prefixes after maximum aggregation: 5853 LACNIC Deaggregation factor: 4.06 Prefixes being announced from the LACNIC address blocks: 21917 Unique aggregates announced from the LACNIC address blocks: 12078 LACNIC Region origin ASes present in the Internet Routing Table: 1095 LACNIC Prefixes per ASN: 20.02 LACNIC Region origin ASes announcing only one prefix: 350 LACNIC Region transit ASes present in the Internet Routing Table: 181 Average LACNIC Region AS path length visible: 4.1 Max LACNIC Region AS path length visible: 28 Number of LACNIC addresses announced to Internet: 62481664 Equivalent to 3 /8s, 185 /16s and 101 /24s Percentage of available LACNIC address space announced: 62.1 LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247 plus ERX transfers LACNIC Address Blocks 186/8, 187/8, 189/8, 190/8, 200/8, 201/8, AfriNIC Region Analysis Summary ------------------------------- Prefixes being announced by AfriNIC Region ASes: 4885 Total AfriNIC prefixes after maximum aggregation: 1406 AfriNIC Deaggregation factor: 3.47 Prefixes being announced from the AfriNIC address blocks: 4578 Unique aggregates announced from the AfriNIC address blocks: 1394 AfriNIC Region origin ASes present in the Internet Routing Table: 292 AfriNIC Prefixes per ASN: 15.68 AfriNIC Region origin ASes announcing only one prefix: 89 AfriNIC Region transit ASes present in the Internet Routing Table: 59 Average AfriNIC Region AS path length visible: 3.9 Max AfriNIC Region AS path length visible: 15 Number of AfriNIC addresses announced to Internet: 11293696 Equivalent to 0 /8s, 172 /16s and 84 /24s Percentage of available AfriNIC address space announced: 33.7 AfriNIC AS Blocks 36864-37887 & ERX transfers AfriNIC Address Blocks 41/8, 197/8, APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 4766 1694 6930 401 Korea Telecom (KIX) 17488 1553 124 98 Hathway IP Over Cable Interne 4755 1229 432 176 TATA Communications formerly 9583 1090 87 539 Sify Limited 4134 896 16580 371 CHINANET-BACKBONE 7545 788 168 107 TPG Internet Pty Ltd 18101 751 217 31 Reliance Infocom Ltd Internet 24560 682 228 174 Bharti Airtel Ltd. 9498 675 297 53 BHARTI BT INTERNET LTD. 9829 634 495 21 BSNL National Internet Backbo Complete listing at http://thyme.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 6389 4314 3669 346 bellsouth.net, inc. 209 2648 4151 624 Qwest 4323 1837 1051 375 Time Warner Telecom 1785 1752 717 139 PaeTec Communications, Inc. 20115 1616 1439 719 Charter Communications 7018 1479 5897 1015 AT&T WorldNet Services 6478 1368 305 454 AT&T Worldnet Services 2386 1255 681 905 AT&T Data Communications Serv 3356 1194 10980 454 Level 3 Communications, LLC 11492 1163 192 11 Cable One Complete listing at http://thyme.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8452 1248 188 7 TEDATA 30890 539 88 198 SC Kappa Invexim SRL 3292 452 1764 390 TDC Tele Danmark 12479 447 578 6 Uni2 Autonomous System 3301 343 1670 307 TeliaNet Sweden 3320 342 7080 293 Deutsche Telekom AG 3215 340 3025 108 France Telecom Transpac 8866 337 109 22 Bulgarian Telecommunication C 35805 324 24 4 United Telecom of Georgia 29049 319 26 3 AzerSat LLC. Complete listing at http://thyme.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 1450 2848 233 UniNet S.A. de C.V. 10620 889 198 97 TVCABLE BOGOTA 22047 615 302 14 VTR PUNTO NET S.A. 7303 521 270 74 Telecom Argentina Stet-France 11830 516 294 34 Instituto Costarricense de El 16814 461 31 10 NSS, S.A. 6471 442 96 31 ENTEL CHILE S.A. 11172 410 102 72 Servicios Alestra S.A de C.V 28573 405 536 26 NET Servicos de Comunicao S.A 7738 397 794 28 Telecomunicacoes da Bahia S.A Complete listing at http://thyme.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24863 855 78 35 LINKdotNET AS number 20858 297 34 4 This AS will be used to conne 3741 277 860 237 The Internet Solution 2018 243 215 143 Tertiary Education Network 6713 159 150 15 Itissalat Al-MAGHRIB 33783 151 10 8 EEPAD TISP TELECOM & INTERNET 29571 138 15 9 Ci Telecom Autonomous system 5536 123 8 9 Internet Egypt Network 5713 115 507 66 Telkom SA Ltd 33776 107 6 3 Starcomms Nigeria Limited Complete listing at http://thyme.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 6389 4314 3669 346 bellsouth.net, inc. 209 2648 4151 624 Qwest 4323 1837 1051 375 Time Warner Telecom 1785 1752 717 139 PaeTec Communications, Inc. 4766 1694 6930 401 Korea Telecom (KIX) 20115 1616 1439 719 Charter Communications 17488 1553 124 98 Hathway IP Over Cable Interne 7018 1479 5897 1015 AT&T WorldNet Services 8151 1450 2848 233 UniNet S.A. de C.V. 6478 1368 305 454 AT&T Worldnet Services Complete listing at http://thyme.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 209 2648 2024 Qwest 1785 1752 1613 PaeTec Communications, Inc. 4323 1837 1462 Time Warner Telecom 17488 1553 1455 Hathway IP Over Cable Interne 4766 1694 1293 Korea Telecom (KIX) 8452 1248 1241 TEDATA 8151 1450 1217 UniNet S.A. de C.V. 11492 1163 1152 Cable One 4755 1229 1053 TATA Communications formerly 18566 1059 1049 Covad Communications Complete listing at http://thyme.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 16927 UNALLOCATED 12.0.252.0/23 7018 AT&T WorldNet Servic 15132 UNALLOCATED 12.9.150.0/24 7018 AT&T WorldNet Servic 32567 UNALLOCATED 12.14.170.0/24 7018 AT&T WorldNet Servic 13746 UNALLOCATED 12.24.56.0/24 7018 AT&T WorldNet Servic 32567 UNALLOCATED 12.25.107.0/24 7018 AT&T WorldNet Servic 26973 UNALLOCATED 12.39.152.0/24 7018 AT&T WorldNet Servic 26973 UNALLOCATED 12.39.154.0/23 7018 AT&T WorldNet Servic 26973 UNALLOCATED 12.39.159.0/24 7018 AT&T WorldNet Servic 32326 UNALLOCATED 12.40.49.0/24 7018 AT&T WorldNet Servic 25639 UNALLOCATED 12.41.169.0/24 7018 AT&T WorldNet Servic Complete listing at http://thyme.apnic.net/current/data-badAS Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 24.75.116.0/22 10796 ServiceCo LLC - Road Runner 24.246.0.0/17 7018 AT&T WorldNet Services 24.246.128.0/18 7018 AT&T WorldNet Services 41.223.112.0/22 5713 Telkom SA Ltd 41.223.176.0/22 36981 >>UNKNOWN<< 41.223.188.0/24 22351 Intelsat 41.223.189.0/24 26452 Local Communications Networks 62.61.220.0/24 24974 Tachyon Europe BV - Wireless 62.61.221.0/24 24974 Tachyon Europe BV - Wireless 63.140.213.0/24 22555 Universal Talkware Corporatio Complete listing at http://thyme.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:10 /10:20 /11:58 /12:166 /13:335 /14:595 /15:1147 /16:10427 /17:4694 /18:8086 /19:17057 /20:20310 /21:20145 /22:25752 /23:25374 /24:149930 /25:726 /26:848 /27:350 /28:161 /29:37 /30:10 /31:0 /32:8 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 6389 2812 4314 bellsouth.net, inc. 4766 1391 1694 Korea Telecom (KIX) 209 1353 2648 Qwest 17488 1304 1553 Hathway IP Over Cable Interne 8452 1227 1248 TEDATA 1785 1158 1752 PaeTec Communications, Inc. 11492 1107 1163 Cable One 18566 1040 1059 Covad Communications 2386 954 1255 AT&T Data Communications Serv 4323 951 1837 Time Warner Telecom Complete listing at http://thyme.apnic.net/current/data/sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 4:13 8:200 12:2223 13:3 15:19 16:3 17:4 20:35 24:1076 32:50 38:523 40:97 41:2012 43:1 44:2 47:22 52:3 55:2 56:3 57:25 58:573 59:629 60:460 61:1114 62:1106 63:2034 64:3663 65:2394 66:3599 67:1514 68:719 69:2577 70:534 71:134 72:1652 73:2 74:1494 75:168 76:306 77:847 78:555 79:311 80:979 81:815 82:543 83:423 84:606 85:1059 86:394 87:635 88:357 89:1454 90:47 91:2161 92:350 93:1125 94:1189 95:1041 96:120 97:189 98:214 99:17 109:1 110:58 112:108 113:100 114:224 115:249 116:1159 117:515 118:293 119:668 120:143 121:704 122:1011 123:673 124:970 125:1311 128:224 129:231 130:127 131:417 132:73 133:9 134:185 135:214 136:242 137:151 138:149 139:79 140:424 141:107 142:376 143:335 144:357 145:45 146:372 147:154 148:519 149:236 150:181 151:198 152:151 153:138 154:2 155:271 156:169 157:298 158:126 159:304 160:282 161:133 162:274 163:149 164:482 165:537 166:267 167:357 168:687 169:163 170:472 171:38 172:10 173:271 174:186 178:1 186:8 187:76 188:9 189:333 190:2712 192:5797 193:4227 194:3309 195:2691 196:1055 198:3715 199:3321 200:5437 201:1347 202:7853 203:8163 204:3807 205:2150 206:2407 207:2806 208:3881 209:3390 210:2646 211:1100 212:1527 213:1713 214:71 215:30 216:4572 217:1260 218:361 219:420 220:1208 221:453 222:296 End of report

1 0

Re: Config Backup / Inventory
by Jon Wolberg 24 Apr '09

24 Apr '09

Check out HyperConf http://www.winagents.com/en/products/hyperconf/ It does multi-vendor device backups as well as a scripting function to blow out mass changes to devices. They are also pretty easy to work with to enable new devices if you want them. The licensing is somewhat reasonable. Jon Wolberg Operations Manager PowerVPS / Defender Hosting Defender Technologies Group, LLC. ----- Original Message ----- From: "Joshua Eyres" <joshua.eyres(a)gmail.com> To: nanog(a)nanog.org Sent: Friday, April 24, 2009 4:25:05 AM GMT -05:00 US/Canada Eastern Subject: Config Backup / Inventory Hi, I am looking for a bit of advice around configuration backup / inventory. We currently have a large multi-vendor network which is currently managed through two separate tools (rancid - http://www.shrubbery.net/rancid and ns4 - http://www.noodles.org.uk/ns4.html) Both tools do the job very well, but management have asked that we look for commercial alternatives that have a proper support organisation looking after them. IP Service Activator has been mentioned as something which can fit this role, but I haven't had any experience and I haven't heard a lot of good things about it. We are looking for a tool which is flexible that allows configuration backup to textual form for easy restoration as well as the ability to deploy scripted changes to the network quickly. Do people generally use free tools for network management or are there viable commercial alternatives? Thanks, Josh

1 0

Problems reaching tools.ietf.org?
by Jack Bates 24 Apr '09

24 Apr '09

Anyone seeing issues with reachability for tools.ietf.org in IPv6? v4 works fine for me, but oh, the timeouts. :( Tracing the route to tools.ietf.org (2001:1890:1112:1:214:22FF:FE1F:1E54) 1 bnet6-2.tunnel.tserv2.fmt.ipv6.he.net (2001:470:1F03:1031::1) 64 msec 64 msec 64 msec 2 1g-3-9.core1.fmt1.ipv6.he.net (2001:470:0:44::3) 76 msec 72 msec 76 msec 3 10gigabitethernet1-1.core1.pao1.he.net (2001:470:0:2E::2) 64 msec 64 msec 64 msec 4 10gigabitethernet2-4.core1.ash1.he.net (2001:470:0:35::2) 144 msec 140 msec 140 msec 5 ibr01-ve96.asbn01.occaid.net (2001:504:0:2:0:3:71:1) 140 msec 140 msec 140 msec 6 r1.flpnj.ipv6.att.net (2001:4830:E2:2B::2) 148 msec 148 msec 148 msec 7 2001:1890:61:9117::2 224 msec 228 msec 224 msec 8 2001:1890:61:9117::2 !H * *

3 3

Re: NAT64/NAT-PT update in IETF,was: Re: Important New Requirement for IPv4 Requests [re"impacting revenue"]
by Manish Karir 24 Apr '09

24 Apr '09

Would there be interest in trying to organize a day long mini-nanog with the ietf in March 2010? The regular nanog mtg is scheduled for Feb 22 2010 so this would have to be an extra meeting. and would require all sorts of help and interest from the ietf to put together. Perhaps the NANOG SC can try to figure out if there is sufficient interest in this and what this should consist of? -manish ------- > * From: Iljitsch van Beijnum > * Date: Thu Apr 23 10:37:12 2009 > > * List-archive: <http://mailman.nanog.org/mailman/nanog> > * List-help: <mailto:nanog-request@nanog.org?subject=help> > * List-id: North American Network Operators Group <nanog.nanog.org> > * List-post: <mailto:nanog@nanog.org> > * List-subscribe: ><http://mailman.nanog.org/mailman/listinfo/nanog>,<mailto:nanog-request@nanog.org?subject=subscribe> > * List-unsubscribe: ><http://mailman.nanog.org/mailman/listinfo/nanog>,<mailto:nanog-request@nanog.org?subject=unsubscribe> > >On 23 apr 2009, at 14:17, Adrian Chadd wrote: > > > Methinks its time a large cabal of network operators should represent > at IETF and make their opinions heard as a collective group. > That would be how change is brought about in a participative organisation, > no? :) > >Why don't you start by simpling stating what you want to have happen? > >So far I've seen a number of messages complaining about the IETF (btw, if you like complaining about the IETF, go to >the meetings, there is significant time set aside for that there) but not a single technical request, remark or >observation. > >The IETF works by rough consensus. That means if people disagree, nothing much happens. That is annoying. But a lot of >good work gets done when people agree, and a lot of the time good technical arguments help. > >Like I said, the IETF really wants input from operators. Why not start by giving some?

2 1