- NANOG - lists.nanog.org

Now Available: Whois-RWS Differences Documentation
by Mark Kosters 11 Jun '10

11 Jun '10

Hi FYI - this was posted a few minutes ago on arin-announce and may be of interest to NANOG as well. Regards, Mark ----- Forwarded message from Member Services <info(a)arin.net> ----- From: Member Services <info(a)arin.net> Date: Fri, 11 Jun 2010 16:30:40 -0400 To: "arin-announce(a)arin.net" <arin-announce(a)arin.net> Subject: [arin-announce] Now Available: Whois-RWS Differences Documentation ARIN is deploying an improved Whois service called Whois-RWS on 26 June 2010. When using the Whois-RWS you will notice some differences in behavior for certain queries and corresponding result sets on the NICNAME/WHOIS port 43 service. Detailed documentation on these differences is now available at: https://www.arin.net/resources/whoisrws/whois_diff.html ARIN's Directory Service for registration data has used the NICNAME/WHOIS protocol since its inception. The limitations of the NICNAME/WHOIS protocol are well known and documented in RFC3912. Whois-RWS was created as an alternative to the ARIN Whois and will provide much richer functionality and capability to the community. A demo of this service has been available since October 2009. The demonstration service is available at: http://whoisrws-demo.arin.net. ARIN continues to welcome community participation on the Whois-RWS mailing list, and we invite you to subscribe and share your thoughts and suggestions at: http://lists.arin.net/mailman/listinfo/arin-whoisrws More detailed information on these changes and other future features that may impact the community at ARIN is available at: https://www.arin.net/features/ Regards, Mark Kosters Chief Technical Officer American Registry for Internet Numbers (ARIN) ----- End forwarded message -----

1 0

Verizon OC12 outage in Dallas, TX
by Tim Connolly 11 Jun '10

11 Jun '10

I don't know whether this is bigger or smaller, but Savvis seems to suggest there are 11 other DS3's involved in an outage that took us out around 11am. Anyone else have details? Verizon supposedly dispatched a tech to the Bryan St. pop.

1 0

Weekly Routing Table Report
by Routing Analysis Role Account 11 Jun '10

