someone RBL'd a reserveD-8 number from IANA
98.100.32.32 traceroute to 98.100.32.32 (98.100.32.32): 1-30 hops, 38 byte packets 1 main.bungi.com (207.126.97.9) 2.15 ms 1.73 ms 1.86 ms 2 above-gw2.above.net (207.126.96.217) 4.41 ms 4.88 ms 3.67 ms 3 core5-main2-oc3.sjc.above.net (216.200.0.205) 3.62 ms 4.56 ms 7.53 ms 4 core3-core5-oc48.sjc2.above.net (208.184.102.206) 6.34 ms 5.7 ms 5.3 ms 5 iad-sjc2-oc48.iad.above.net (216.200.127.25) 73.0 ms 79.7 ms 72.6 ms 6 hat.address.is.on.the.rbl.see.www.mail-abuse.org.for.more.information.above.net (208.185.0.26) 72.7 ms 73.6 ms 105 ms 7 * * * -- Thank you; |--------------------------------| | Thinking is a learned process. | | ICANN member @large | | Gigabit over IP, ieee 802.17 | |--------------------------------| Henry R. Linneweh
On Thu, 20 Jul 2000, Henry R. Linneweh wrote:
98.100.32.32 hat.address.is.on.the.rbl.see.www.mail-abuse.org.for.more.information.above.net (208.185.0.26) 72.7 ms 73.6 ms 105 ms 7 * * *
I thought they had put all reserved IP space on the RBL to prevent it from being announced and used by spammers, then unannounced to make it harder to track the source. ---------------------------------------------------------------------- Jon Lewis *jlewis@lewis.org*| I route System Administrator | therefore you are Atlantic Net | _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________
On Thu, 20 Jul 2000 07:47:30 PDT, "Henry R. Linneweh" <linneweh@concentric.net> said:
98.100.32.32
OK.. I proved yesterday that I'm an idiot, but could somebody explain to me why you'd expect to be able to reach an address in IANA-reserved space? (Didn't we just have this same discussion re: 1918 addresses? ;) -- Valdis Kletnieks Operating Systems Analyst Virginia Tech
It seems some people don't Martian filter IANA-reserved space, and some providers that do BGP with their customers don't filter their customers announcements. So, there's nothing to stop a person from getting a T1 to a provider that doesn't filter announcements and announcing some IANA-reserved space to do malicious things through, and then stop the announcements of the IANA-reserved space after their done. It's not likely that anyone else would be using the reserved space, and less chance that people will be actively filtering it like they do RFC1918 address space. The effects of such activities are left as an exercise for the reader. -- Joseph W. Shaw On Thu, 20 Jul 2000 Valdis.Kletnieks@vt.edu wrote:
On Thu, 20 Jul 2000 07:47:30 PDT, "Henry R. Linneweh" <linneweh@concentric.net> said:
98.100.32.32
OK.. I proved yesterday that I'm an idiot, but could somebody explain to me why you'd expect to be able to reach an address in IANA-reserved space?
(Didn't we just have this same discussion re: 1918 addresses? ;)
participants (5)
-
Henry R. Linneweh -
jlewis＠lewis.org -
Joe Shaw -
Mark Milhollan -
Valdis.Kletnieks＠vt.edu