One for the router techies - GoFuckYourself.com

UnseenWorld · 11-13-2002, 11:48 AM

I run into "router issues" from time to time. You know: I can see a site but someone else can't and vice versa.

According to my understanding of the genesis of the Internet, this is exactly the sort of thing the Internet was designed to prevent, right? I mean, if someone drops a nuker on Nashville or Topeka, information is simply routed around the bomb crater and data travels uninterrupted.

So, WHY ARE THERE ROUTER PROBLEMS?

pr0 · 11-13-2002, 12:26 PM

Typically the problem originates at the end host, or at your isp. The route in between is usually clear. So its probably your isp's fuck up, or your end-servers fuck up.

Droppin a nuker

Rory · 11-13-2002, 12:27 PM

Quote:

Originally posted by UnseenWorld
I run into "router issues" from time to time. You know: I can see a site but someone else can't and vice versa.

According to my understanding of the genesis of the Internet, this is exactly the sort of thing the Internet was designed to prevent, right? I mean, if someone drops a nuker on Nashville or Topeka, information is simply routed around the bomb crater and data travels uninterrupted.

So, WHY ARE THERE ROUTER PROBLEMS?

Call Ponch.

buran · 11-13-2002, 01:11 PM

that's the way it was DESIGNED, but that's not the way it operates. Today most internet topology is like a star. Once you get to the Level1 providers you can typically find another route, but from you to your first tier1/level1 provider and from the cloud down to your host you'll almost always find single points of failure. That's supposed to be on the big advantages of colocation, the facility where you're located should have multiple paths, both logically and phsyically.

Learn to use the traceroute/tracert command. On windows go to start, run, command, then from the dos shell type "tracert hostname.com" or from a unix shell type "traceroute hostname.com" ... this should give you an understanding of who's problem it is.

11-13-2002, 11:48 AM	#1
UnseenWorld Confirmed User Join Date: May 2001 Location: Portland, OR, USA Posts: 5,279	One for the router techies I run into "router issues" from time to time. You know: I can see a site but someone else can't and vice versa. According to my understanding of the genesis of the Internet, this is exactly the sort of thing the Internet was designed to prevent, right? I mean, if someone drops a nuker on Nashville or Topeka, information is simply routed around the bomb crater and data travels uninterrupted. So, WHY ARE THERE ROUTER PROBLEMS? __________________ SIG TOO BIG! Maximum 120x60 button and no more than 3 text lines of DEFAULT SIZE and COLOR. Unless your sig is for a GFY top banner sponsor, then you may use a 624x80 instead of a 120x60.

11-13-2002, 12:26 PM	#2
pr0 rockin tha trailerpark Industry Role: Join Date: May 2001 Location: ~Coastal~ Posts: 23,088	Typically the problem originates at the end host, or at your isp. The route in between is usually clear. So its probably your isp's fuck up, or your end-servers fuck up. Droppin a nuker __________________ __________ Loadedca$h - get sum! - Revengebucks - mmm rebills! - webair (gotz sErVrz)

11-13-2002, 01:11 PM	#4
buran Confirmed User Join Date: Mar 2002 Location: how'd I get here? Posts: 264	that's the way it was DESIGNED, but that's not the way it operates. Today most internet topology is like a star. Once you get to the Level1 providers you can typically find another route, but from you to your first tier1/level1 provider and from the cloud down to your host you'll almost always find single points of failure. That's supposed to be on the big advantages of colocation, the facility where you're located should have multiple paths, both logically and phsyically. Learn to use the traceroute/tracert command. On windows go to start, run, command, then from the dos shell type "tracert hostname.com" or from a unix shell type "traceroute hostname.com" ... this should give you an understanding of who's problem it is. __________________ [this signature intentionally left blank]