March 2002 - Test - lists.nanog.org

SNMP Advisory Updates
by CERT(R) Coordination Center 07 Mar '02

07 Mar '02

-----BEGIN PGP SIGNED MESSAGE----- Hello Folks, I've made a large number of vendor updates to the SNMP Advisory (http://www.cert.org/advisories/CA-2002-03.html) Due to the sheer number of vendors included in this Advisory, you may wish to take a look at your convenience. Thanks, Ian Ian A. Finlay CERT (R) Coordination Center Software Engineering Institute Carnegie Mellon University Pittsburgh, PA USA 15213-3890 Feb 12, 2002: Initial release Feb 12, 2002: Corrected vendor appendix formatting issues Feb 12, 2002: Added vendor statement for Inktomi Feb 12, 2002: Fixed formatting problem in "Disable stack execution" section Feb 12, 2002: Updated vendor statement for Juniper Feb 12, 2002: Fixed broken link in Juniper statement Feb 12, 2002: Updated Public Thanks section Feb 12, 2002: Updated Covalent statement Feb 12, 2002: Updated SNMP Research statement Feb 12, 2002: Updated CVE and Comtek services links Feb 13, 2002: Updated Cisco, Enterasys, FreeBSD, HP, Microsoft, Sun, and Tandberg statements, removed Tivoli statement Feb 14, 2002: Added vendor statement for Aprisma Feb 14, 2002: Added vendor statements for MG-Soft and NetScreen Feb 14, 2002: Added vendor statement for iTouch Communications Feb 14, 2002: Added vendor statement for F5 Networks Feb 14, 2002: Added vendor statement for Sierra Wireless Feb 15, 2002: Added vendor statement for MICROMUSE Feb 15, 2002: Updated HP statement Feb 16, 2002: Updated Nortel Networks statement Feb 16, 2002: Added vendor statement for Foundry Networks Feb 18, 2002: Added vendor statement for Tivoli Feb 18, 2002: Added vendor statement for Radware Feb 18, 2002: Updated Nortel Networks statement Feb 19, 2002: Updated Nortel Networks statement Feb 19, 2002: Updated F5 Networks statement Feb 19, 2002: Updated Compaq statement Feb 19, 2002: Updated IBM statement Feb 19, 2002: Added vendor statement for Dell Feb 19, 2002: Fixed bad link in Enterasys statement Feb 19, 2002: Updated IBM statement Feb 19, 2002: Added vendor statement for BMC Software Feb 20, 2002: Added vendor statement for Wind River Systems Feb 20, 2002: Added vendor statement for Concord Communications Feb 20, 2002: Added vendor statement for CommWorks Corporation (a 3Com company) Feb 20, 2002: Added vendor statement for Lexmark International Feb 20, 2002: Added vendor statement for Check Point Software Technologies Inc. Feb 20, 2002: Added vendor statement for Alcatel Feb 21, 2002: Added vendor statement for Avici Systems Inc. Feb 21, 2002: Added vendor statement for NuDesign Team Inc. Feb 21, 2002: Added vendor statement for ADTRAN, Inc. Feb 21, 2002: Updated NetScreen vendor statement Feb 21, 2002: Added vendor statement for TMP Consultoria S/C Feb 21, 2002: Added vendor statement for Xerox Feb 21, 2002: Updated Inktomi vendor statement Feb 21, 2002: Added vendor statement for nCipher Corp. Feb 21, 2002: Updated Lucent vendor statement Feb 21, 2002: Added vendor statement for Spider Software Feb 21, 2002: Added vendor statement for Riverstone Networks Feb 21, 2002: Added vendor statement for Standard Networks, Inc. Feb 21, 2002: Added vendor statement for Openwave Systems Inc. Feb 21, 2002: Added vendor statement for General DataComm Feb 22, 2002: Added vendor statement for NETWORK HARMONi, Inc. Feb 22, 2002: Updated HP vendor statement Feb 22, 2002: Updated Nortel Networks statement Feb 25, 2002: Added vendor statement for American Power Conversion Feb 25, 2002: Added vendor statement for Cambridge Broadband Ltd. Feb 25, 2002: Added vendor statement for Corsaire Limited Feb 25, 2002: Added vendor statement for SonicWALL, Inc. Feb 26, 2002: Added vendor statement for Perle Systems Feb 26, 2002: Added vendor statement for Sonus Networks Feb 26, 2002: Added vendor statement for Optical Access Feb 26, 2002: Added vendor statement for INRANGE Technologies Feb 26, 2002: Updated vendor statement for Redback Networks, Inc. Feb 26, 2002: Removed "Disable stack execution" section from Solutions Feb 26, 2002: Added vendor statement for BinTec Communications AG Feb 26, 2002: Updated vendor statement for IBM Feb 27, 2002: Updated HP vendor statement Feb 27, 2002: Added vendor statement for World Wide Packets Feb 27, 2002: Added vendor statement for Dart Communications Feb 27, 2002: Added vendor statement for Quallaby Corporation Feb 27, 2002: Updated iTouch Communications vendor statement Feb 27, 2002: Added vendor statement for CipherTrust, Inc. Feb 27, 2002: Added vendor statement for Ipswitch, Inc. Feb 27, 2002: Added vendor statement for D-Link Systems, Inc. Mar 01, 2002: Added vendor statement for iPlanet Mar 01, 2002: Updated vendor statement for Novell Mar 01, 2002: Updated vendor statement for nCipher Corp. Mar 01, 2002: Added vendor statement for Extreme Networks Mar 04, 2002: Added vendor statement for NetSilicon Mar 04, 2002: Added vendor statement for SecureWorks, Inc. Mar 04, 2002: Added vendor statement for Efficient Networks, Inc. Mar 04, 2002: Updated vendor statement for Novell Mar 04, 2002: Added vendor statement for Monfox, LLC Mar 05, 2002: Added vendor statement for Paradyne Mar 05, 2002: Added vendor statement for Trend Micro Mar 05, 2002: Updated vendor statement for Dartware, LLC Mar 05, 2002: Added vendor statement for Quick Eagle Networks Mar 05, 2002: Added vendor statement for Conectiva Mar 05, 2002: Added vendor statement for Asante Technologies, Inc. Mar 05, 2002: Added vendor statement for SolarWinds.Net, Inc. Mar 06, 2002: Updated vendor statement for Aprisma Mar 06, 2002: Updated vendor statement for Ipswitch, Inc. Mar 06, 2002: Added vendor statement for CSCare, Inc. Mar 06, 2002: Updated vendor statement for iTouch Communications Mar 06, 2002: Added vendor statement for Uptime Devices, Inc. Mar 06, 2002: Added vendor statement for Larscom Incorporated Mar 06, 2002: Added vendor statement for InterNiche Technologies, Inc. Mar 07, 2002: Added vendor statement for Network Appliance Mar 07, 2002: Updated vendor statement for Avaya Mar 07, 2002: Updated vendor statement for Xerox Mar 07, 2002: Added vendor statement for Sniffer Technologies Mar 07, 2002: Added vendor statement for Powerware Corporation Mar 07, 2002: Added vendor statement for Carrier Access Mar 07, 2002: Added vendor statement for net.com Mar 07, 2002: Added vendor statement for Oracle Corporation -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use Charset: noconv iQCVAwUBPIfb/KCVPMXQI2HJAQGVcgQApnmr2rPkaXwxEK1KoikbQSpjlVngHNBi R4EkoyvrpWXtlNlGQWX8zLAvEWZf4mS12r8Ai/zyYLw3mIhzs48SM6d5+f07aTrh afKwbsdAocdg3lx8T5F1toBlM4GphYFaQDDYPMh6EzDko3aIbrXaEmpcOCM8CJ2F aofaejrBLb0= =m5if -----END PGP SIGNATURE-----