11 Jun '10

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 12 Jun, 2010 Report Website: http://thyme.apnic.net Detailed Analysis: http://thyme.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 322325 Prefixes after maximum aggregation: 148837 Deaggregation factor: 2.17 Unique aggregates announced to Internet: 158178 Total ASes present in the Internet Routing Table: 34173 Prefixes per ASN: 9.43 Origin-only ASes present in the Internet Routing Table: 29656 Origin ASes announcing only one prefix: 14403 Transit ASes present in the Internet Routing Table: 4517 Transit-only ASes present in the Internet Routing Table: 102 Average AS path length visible in the Internet Routing Table: 3.6 Max AS path length visible: 25 Max AS path prepend of ASN (41664) 21 Prefixes from unregistered ASNs in the Routing Table: 308 Unregistered ASNs in the Routing Table: 114 Number of 32-bit ASNs allocated by the RIRs: 618 Prefixes from 32-bit ASNs in the Routing Table: 704 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 153 Number of addresses announced to Internet: 2226107872 Equivalent to 132 /8s, 175 /16s and 181 /24s Percentage of available address space announced: 60.1 Percentage of allocated address space announced: 64.7 Percentage of available address space allocated: 92.8 Percentage of address space in use by end-sites: 83.2 Total number of prefixes smaller than registry allocations: 154163 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 77175 Total APNIC prefixes after maximum aggregation: 26893 APNIC Deaggregation factor: 2.87 Prefixes being announced from the APNIC address blocks: 74194 Unique aggregates announced from the APNIC address blocks: 33008 APNIC Region origin ASes present in the Internet Routing Table: 4076 APNIC Prefixes per ASN: 18.20 APNIC Region origin ASes announcing only one prefix: 1121 APNIC Region transit ASes present in the Internet Routing Table: 632 Average APNIC Region AS path length visible: 3.6 Max APNIC Region AS path length visible: 18 Number of APNIC addresses announced to Internet: 521993248 Equivalent to 31 /8s, 28 /16s and 252 /24s Percentage of available APNIC address space announced: 77.8 APNIC AS Blocks 4608-4864, 7467-7722, 9216-10239, 17408-18431 (pre-ERX allocations) 23552-24575, 37888-38911, 45056-46079 55296-56319, 131072-132095 APNIC Address Blocks 1/8, 14/8, 27/8, 43/8, 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, 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: 134088 Total ARIN prefixes after maximum aggregation: 69138 ARIN Deaggregation factor: 1.94 Prefixes being announced from the ARIN address blocks: 106811 Unique aggregates announced from the ARIN address blocks: 41644 ARIN Region origin ASes present in the Internet Routing Table: 13733 ARIN Prefixes per ASN: 7.78 ARIN Region origin ASes announcing only one prefix: 5271 ARIN Region transit ASes present in the Internet Routing Table: 1344 Average ARIN Region AS path length visible: 3.4 Max ARIN Region AS path length visible: 22 Number of ARIN addresses announced to Internet: 727992352 Equivalent to 43 /8s, 100 /16s and 72 /24s Percentage of available ARIN address space announced: 62.0 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, 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, 54/8, 55/8, 56/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, 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: 74215 Total RIPE prefixes after maximum aggregation: 43198 RIPE Deaggregation factor: 1.72 Prefixes being announced from the RIPE address blocks: 67232 Unique aggregates announced from the RIPE address blocks: 44421 RIPE Region origin ASes present in the Internet Routing Table: 14524 RIPE Prefixes per ASN: 4.63 RIPE Region origin ASes announcing only one prefix: 7499 RIPE Region transit ASes present in the Internet Routing Table: 2182 Average RIPE Region AS path length visible: 3.9 Max RIPE Region AS path length visible: 25 Number of RIPE addresses announced to Internet: 430186912 Equivalent to 25 /8s, 164 /16s and 33 /24s Percentage of available RIPE address space announced: 75.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, 196608-197631 RIPE Address Blocks 2/8, 25/8, 31/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, 193/8, 194/8, 195/8, 212/8, 213/8, 217/8, LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 28644 Total LACNIC prefixes after maximum aggregation: 6829 LACNIC Deaggregation factor: 4.19 Prefixes being announced from the LACNIC address blocks: 27053 Unique aggregates announced from the LACNIC address blocks: 14082 LACNIC Region origin ASes present in the Internet Routing Table: 1299 LACNIC Prefixes per ASN: 20.83 LACNIC Region origin ASes announcing only one prefix: 404 LACNIC Region transit ASes present in the Internet Routing Table: 228 Average LACNIC Region AS path length visible: 4.0 Max LACNIC Region AS path length visible: 24 Number of LACNIC addresses announced to Internet: 73906944 Equivalent to 4 /8s, 103 /16s and 187 /24s Percentage of available LACNIC address space announced: 55.1 LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 262144-263167 plus ERX transfers LACNIC Address Blocks 177/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: 7281 Total AfriNIC prefixes after maximum aggregation: 1809 AfriNIC Deaggregation factor: 4.02 Prefixes being announced from the AfriNIC address blocks: 5613 Unique aggregates announced from the AfriNIC address blocks: 1718 AfriNIC Region origin ASes present in the Internet Routing Table: 368 AfriNIC Prefixes per ASN: 15.25 AfriNIC Region origin ASes announcing only one prefix: 108 AfriNIC Region transit ASes present in the Internet Routing Table: 86 Average AfriNIC Region AS path length visible: 3.7 Max AfriNIC Region AS path length visible: 15 Number of AfriNIC addresses announced to Internet: 18883072 Equivalent to 1 /8s, 32 /16s and 34 /24s Percentage of available AfriNIC address space announced: 56.3 AfriNIC AS Blocks 36864-37887, 327680-328703 & 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 1849 8422 484 Korea Telecom (KIX) 17488 1316 140 125 Hathway IP Over Cable Interne 4755 1309 293 153 TATA Communications formerly 7545 1307 232 105 TPG Internet Pty Ltd 17974 1097 282 21 PT TELEKOMUNIKASI INDONESIA 9583 994 73 490 Sify Limited 24560 916 306 169 Bharti Airtel Ltd., Telemedia 4134 877 21295 409 CHINANET-BACKBONE 4808 842 1573 217 CNCGROUP IP network: China169 9829 793 680 39 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 3913 3733 287 bellsouth.net, inc. 4323 3362 1113 394 Time Warner Telecom 1785 1782 699 131 PaeTec Communications, Inc. 20115 1552 1512 659 Charter Communications 7018 1512 5735 962 AT&T WorldNet Services 2386 1287 569 909 AT&T Data Communications Serv 6478 1269 259 92 AT&T Worldnet Services 3356 1182 10890 406 Level 3 Communications, LLC 22773 1162 2605 65 Cox Communications, Inc. 11492 1151 207 68 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 35805 634 56 6 United Telecom of Georgia 3292 453 2026 394 TDC Tele Danmark 30890 442 111 205 Evolva Telecom 702 412 1869 328 UUNET - Commercial IP service 8551 402 355 38 Bezeq International 8866 400 117 18 Bulgarian Telecommunication C 3301 370 1414 325 TeliaNet Sweden 3320 370 7073 321 Deutsche Telekom AG 34984 358 88 184 BILISIM TELEKOM 12479 335 576 5 Uni2 Autonomous System 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 1521 2965 244 UniNet S.A. de C.V. 10620 1059 237 152 TVCABLE BOGOTA 28573 901 745 81 NET Servicos de Comunicao S.A 7303 724 374 132 Telecom Argentina Stet-France 6503 642 173 209 AVANTEL, S.A. 22047 545 310 15 VTR PUNTO NET S.A. 3816 480 208 76 Empresa Nacional de Telecomun 7738 477 922 30 Telecomunicacoes da Bahia S.A 14420 463 32 67 ANDINATEL S.A. 14117 456 30 13 Telefonica del Sur 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 8452 1151 445 10 TEDATA 24863 716 147 39 LINKdotNET AS number 36992 642 278 186 Etisalat MISR 3741 269 852 230 The Internet Solution 33776 219 12 11 Starcomms Nigeria Limited 2018 211 244 61 Tertiary Education Network 6713 195 186 16 Itissalat Al-MAGHRIB 24835 183 78 10 RAYA Telecom - Egypt 29571 175 19 10 Ci Telecom Autonomous system 29975 133 506 14 Vodacom 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 3913 3733 287 bellsouth.net, inc. 4323 3362 1113 394 Time Warner Telecom 4766 1849 8422 484 Korea Telecom (KIX) 1785 1782 699 131 PaeTec Communications, Inc. 20115 1552 1512 659 Charter Communications 8151 1521 2965 244 UniNet S.A. de C.V. 7018 1512 5735 962 AT&T WorldNet Services 17488 1316 140 125 Hathway IP Over Cable Interne 4755 1309 293 153 TATA Communications formerly 7545 1307 232 105 TPG Internet Pty Ltd Complete listing at http://thyme.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 4323 3362 2968 Time Warner Telecom 1785 1782 1651 PaeTec Communications, Inc. 4766 1849 1365 Korea Telecom (KIX) 8151 1521 1277 UniNet S.A. de C.V. 7545 1307 1202 TPG Internet Pty Ltd 17488 1316 1191 Hathway IP Over Cable Interne 6478 1269 1177 AT&T Worldnet Services 4755 1309 1156 TATA Communications formerly 8452 1151 1141 TEDATA 22773 1162 1097 Cox Communications, Inc. 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.155.0/24 7018 AT&T WorldNet Servic 26973 UNALLOCATED 12.39.159.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 31.0.0.0/16 12654 RIPE NCC RIS Project 31.1.0.0/21 12654 RIPE NCC RIS Project 31.1.24.0/24 12654 RIPE NCC RIS Project 41.76.160.0/21 37063 Roke Investments Internationa 41.222.79.0/24 36938 >>UNKNOWN<< 41.223.92.0/22 36936 >>UNKNOWN<< 41.223.188.0/24 22351 Intelsat 41.223.189.0/24 6453 Teleglobe Inc. 41.223.196.0/24 36990 Alkan Telecom Ltd 41.223.197.0/24 36990 Alkan Telecom Ltd 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:25 /11:67 /12:193 /13:403 /14:699 /15:1279 /16:11105 /17:5301 /18:9023 /19:18326 /20:22576 /21:22617 /22:29601 /23:29231 /24:168924 /25:954 /26:1226 /27:617 /28:104 /29:10 /30:7 /31:0 /32:8 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 6389 2508 3913 bellsouth.net, inc. 4323 1852 3362 Time Warner Telecom 4766 1480 1849 Korea Telecom (KIX) 1785 1246 1782 PaeTec Communications, Inc. 11492 1065 1151 Cable One 17488 1063 1316 Hathway IP Over Cable Interne 8452 1045 1151 TEDATA 18566 1040 1059 Covad Communications 10620 975 1059 TVCABLE BOGOTA 7018 910 1512 AT&T WorldNet Services Complete listing at http://thyme.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:2 4:13 8:284 12:2007 13:11 14:1 15:23 16:3 17:8 20:21 24:1422 27:113 31:1 32:49 33:12 38:680 40:98 41:2432 44:3 47:26 52:8 55:9 56:2 57:25 58:739 59:504 60:458 61:1074 62:1070 63:1974 64:3617 65:2339 66:4249 67:1818 68:1107 69:2873 70:718 71:236 72:1832 73:2 74:2109 75:252 76:312 77:898 78:629 79:426 80:982 81:797 82:487 83:431 84:702 85:1040 86:459 87:694 88:334 89:1546 90:92 91:2800 92:508 93:1107 94:1416 95:610 96:281 97:323 98:562 99:28 108:32 109:526 110:427 111:517 112:261 113:296 114:418 115:549 116:1048 117:650 118:470 119:934 120:147 121:737 122:1450 123:926 124:1108 125:1313 128:210 129:217 130:193 131:555 132:250 133:17 134:195 135:45 136:229 137:168 138:257 139:104 140:510 141:137 142:348 143:388 144:468 145:50 146:440 147:166 148:648 149:299 150:152 151:166 152:285 153:168 154:2 155:328 156:158 157:324 158:107 159:376 160:316 161:179 162:254 163:171 164:408 165:331 166:467 167:401 168:786 169:165 170:707 171:57 172:2 173:818 174:607 175:90 176:1 178:165 180:488 182:109 183:224 184:58 186:466 187:343 188:1295 189:795 190:3770 192:5752 193:4707 194:3355 195:2757 196:1204 198:3585 199:3434 200:5354 201:1548 202:7978 203:8254 204:4064 205:2328 206:2515 207:3051 208:3889 209:3401 210:2494 211:1262 212:1750 213:1687 214:671 215:69 216:4659 217:1523 218:486 219:378 220:1136 221:398 222:304 223:1 End of report

