Anyone else see this from their paths? vader# whois -h whois.cymru.com " -v 11.11.11.2" AS | IP | BGP Prefix | CC | Registry | Allocated | AS Name NA | 11.11.11.2 | NA | US | arin | 1984-01-19 | NA #trace Protocol [ip]: Target IP address: 66.80.187.122 Source address: Numeric display [n]: y 1 68.250.30.166 0 msec 2 68.250.30.131 0 msec 3 66.73.28.129 4 msec 4 65.43.25.116 4 msec 5 151.164.93.93 12 msec 6 151.164.43.195 16 msec 7 151.164.42.168 52 msec 8 151.164.191.174 16 msec 9 151.164.42.141 16 msec 10 4.68.110.197 20 msec 11 4.68.101.1 20 msec 12 209.247.8.65 28 msec 13 209.247.9.254 44 msec 14 4.78.164.11 28 msec 15 169.130.98.227 188 msec 16 199.72.43.250 52 msec 17 11.11.11.2 40 msec 18 11.11.11.1 40 msec 19 11.11.11.2 44 msec 20 11.11.11.1 40 msec 21 11.11.11.2 44 msec 22 11.11.11.1 40 msec 23 11.11.11.2 48 msec 24 11.11.11.1 44 msec 25 11.11.11.2 44 msec 26 11.11.11.1 48 msec 27 11.11.11.2 48 msec 28 11.11.11.1 48 msec
Elijah Savage wrote (on Thu, Jan 04, 2007 at 03:28:13PM -0500):
Anyone else see this from their paths?
vader# whois -h whois.cymru.com " -v 11.11.11.2" AS | IP | BGP Prefix | CC | Registry | Allocated | AS Name NA | 11.11.11.2 | NA | US | arin | 1984-01-19 | NA
#trace Protocol [ip]: Target IP address: 66.80.187.122 Source address: Numeric display [n]: y 17 11.11.11.2 40 msec 18 11.11.11.1 40 msec 19 11.11.11.2 44 msec 20 11.11.11.1 40 msec 21 11.11.11.2 44 msec 22 11.11.11.1 40 msec 23 11.11.11.2 48 msec 24 11.11.11.1 44 msec 25 11.11.11.2 44 msec 26 11.11.11.1 48 msec 27 11.11.11.2 48 msec 28 11.11.11.1 48 msec
Yep. Way cool. -- _________________________________________ Nachman Yaakov Ziskind, FSPA, LLM awacs@ziskind.us Attorney and Counselor-at-Law http://ziskind.us Economic Group Pension Services http://egps.com Actuaries and Employee Benefit Consultants
On Thu, 4 Jan 2007, Nachman Yaakov Ziskind wrote:
25 11.11.11.2 44 msec 26 11.11.11.1 48 msec 27 11.11.11.2 48 msec 28 11.11.11.1 48 msec
Yep. Way cool.
Unfortunately it's not the first time that: 1) someone with enable screwed up a routing design or did something dumb like dueling static routes, or some similar kind of rubbish. 2) someone with enable (or someone who manages peple with enable) co-opted arbitrary non-1918 IP space for use on their internal network. Calling it RFC1919 space would almost be funny if it weren't such a pain the butt to deal with people who do things like this. jms
participants (3)
-
Elijah Savage -
Justin M. Streiner -
Nachman Yaakov Ziskind