New City/County web portal good for IDCnet.com
Ask your nerdy friends what this all means.
In short:
The new web site takes traffic from the largest propable sources via some rather questionable routes.
We need a traffic exchange point in southeastern wisconsin where government and corporate networks can directly interconnect. Pick a room in a well connected building and just do it.
Traceroute to www.city.milwaukee.gov
From UWM
1 salmonbay-7-7 (129.89.7.7) 2 ms 1 ms 2 ms
2 space-needle-10-146 (129.89.10.146) 1 ms 1 ms 1 ms
3 UWMilwaukeeISP-ge0-0-0-301.core.wiscnet.net (216.56.1.193) 1 ms 1 ms 1 ms
4 r-doral-isp-a0-1-0-2.wiscnet.net (140.189.8.166) 2 ms 2 ms 3 ms
5 ge3-13.as.eqxchiil.aleron.net (205.198.16.157) 2 ms 3 ms 2 ms
6 p12-0.core02.ord01.atlas.cogentco.com (154.54.2.241) 4 ms 3 ms 3 ms
7 p12-0.core03.ord01.atlas.cogentco.com (154.54.3.154) 3 ms 4 ms 4 ms
8 p4-0.ca02.mke01.atlas.cogentco.com (154.54.1.154) 181 ms 371 ms 10 ms
9 38.119.239.138 (38.119.239.138) 9 ms 6 ms 8 ms
10 ip-66-175-196-210.idcnet.com (66.175.196.210) 9 ms 8 ms 14 ms
11 County Firewall
Analysis:
1-2 UWM campus
3-4 Wiscnet backbone to Norlight colocation at Doral Plaza in Chicago
5 Hop to aleron at Equinix in Chaicago
6-8 Back up to Milwaukee on the cogent network
9 Unresolved ex PSI now Cogent interface to idcnet
10 idcs net (Milwaukee?)
11 County Firewall
Traceroute to www.city.milwaukee.gov
From SBC
traceroute to www.city.milwaukee.gov (204.194.251.40), 64 hops max, 40 byte packets
1 adsl-68-78-82-30.dsl.milwwi.ameritech.net (68.78.82.30) 1.199 ms 0.602 ms 0.529 ms
2 adsl-68-78-83-254.dsl.milwwi.ameritech.net (68.78.83.254) 7.650 ms 9.399 ms 7.524 ms
3 dist1-vlan60.milwwi.ameritech.net (65.43.19.242) 8.324 ms 8.899 ms 8.541 ms
4 bb1-g1-0.milwwi.ameritech.net (65.43.19.99) 9.285 ms 8.689 ms 8.287 ms
5 bb1-p3-2.chcgil.ameritech.net (151.164.190.85) 10.773 ms 10.364 ms 11.225 ms
6 bb2-p11-0.chcgil.ameritech.net (151.164.191.182) 13.205 ms 11.738 ms 11.714 ms
7 bb1-p5-0.applwi.sbcglobal.net (151.164.191.94) 14.222 ms 15.746 ms 15.440 ms
8 ded1-fa0-0-0.applwi.ameritech.net (67.38.56.101) 15.943 ms 15.292 ms 15.407 ms
9 64.108.143.130 (64.108.143.130) 16.943 ms 18.175 ms 16.889 ms
10 backbone.f0-0.c7206-2.noc.apl.athenet.net (209.103.221.227) 17.690 ms 17.736 ms 17.615 ms
11 border1.wel.mke.athenet.net (209.103.211.78) 19.143 ms 18.917 ms 19.145 ms
12 209.103.211.82 (209.103.211.82) 62.535 ms 58.371 ms 60.712 ms
13 ip-66-175-196-210.idcnet.com (66.175.196.210) 62.761 ms 47.244 ms 43.508 ms
14 * * *
Analysis:
1-4 Bounce around Milwaukee on SBCs network.
4-5 Milwaukee broadway Central Office to Chicago Franklin Central Office.
5-7 Bounce around inside the Franklin Central Office then up to Appleton.
9 Unresolved interface facing athenet
10 Probably the athenet office in Appleton
11 Down to Milwaukee
12 Unresolved border router address facing idcnet
13 idcnet milwaukee
14 County Firewall
Traceroute to www.city.milwaukee.gov
From Road Runner
traceroute to www.city.milwaukee.gov (204.194.251.40), 30 hops max, 40 byte packets
1 ** RFC 1918 NAT **
2 ** RFC 1918 NAT **
3 srp1-0.milwwirtco-rtr1.wi.rr.com (24.160.224.241) 10.758 ms 18.122 ms 10.793 ms
4 so0-1-0.kscymol3-rtr1.kc.rr.com (24.94.160.17) 33.625 ms 43.678 ms 37.71 ms
5 so-4-0.hsa1.stlouis1.level3.net (63.208.56.5) 33.287 ms 34.001 ms 36.345 ms
6 ge-6-0-0.mp2.stlouis1.level3.net (64.159.0.69) 37.348 ms 35.796 ms 38.166 ms
7 ae-0-0.bbr1.chicago1.level3.net (64.159.1.33) 41.021 ms so-6-1-0.bbr2.chicago1.level3.net (64.159.0.58) 53.142 ms ae-0-0.bbr1.chicago1.level3.net (64.159.1.33) 41.408 ms
8 so-7-0-0.edge1.chicago1.level3.net (209.244.8.14) 37.616 ms so-6-0-0.edge1.chicago1.level3.net (209.244.8.10) 57.614 ms so-7-0-0.edge1.chicago1.level3.net (209.244.8.14) 93.069 ms
9 4.68.127.130 (4.68.127.130) 38.884 ms 48.232 ms 37.647 ms
10 p12-0.core02.ord01.atlas.cogentco.com (154.54.2.241) 42.209 ms 41.332 ms 42.499 ms
11 p12-0.core03.ord01.atlas.cogentco.com (154.54.3.154) 38.151 ms 37.737 ms 37.609 ms
12 p4-0.ca02.mke01.atlas.cogentco.com (154.54.1.154) 49.592 ms 41.256 ms 63.596 ms
13 38.119.239.138 (38.119.239.138) 50.204 ms 50.993 ms 52.284 ms
14 ip-66-175-196-210.idcnet.com (66.175.196.210) 49.794 ms 58.065 ms 43.769 ms
15 County Firewall
Analysis:
1-2 internal network numbers of the network used for the traceroute
3-4 RoadRunner down to Kansas City
4-5 Off to Saint Louis via the Level 3 network (apparently RR wisconsin is not on the shinny new Time Warner ATDN network)
5-8 Bounce around level 3 until we get to Chicago
9 Unresolved private handoff between level 3 and cogent (don't tell anyone!)
10-12 Take cogent back up to Milwaukee
13-14 Same stuff we saw in our first two traces.
renoir:~ jtk$ whois -a 204.194.251.40
OrgName: Milwaukee County Gov't
OrgID: MCG-45
Address: 235 West Galena St. Suite 600
City: Milwaukee
StateProv: WI
PostalCode: 53212
Country: US
NetRange: 204.194.248.0 - 204.194.255.255
CIDR: 204.194.248.0/21
NetName: MILWCNTY-NET
NetHandle: NET-204-194-248-0-1
Parent: NET-204-0-0-0-0
NetType: Direct Assignment
NameServer: A.NS.ONLIGHT.COM
NameServer: B.NS.ONLIGHT.COM
NameServer: C.NS.ONLIGHT.COM
Comment:
RegDate:
Updated: 2002-11-20
NOCHandle: ZO26-ARIN
NOCName: Onlight, llc.
NOCPhone: +1-414-272-4477
NOCEmail: support@onlight.com
TechHandle: ZI95-ARIN
TechName: IMSD
TechPhone: +1-414-289-6654
TechEmail: RSLADKY@milwcnty.com
# ARIN WHOIS database, last updated 2005-04-06 19:10
# Enter ? for additional hints on searching ARIN's WHOIS database.
posted by Joe Klein @ 11:11 AM
5 comments
links to this post
5 Comments:
You fail to take into account the downside of housing all of this information in one place. Your idea is short-sighted.
thanks.
I'm a terrorist. I'm going to blow up your building and guess what. So long milwaukee government/corporate internet accessibility. The internet is good because of redundancy and diversity in providers. Putting everything important in one building is a horrible idea. BOOM!
Seriously, one bad hop in a list of hops that are an average of 10ms or less? This is bad why? A total hop count of less than 11 (if you take out firewall and the user's computer).
What exactly are you complaining about? As long as it is fast and has good availability, who cares what traffic your data goes on? Nevermind that different networks are going to get to the same sites via completely different routes. Anyone not at UWM probably won't get anything near the same route as this one.
Do I? The fact is that the information is currently all in one place. Exchange points create diversity and can be spread out across multiple geaographic locations. I have suggested to the city that they use DNS services from an organization like UltraDNS that uses anycast and has servers in multiple locations.
Take a good look. It is not diversified and it is in all one place
Hurricains, tornados, fires, earthquakes, hackers. Bambs are hardly the only concern.
Point is ... it is neither fast or diverse.
I have been seeing that same ISP on every one of my server logs. I have been suspicious of it for a long time, but could not resolve where it was coming from. I have been noticing that the ISP is also monitoring (at least one) message board(s) as well...because there have been several direct connections to my site from that message board (from someone using an ISP containing "milwwi").
I have a question for you. There is another suspicious block of ISPs coming on my server logs. I think they belong to Homeland Security, but I cannot know for sure yet. Here is a sample: mn-71-49-90-236.dhcp.sprint-hsd.net
nv-69-68-202-29.sta.sprint-hsd.net
There are many more, but WHOIS info says they are registered in Winterpark, Florida. However, I have been monitoring my server logs very closely, and I could swear that it's Homeland Security and their contract with Sprint.
Can you get back to me on this?
Thanx.
Mel.
Post a Comment
Links to this post:
Create a Link
<< Home