Date: Thu, 15 Jul 1999 15:57:41 -0700 From: Kelly McGrew <kmcgrew@tss.net> To: dtougas@converging.net Cc: freebsd-questions@freebsd.org Subject: Re: Routing question... Message-ID: <378E6765.144E4AB1@tss.net> References: <D1378A34D8E2D211831900105A99D3FE06D1CC@BDC>
next in thread | previous in thread | raw e-mail | index | archive | help
Damien....
To know what's really up, I'd have to know your address. Is it public or
private (see RFC 1918 for a discussion of the difference, link below). If they
are assigning you a private address then NAT'ing it you could be in for trouble
down the road. If they use private addresses internally (except at their POPs)
you're fine. If I were them, that's exactly what I'd do, since I don't want
internal devices to be route-able.
Things have changed a lot over the years, but here's who owns that "wierd"
address:
Edmonton Telephones Corporation (NET-ED-TEL)
P.O. Box 20500 Edmonton, Alberta2R4
CA
Netname: ED-TEL
Netnumber: 161.184.0.0
Coordinator:
Commance, Peter (PC182-ARIN) peter@EON.NET
(403) 441-7878
Domain System inverse mapping provided by:
CLGRPS01.AGT.NET 198.80.55.1
CLGRPS02.AGT.NET 198.161.156.1
Record last updated on 21-Jan-99.
Database last updated on 15-Jul-99 16:16:09 EDT.
You can find stuff like this out from: http://www.arin.net and check their
"whois" service. You used to be able to get it from a number of places, but I
can't remember the URLS.
For RFCs go to: ftp://nis.nsf.net/documents
Go the the RFC directory.
First get the file rfc-index.txt.
RFC2400 lists the status of protocol standards. It's a good one to keep on
hand. I'd look for an update in RFC 2600 before long. The seem to do them
every 200 RFCs if they need to or not :-)
RFC1700 ("Assigned Numbers") is a good RFC to keep on hand if you do much
detailed stuff.
Check the rfc-index.txt file for keywords like "subnet" if that's your interest.
RFC1918 is Best Current Practice (you'll find only BCPs in the /documents/bcp
directory) for network addressing--it lists the private networks.
I always recommend reading the RFC dealing with whatever routing protocol(s)
you're using as well as the PPP stuff if you're dialing in.
RFC1058 describes RIP and does a good job of describing things like split
horizon, poison reverse, and triggered updates.
RFC 1122 ("Host Requirements") has an excellent discussion of how the mask is
used around page 42 or so.
RFC1812 is a good discussion of what it takes to be a router--since it is the
router requirements RFC.
For Internet-Drafts go to: ftp://ftp.isi.edu/internet-drafts/ or
http://www.ietf.org
Find drafts on the subject you're interested in, but keep in mind that drafts
expire in 6 months, so even if the topic is still timely the draft may not be
found.
Damien Tougas wrote:
> We have been experiencing some problems with our server, and
> we suspect it might be due to routing issues within our ISPs network.
> When we did a traceroute from our server, this is what we got:
>
> traceroute to freefall.freebsd.org (204.216.27.21), 30 hops max, 40 byte
> packets
> 1 10.128.4.13 (10.128.4.13) 12.350 ms 79.670 ms 12.336 ms
> 2 10.128.3.2 (10.128.3.2) 12.904 ms 12.847 ms 12.983 ms
> 3 tac02-enet0.rtr.agt.net (161.184.255.225) 13.098 ms 13.684 ms 13.814
> ms
> 4 local1-atm0-0-111.tac.net (207.229.15.25) 18.424 ms 17.902 ms 17.792
> ms
> 5 REGIONAL1-fe2-1-0.tac.net (205.233.111.39) 17.904 ms 21.189 ms 19.104
> ms
> ...etc...
>
> as you will notice, our provider is using non-routable addresses (as seen in
> hop 1
> and 2), and then they are using another wierd one (161.184.255.255) in hop 3
> before
> it gets back out in to real world addresses. I don't understand everything
> about
> internet addressing, but is what they are doing a valid scheme, or is it
> looking for
> disaster? Any thoughts (and if you could point me to an RFC) on this would
> be appreciated.
>
> Thanks.
>
> Damien Tougas
> Converging Technology Solutions, Inc.
> 10148 - 73 Street
> Edmonton, Alberta T6A 2W9
> Phone: (780) 469-1679
> Fax: (780) 461-5127
> mailto:dtougas@converging.net
> http://www.converging.net
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-questions" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?378E6765.144E4AB1>