1 0

Contact for AS4015
by Eric Whitehill 07 Mar '02

07 Mar '02

Hey everyone: Sorry to ask this, but if someone can please contact me from AS4015? The contacts listed at Arin are no longer any good, and anyone we have talked to at Qwest doesn't seem to know anyone we can talk to about an issue we are having. Thanks, -Eric

1 0

ICANN - The Case for Replacing its Management
by Patrick 07 Mar '02

07 Mar '02

Although I reserve comment on some of the specific recommendation offered by the author, this is an otherwise extremely timely, well-articulated view into the history of ICANN to present written by the former Chair of the General Assembly. http://www.icannworld.org P.S. Yes Virgina, the resultant outcome of this mess could actually affect how you configure your router(s) some day.... /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ Patrick Greenwell Asking the wrong questions is the leading cause of wrong answers \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/

18 27

Re: Telco's write best practices for packet switching networks
by Steven M. Bellovin 07 Mar '02

07 Mar '02

In message <gu9ofi1rcwe.fsf(a)rampart.argfrp.us.uu.net>, Eric Brandwine writes: > >Firewalls are good things for general purpose networks. When you've >got a bunch of clueless employees, all using Windows shares, NFS, and >all sorts of nasty protocols, a firewall is best practice. Rather >than educate every single one of them as to the security implications >of their actions, just insulate them, and do what you can behind the >firewall. > >When you've got a deployed server, run by clueful people, dedicated to >a single task, firewalls are not the way to go. You've got a DNS >server. What are you going to do with a firewall? Permit tcp/53 and >udp/53 from the appropriate net blocks. Where's the protection? Turn >off unneeded services, chose a resilient and flame tested daemon, and >watch the patchlist for it. Precisely. You *may* need a packet filter to block things like SNMP (to name a recent case in point), but a general-purpose firewall is generally the wrong solution for appliance computers. --Steve Bellovin, http://www.research.att.com/~smb Full text of "Firewalls" book now at http://www.wilyhacker.com