1 0

huawei-nsp
by Jared Mauch 10 Jun '10

10 Jun '10

I've created a new list on puck, huawei-nsp You can subscribe here: https://puck.nether.net/mailman/listinfo/huawei-nsp - Jared -- Jared Mauch | pgp key available via finger from jared(a)puck.nether.net clue++; | http://puck.nether.net/~jared/ My statements are only mine.

1 0

Re: Nato warns of strike against cyber attackers
by dlr＠bungi.com 10 Jun '10

10 Jun '10

[In the message entitled "Re: Nato warns of strike against cyber attackers" on Jun 8, 16:03, "J. Oquendo" writes:] > > All humor aside, I'm curious to know what can anyone truly do at the end > of the day if say a botnet was used to instigate a situation. Surely > someone would have to say something to the tune of "better now than > never" to implement BCP filtering on a large scale. Knobs, Levers, Dials > and Switches: Now and Then (please sir, may I have some more ?) is 7 > years old yet I wonder in practice, how many networks have 38/84 > filtering. I'm wondering why it hasn't been implemented off the shelf in > some of the newer equipment. This is not to say "huge backbones" should > have it, but think about it, if smaller networks implemented it from the > rip, the overheard wouldn't hurt that many of the bigger guys. On the > contrary, my theory is it would save them headaches in the long run... > Guess that's a pragmatic approach. Better that than an immediate > pessimistic one. > It's really way, way past time for us to actually deal with compromised computers on our networks. Abuse desks need to have the power to filter customers immediately on notification of activity. We need to have tools to help us identify compromised customers. We need to have policies that actually work to help notify the customers when they are compromised. None of this needs to be done for free. There needs to be a "security fee" charged _all_ customers, which would fund the abuse desk. With more than 100,000,000 compromised computers out there, it's really time for us to step up to the plate, and make this happen. --

