- Test - lists.nanog.org

RE: redistribute IGP routes to BGP
by Zhao, Xingguo 01 Nov '01

01 Nov '01

I didn't get how this helps to make this redistribution useful. Could you give me more hints? > -----Original Message----- > From: Brian [mailto:bri@sonicboom.org] > Sent: Thursday, November 01, 2001 11:45 AM > To: Zhao, Xingguo; nanog(a)merit.edu > Subject: Re: > > > I would much rather define my neighbors individually and > control them that > way, and use either no sync or a hi metric null route to > satisfy bgp's must > be in igp requirement. > > Brian > > ----- Original Message ----- > From: "Zhao, Xingguo" <xzhao(a)celoxnetworks.com> > To: <nanog(a)merit.edu> > Sent: Thursday, November 01, 2001 9:33 AM > > > > > > Hi, all > > > > I have a question regarding to redistribute IGR routes into > BGP. Currently > > both Cisco > > and Juniper support it. > > > > Here I don't understand what is the advantage of this > redistribution? > > Because BGP is > > potentially injecting information into the IGP and then sending such > > information back into BGP. > > > > Could anybody provide more description regarding the > advantage and the > > disadvantage > > of redistribuing IGP routes into BGP? > > > > Do people use this in real life? > > > > Thanks a lot, > > Xingguo > > >

1 0

RE: /8 mysteries
by Stanley, Jon 01 Nov '01

01 Nov '01

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I don't recall 64/8 or 66/8 being assigned to any one entity.... - -----Original Message----- From: bmanning(a)vacation.karoshi.com [mailto:bmanning@vacation.karoshi.com] Sent: Thursday, November 01, 2001 10:54 AM To: thegameiam(a)yahoo.com Cc: nanog(a)merit.edu; rekoil(a)semihuman.com; jtk(a)aharp.is-net.depaul.edu Subject: Re: /8 mysteries and why are these bogus? - --bill -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com> iQA/AwUBO+GFxz1RUKGwp4eKEQLL9wCgvupNDoqlSEuI1peN5eZhksDr/p0AnRSJ 3IPRLvS/QN6kTwQpE3FcQcQ+ =kgII -----END PGP SIGNATURE-----

1 0

/8 mysteries
by David Barak 01 Nov '01

01 Nov '01

Personally, I find the bogus /8s which are actually IN the routing table to be about as interesting as those which are not - According to route-views.oregon-ix.net, only 22 /8s are routed in the whole, and several of them are bogus - B 64.0.0.0/8 [20/0] via 195.211.29.22, 00:17:00 B 80.0.0.0/8 [20/21040] via 4.0.0.2, 00:53:17 B 66.0.0.0/8 [20/24403] via 198.32.162.18, 09:19:59 B 62.0.0.0/8 [20/21040] via 4.0.0.2, 09:15:21 B 39.0.0.0/8 [20/24403] via 198.32.162.18, 09:19:59 -David Barak "Quis custodes ipsos custodiet?" - Juvenal __________________________________________________ Do You Yahoo!? Make a great connection at Yahoo! Personals. http://personals.yahoo.com

2 2

Re: 214/8 and 215/8
by smd＠clock.org 01 Nov '01

01 Nov '01

| The full RFC2050 justification for a /7's worth of space would | be a mighty and wondrous thing to behold. Indeed, and since 2050 predates the allocation date listed at http://www.iana.org/assignments/ipv4-address-space by a year and a half, I hope such a full justification exists for what otherwise would be a rather creepy land-grab. Maybe someone who does FOIAs regularly could start on one, since nobody seems to have jumped up to justify the two /8s? Sean. (studiously avoiding the issue of the IANA institutionalization process underway now, which presumably will have a practical bearing on such matters...)

1 0