6 7

Re: Equinix Exchange Point
by Reggie Forster 07 Mar '02

07 Mar '02

XO is... At 09:14 AM 3/7/02, Guy.Ram(a)usa.telekom.de wrote: >Quick poll to see who's at or planning to be at the Equinix Asburn exchange >point. > >thanks, > >-guy

1 0

Re: Equinix Exchange Point
by renster 07 Mar '02

07 Mar '02

SBC is. Also at Dallas & San Jose now. Soon to be at Los Angeles & Chicago. http://www.sbcbackbone.net/peering/ -ren At 09:14 AM 3/7/2002 -0500, Guy.Ram(a)usa.telekom.de wrote: >Quick poll to see who's at or planning to be at the Equinix Asburn exchange >point. > >thanks, > >-guy

1 0

RE: Equinix Exchange Point
by Allison.Feese＠Broadwing.com 07 Mar '02

07 Mar '02

Broadwing will be there sometime between April and May. Allison -----Original Message----- From: Guy.Ram(a)usa.telekom.de [mailto:Guy.Ram@usa.telekom.de] Sent: Thursday, March 07, 2002 8:14 AM To: nanog(a)merit.edu Subject: Equinix Exchange Point Quick poll to see who's at or planning to be at the Equinix Asburn exchange point. thanks, -guy +++The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy any copies of this document.+++

1 0

RE: Equinix Exchange Point
by Hallgren, Michael 07 Mar '02

07 Mar '02

> > > Quick poll to see who's at or planning to be at the Equinix > Asburn exchange > point. Teleglobe is. mh > > thanks, > > -guy >

1 0

216.119.248.0/21
by J.D. Falk 07 Mar '02

07 Mar '02

Has ARIN begun assigning from 216 (but not updating whois), or is AS16994 playing silly buggers here? (Apparently this network was sending spam.) route-views.oregon-ix.net>sh ip bgp 216.119.251.98 BGP routing table entry for 216.119.248.0/21, version 1338771 Paths: (53 available, best #14) Advertised to non peer-group peers: 64.166.72.140 3333 9057 3549 11456 11456 16994 193.0.0.56 from 193.0.0.56 (193.0.0.56) Origin IGP, localpref 100, valid, external 7018 3549 11456 11456 16994 192.205.31.33 from 192.205.31.33 (192.205.31.33) Origin IGP, localpref 100, valid, external 8918 3356 11456 11456 16994 212.4.193.253 from 212.4.193.253 (212.4.193.253) Origin IGP, localpref 100, valid, external 6395 3356 11456 11456 16994 216.140.8.63 from 216.140.8.63 (216.140.8.63) Origin IGP, metric 416, localpref 100, valid, external Community: 6395:200 6395:1005 4006 3549 11456 11456 16994 205.215.45.50 from 205.215.45.50 (205.215.45.50) Origin IGP, localpref 100, valid, external 5056 701 3549 11456 11456 16994 167.142.3.6 from 167.142.3.6 (167.142.225.101) Origin IGP, localpref 100, valid, external [snip] -- J.D. Falk "The kick defines the beat, <jdfalk(a)cybernothing.org> the bass defines the groove." -- Phil Lockwood

3 3

Re: Telco's write best practices for packet switching networks
by Simon Higgs 06 Mar '02

06 Mar '02

At 06:30 PM 3/6/2002 +0000, you wrote: >In most people's example networks they PROBABLY run all their 'services' >on virtual interfaces anyway so ssh doesn't have to listen on the same ip >as bind so perhaps it's a non-issue. Does anyone have a good reference for this particular solution? Most software is really badly documented when it comes to this, and without configuration the service ends up on all the interfaces (or even just localhost). Popular services like BIND and Sendmail are easy enough to configure, but, documentation wise, this topic now reminds me of trying to find decent rwx anon ftp instructions ten years ago. Best Regards, Simon -- ###

1 0