20 36

Best Practices checklists
by Michael Dillon 10 Jun '10

10 Jun '10

I expect that the collected members of this list could do a good job of defining some network security practices checklists. Now that NANOG has been spun out as an independent entity, I would hate to see it become just another conference organizer. In the recent past many professions have learned how valuable a simple checklist is in preventing errors and ensuring that work adheres to a certain standard. So I am suggesting that NANOG take on the task of compiling and publishing checklists for various areas of network operations. We could have a NANOG wiki where people can publish, and work over, suggestions for checklist topics and content. Then at the conferences, a BOF-style meeting could hash out the official published versions. We could have an interesting debate on whether or not this would make a difference and whether or not NANOG should take on this role. But I hope that we are now at a point where we see that network sloppiness and insecurity are becoming such major issues that action is needed. Let's act first, and evaluate the usefulness of the work, later. --Michael Dillon

4 3

Google Issues?
by Thomas Magill 10 Jun '10

10 Jun '10

Is anyone seeing warnings today from Google that they suspect that searches are coming from an automated source and asking to complete some captcha-type authentication to complete a search? We have had a couple of reports on this and I want to make sure it isn't a google issue. I know this isn't really an operator issue but there are enough knowledgeable people here that I thought I would ask. Thomas Magill Network Engineer Office: (858) 909-3777 Cell: (858) 869-9685 mailto:tmagill@providecommerce.com <mailto:tmagill@providecommerce.com> provide-commerce 4840 Eastgate Mall San Diego, CA 92121 ProFlowers <http://www.proflowers.com/> | redENVELOPE <http://www.redenvelope.com/> | Cherry Moon Farms <http://www.cherrymoonfarms.com/> | Shari's Berries <http://www.berries.com/>