ISP-ISAC (was Re: New Alert :: Whens the 'Net the target?)
by Kelly J. Cooper 01 Nov '01

01 Nov '01

On Oct 30, 6:38am, Randy Bush wrote: > Subject: RE: New Alert :: Whens the 'Net the target? * *> I agree. But I'd rather set up a sacrificial neck for the government to *> wring instead of letting the beaucrats pick one at random. * *couldn't think of a better one than IOPS, years of hot air and doing *nothing real. Y'know, nothing ends a day better than being told that I've been toiling for years in vain. Ah, the good life. Let me try again to do something real, but this time with a little more context. A couple of weeks ago, I asked the NANOG mailing list for feedback on what ISPs (of every stripe) consider to be useful information feeds. The REASON I was asking is because we're about to get the ISP-ISAC started (hopefully before the year is out) and I was wondering what information would be useful enough for the us to collect, analyze, and provide to members that ISPs would consider it (the ISP-ISAC that is) valuable. So, instead of a bunch of hot air about the ISP-ISAC not doing anything when we haven't even started yet, howzabout ya'll give me some good solid feedback to this request? Because I only got 3 (serious) emails and a phone call last time I asked. (All with good suggestions, btw, but I'm hoping for more). --- Forwarded mail from <kcooper> ("Kelly J. Cooper") * From: "Kelly J. Cooper" <kcooper> * Date: Mon, 8 Oct 2001 22:54:39 +0000 * To: nanog(a)merit.edu * Subject: INFORMATION FEEDS What information feeds are the most useful to your NOC? To your Analysts? To your Engineers? To your Customers? Do you want them to see outage reports on the MAEs? Fiber cut reports from certain telcos/fiber providers? (If so, which ones?) Maintenance reports on NAPs? Maintenance plans from peers? Ticket-based updates from your upstreams/transit providers/peers regarding outages? Changes to registrar databases? Maintenance announcements on the root servers? Outages or degradation in availability for popular web sites? All of the above? None of the above? Many other subjects? (If so, which ones?) Thanks, Kelly J. (Not talking about Security just yet...) -- Kelly J. Cooper - Security Engineer GENUITY - Main # - 800-632-7638 3 Van de Graaff Drive - Fax - 781-262-2744 Burlington, MA 01803 - http://www.genuity.net ---End of forwarded mail from <kcooper> ("Kelly J. Cooper")

2 1

whois.ra.net
by Tatsuya Kawasaki 31 Oct '01

31 Oct '01

whois server on RA.NET is not working .. it does not look like DNS update correctly.. > set q=SOA > ra.net Server: auth2.xx.xx.xx Address: 210.xx.xx.xx *** xx.xx.xx.xx can't find ra.net: Non-existent host/domain Default Server: DNS.MERIT.NET Address: 198.108.1.42 > set q=SOA > ra.net Server: DNS.MERIT.NET Address: 198.108.1.42 ra.net origin = dns.merit.net mail addr = dns.merit.net serial = 200008040 refresh = 28800 (8H) retry = 14400 (4H) expire = 2419200 (4W) minimum ttl = 1200 (20M) ra.net nameserver = dns.merit.net ra.net nameserver = dns2.merit.net ra.net nameserver = dns3.merit.net dns.merit.net internet address = 198.108.1.42 dns2.merit.net internet address = 198.109.36.3 dns3.merit.net internet address = 198.108.130.5 I can use "whois.radb.net" though... Tatsuya /_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ Tatsuya Kawasaki Allegiance Telecom Unlock the Power of the Internet http://www.kivex.com Phone 301.215.6777 Fax 301.215.5991 Affiliation given for identification not representation /_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/

2 1

Nimda.E = New Worm Request for Trace or Log
by Murphy, Brennan 31 Oct '01

31 Oct '01

If you have a sniffer trace file or a log of the activity of the new Nimda.E worm that has begun spreading in APAC, would you kindly send me an email? From those that reply, I can pick one or two to request they send them to me. (saves me from getting 100 emails with logs/traces in them) The new worm is reported here: http://www.zdnet.com/zdnn/stories/news/0,4586,5098988,00.html As this article indicates, the fixes for the original Nimda should work for this as well. Nonetheless, I'm still looking for a trace of it. Thanks!! -BM

1 0

Re: Contact for Yahoo postmaster ?
by miquels＠cistron-office.nl 30 Oct '01

30 Oct '01

In article <cistron.9r9ipi$kov$1(a)ncc1701.cistron.net>, Miquel van Smoorenburg <miquels(a)cistron-office.nl> wrote: >Does anyone know who to contact if you've been blacklisted >by the Yahoo SMTP servers? > ># nc -s195.64.68.40 203.199.70.34 smtp >553 Mail from 195.64.68.40 not allowed - user complaints of spam from this ip > >I tried postmaster(a)yahoo.com but got no reply. > >Weird that a mailservice this big blacklists people without giving >them advance notice and without reading postmaster(a)yahoo.com .. Right, I've tried postmaster(a)yahoo.com, abuse(a)yahoo.com, tech-contact(a)yahoo-inc.com. I got an auto-reply from the latter two, but that's all. Been blacklisted for a week now I guess, without any reason I know of. If someone from Yahoo reads this please contact me at postmaster(a)cistron.nl Mike. -- "Only two things are infinite, the universe and human stupidity, and I'm not sure about the former" -- Albert Einstein.

3 2

New Alert :: Whens the 'Net the target?
by Eric Germann 30 Oct '01

30 Oct '01

Do you think there will be an Internet component to one of these, someday? http://www.msnbc.com/news/633205.asp ========================================================================== Eric Germann CCTec ekgermann(a)cctec.com Van Wert OH 45801 http://www.cctec.com Ph: 419 968 2640 Fax: 603 825 5893 "It is so easy to miss pretty trivial solutions to problems deemed complicated. The goal of a scientist is to find an interesting problem, and live off it for a while. The goal of an engineer is to evade interesting problems :)" -- Vadim Antonov <avg(a)kotovnik.com> on NANOG

6 7

Re: kornet.net abuse desk is mailing out W32.Nimda.E@mm worm
by Steven M. Bellovin 30 Oct '01

30 Oct '01

In message <195358945566.20011030133637(a)conti.nu>, Kai Schlichting writes: > >If you or your staff have dealt with kornet.net (a Korean ISP belonging >to Korean Telecom), and specifically abuse(a)kornet.net in the past, beware: >It seems that they've been overrun by the brand-spanking-new W32.Nimda.E@mm >worm (**) sometimes late last night. > >Specific case in hand: yesterday at 9:40pm EST, I received a mail >with a Subject: line of an UNRELATED abuse issue (hello MFNX/XO/ >Above.net :) that contains a MIME attachment with an auto-playing >"sound file" of sample.exe , openened in an <iframe> of your favorite >Microsoft email client. Source IP of the mailing : 210.222.17.36 (/24). Note, however, that the From: line on these Nimda variants is also forged; see http://securityresponse.symantec.com/avcenter/venc/data/w32.nimda.a@mm.html for details. (I received several messages saying that some mail I sent was infected with Nimda.E. This struck me as quite improbable, since I use NetBSD for all my email and other real work.) --Steve Bellovin, http://www.research.att.com/~smb Full text of "Firewalls" book now at http://www.wilyhacker.com

1 0