Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!metro!metro!asstdc.scgt.oz.au!nsw.news.telstra.net!act.news.telstra.net!imci3!newsfeed.internetmci.com!in2.uu.net!nntp.teleport.com!usenet
From: blake@pbgi.com (Blake Swensen)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Lame ISP and routing rules.
Date: Tue, 28 May 96 19:54:23 GMT
Organization: Pillar/Blake International
Lines: 60
Message-ID: <4og02d$7if@nadine.teleport.com>
NNTP-Posting-Host: 206.251.72.5
X-Newsreader: News Xpress Version 1.0 Beta #3
I have a problem that I cannot get my ISP to solve and I am looking for a
'work-around.'
Mail destined to GOL.COM (among others) is getting a time out:
phil: {3} mailq
Mail Queue (1 request)
--Q-ID-- --Size-- -----Q-Time----- ------------Sender/Recipient------------
MAA04586 244 Sun May 26 12:40 <SOLOBIKE@china_cat.pbgi.com>
(Deferred: Operation timed out during initial connection with)
<mpotter@gol.com>
This looks like the DNS server, or the GOL router is lame. However when I
telnet offsite, the traceroute to GOL works fine. In fact, mail sent to
GOL.COM from outside my ISP's dominion works fine (from traceroute from
netcom.com):
1 192.100.81.254 (192.100.81.254) 2 ms 4 ms 5 ms
2 sjx-ca-gw1.netcom.net (163.179.1.29) 3 ms 4 ms 8 ms
3 t3-1.scl-ca-gw3.netcom.net (163.179.220.194) 9 ms 8 ms 13 ms
4 sl-mae-w-F0/0.sprintlink.net (198.32.136.11) 123 ms 247 ms 35 ms
5 sl-stk-6-H3/0-T3.sprintlink.net (144.228.10.45) 180 ms 15 ms 16 ms
6 sl-stk-8-F0/0.sprintlink.net (144.228.40.8) 33 ms 18 ms 28 ms
7 sl-gol-2-s0-T1.sprintlink.net (144.228.48.26) 22 ms 26 ms 22 ms
8 202.243.63.70 (202.243.63.70) 972 ms 836 ms 814 ms
9 gol1.gol.com (202.243.48.4) 842 ms 916 ms 842 ms
From within my domain... I get the following traceroute:
1 rtr (206.251.72.1) 2.430 ms 2.095 ms 2.087 ms
2 s0.r0.trans.rain.rg.net (204.119.36.3) 18.536 ms 18.508 ms 17.845 ms
3 s0.r0.trans.rain.rg.net (204.119.36.3) 18.227 ms 30.253 ms 18.119 ms
4 core1-fddi.SaltLake.elix.net (207.0.56.17) 63.969 ms 53.803 ms 66.224
ms
5 core1-fddi.SaltLake.elix.net (207.0.56.17) 58.742 ms 57.554 ms 51.248
ms
6 border2-hssi2-0.Denver.mci.net (204.70.29.9) 75.613 ms 104.264 ms 67.357
ms
7 core1-fddi-1.Denver.mci.net (204.70.3.113) 78.744 ms 79.913 ms 92.507
ms
8 core3.WillowSprings.mci.net (204.70.4.25) 195.730 ms 101.856 ms 117.412
ms
9 ameritech-nap.WillowSprings.mci.net (204.70.1.198) 102.358 ms 92.384 ms
105.263 ms
10 * * *
11 etc * * * to hop 30
I contacted the technical guy at MCI, thinking that they had a lame router,
but he informed me: "Please open a ticket with your service provider if you
are having problems. You are not stopping at the ameritech router, the next
hop doesn't come back to you through MCI. This has to do with multiple access
and route announcments based on your service provider's routing policy."
So my question is: can I, by using gated/routed (on FreeBSD 2.01), bypass my
ISP's routing policy, and take more control of the problem? Alternatively, is
there a way to peek at my ISP's (Linux) routing rules and indentify exactly
what his problem is and how to fix it?
Peace,
Blake