2 2

Re: Nato warns of strike against cyber attackers
by dlr＠bungi.com 10 Jun '10

10 Jun '10

[In the message entitled "Re: Nato warns of strike against cyber attackers" on Jun 8, 13:33, Owen DeLong writes:] > > I realize your fond of punishing all of us to subsidize the ignorant, = > but I would rather see those with compromised machines pay the bill for = > letting their machines get compromised than have to subsidize their = > ignorant or worse behavior. > I'm fond of getting the issues addressed by getting the ISPs to be involved with the problem. If that means users get charged "clean up" fees instead of a "security" fee, that's fine. ISPs remain in the unique position of being able to identify the customer, the machine, and to verify the traffic. It can be done. --

18 65

SCO UNIX Errors
by jacob miller 10 Jun '10

10 Jun '10

Hi, Am getting the following error from my SCO UNIX box. Any idea as to what they mean. proto: 0, age: 1274191185 locks: inits: sockaddrs: <DST,GATEWAY> 172.16.3.12 172.16.1.254 route: got message of size 120 RTM_LOSING: Kernel Suspects Partitioning: len 120, pid: 0, seq 0, errno 0, flags :<UP,GATEWAY,HOST,DONE,PMTU,PMTUMOD> proto: 0, age: 1274191200 locks: inits: sockaddrs: <DST,GATEWAY> 172.16.3.12 172.16.1.254 route: got message of size 120 RTM_LOSING: Kernel Suspects Partitioning: len 120, pid: 0, seq 0, errno 0, flags :<UP,GATEWAY,HOST,DONE,PMTU> proto: 0, age: 1274191204 locks: inits: sockaddrs: <DST,GATEWAY> 172.16.10.3 172.16.1.254 route: got message of size 120 RTM_LOSING: Kernel Suspects Partitioning: len 120, pid: 0, seq 0, errno 0, flags :<UP,GATEWAY,HOST,DONE,PMTU,PMTUMOD> proto: 0, age: 1274191206 locks: inits: sockaddrs: <DST,GATEWAY> 172.16.3.12 172.16.1.254 route: got message of size 120 RTM_LOSING: Kernel Suspects Partitioning: len 120, pid: 0, seq 0, errno 0, flags:<UP,GATEWAY,HOST,DONE,PMTU,PMTUMOD> proto: 0, age: 1274191249 locks: inits: sockaddrs: <DST,GATEWAY> 172.16.3.12 172.16.1.254 route: got message of size 120 RTM_LOSING: Kernel Suspects Partitioning: len 120, pid: 0, seq 0, errno 0, flags:<UP,GATEWAY,HOST,DONE,PMTU> proto: 0, age: 1274191250 locks: inits: sockaddrs: <DST,GATEWAY> 172.16.10.3 172.16.1.254 route: got message of size 120 RTM_LOSING: Kernel Suspects Partitioning: len 120, pid: 0, seq 0, errno 0, flags:<UP,GATEWAY,HOST,DONE,PMTU,PMTUMOD> proto: 0, age: 1274191264 locks: inits: sockaddrs: <DST,GATEWAY> 172.16.3.12 172.16.1.254 route: got message of size 120 RTM_LOSING: Kernel Suspects Partitioning: len 120, pid: 0, seq 0, errno 0, flags:<UP,GATEWAY,HOST,DONE,PMTU> proto: 0, age: 1274191268 locks: inits: sockaddrs: <DST,GATEWAY> 172.16.10.3 172.16.1.254 route: got message of size 120 RTM_LOSING: Kernel Suspects Partitioning: len 120, pid: 0, seq 0, errno 0, flags:<UP,GATEWAY,HOST,DONE,PMTU,PMTUMOD> proto: 0, age: 1274191270 locks: inits: sockaddrs: <DST,GATEWAY> 172.16.3.12 172.16.1.254 route: got message of size 120 RTM_LOSING: Kernel Suspects Partitioning: len 120, pid: 0, seq 0, errno 0, flags:<UP,GATEWAY,HOST,DONE,PMTU> proto: 0, age: 1274191297 locks: inits: sockaddrs: <DST,GATEWAY> 172.16.10.3 172.16.1.254 Regards, Jacob

6 7

Broadband Internet Technical Advisory Group
by Marshall Eubanks 10 Jun '10

10 Jun '10

This just popped up - BITAG, the Broadband Internet Technical Advisory Group, which apparently has some Google backing. While it does not impact router configuration today, it sure does sound like they want to in the future. http://www.prnewswire.com/news-releases/initial-plans-for-broadband-interne… http://googlepublicpolicy.blogspot.com/2010/06/broadband-internet-technical… "For some time now, we’ve been advocating for the formation of a group of technical experts to put forward their best thinking on how to manage broadband networks in ways that still preserve and promote an open Internet. We’ve worked closely with Verizon and others in the Internet sector to further develop the concept, and we’re excited by today’s announcement that the Broadband Internet Technical Advisory Group , or BITAG, has begun the process of formally launching." Regards Marshall

2 1