Hello (Hopefully to someone at ISI). I have been having issues reaching EP.net for a while; Your border serving your BBNcircuit is reporting address unreachable for 198.32.4.0/24. Since I cannot see your annoucements through PBI, I have no other path into ISI. Are you currently having issues with your IGP? Or is there a reason why BBN customers cannot reach EP.net? Thanks Ahead for Fixing this, Joe --- Joe Wood Flying Crocodile, Inc. Senior Network Engineer Network Operations <joew@flyingcroc.net> 2001 Sixth Avenue, Suite 3302 206.269.0190 Seattle WA 98121
either there is a CEF problem (can reach other nodes on that subnet but not www.ep.net) -OR- something else is occuring.
Hello (Hopefully to someone at ISI).
I have been having issues reaching EP.net for a while; Your border serving your BBNcircuit is reporting address unreachable for 198.32.4.0/24. Since I cannot see your annoucements through PBI, I have no other path into ISI.
Are you currently having issues with your IGP? Or is there a reason why BBN customers cannot reach EP.net?
Thanks Ahead for Fixing this,
Joe
--- Joe Wood Flying Crocodile, Inc. Senior Network Engineer Network Operations <joew@flyingcroc.net> 2001 Sixth Avenue, Suite 3302 206.269.0190 Seattle WA 98121
Trace to www.ep.net dies here for us: 16 p0-0-0.lsanca1-cr3.bbnplanet.net (4.24.4.18) 105.426 ms 105.143 ms 104.380 ms 17 * * * 18 * --- John Fraizer EnterZone, Inc On Wed, 21 Mar 2001 bmanning@vacation.karoshi.com wrote:
either there is a CEF problem (can reach other nodes on that subnet but not www.ep.net) -OR- something else is occuring.
Hello (Hopefully to someone at ISI).
I have been having issues reaching EP.net for a while; Your border serving your BBNcircuit is reporting address unreachable for 198.32.4.0/24. Since I cannot see your annoucements through PBI, I have no other path into ISI.
Are you currently having issues with your IGP? Or is there a reason why BBN customers cannot reach EP.net?
Thanks Ahead for Fixing this,
Joe
--- Joe Wood Flying Crocodile, Inc. Senior Network Engineer Network Operations <joew@flyingcroc.net> 2001 Sixth Avenue, Suite 3302 206.269.0190 Seattle WA 98121
On Wed, 21 Mar 2001, John Fraizer wrote:
Joe, a LOT of providers don't accept 198.32.4.0/24. We see it on 2 out of four paths. The other two providers are filtering it.
I can understand this; However, if I see a path, I _should_ (in theory) be able to reach the destination network. I'm not sure why routing policy is even being brought up right now.
Trace to www.ep.net dies here for us: 16 p0-0-0.lsanca1-cr3.bbnplanet.net (4.24.4.18) 105.426 ms 105.143 ms 104.380 ms 17 * * * 18 *
Note that hop 16 is a customer access router. Also note that ISIs border is now responding with !X: traceroute to flag.ep.net (198.32.4.13), 30 hops max, 40 byte packets 1 fw1.westin33.flyingcroc.net (207.246.151.1) 0.173 ms 0.146 ms 0.140 ms 2 f7-0-100M.cr3.sea.flyingcroc.net (207.246.129.225) 0.537 ms 0.504 ms 0.565 ms 3 g1-0-1000M.br4.sea.flyingcroc.net (207.246.155.132) 0.279 ms 0.275ms 0.229 ms 4 p3-3.evrtwa1-cr2.bbnplanet.net (4.0.63.249) 1.894 ms 1.411 ms 1.553ms 5 p3-0.evrtwa1-ba2.bbnplanet.net (4.24.5.109) 1.657 ms 1.585 ms 1.469ms 6 p1-0.evrtwa1-ba1.bbnplanet.net (4.24.5.89) 1.797 ms 2.043 ms 1.700ms 7 p4-0.lsanca1-br1.bbnplanet.net (4.0.6.37) 27.470 ms 27.446 ms 27.302ms 8 p6-0.lsanca2-br1.bbnplanet.net (4.24.5.49) 30.024 ms 27.180 ms 28.528ms 9 p7-0.lsanca1-ba1.bbnplanet.net (4.24.4.1) 27.655 ms 27.807 ms 27.103ms 10 p0-0-0.lsanca1-cr3.bbnplanet.net (4.24.4.18) 27.774 ms 29.077 ms 28.219ms 11 * s0.uscisi.bbnplanet.net (4.24.40.14) 29.742 ms !X * PBI seems to be fine, perhaps another border router? 10 ded3-fe8-0-0.lsan03.pbi.net (206.13.29.130) [AS 5676] 8 msec 8 msec 12 msec 11 uscisi-usc-630375.cust-rtr.pacbell.net (209.232.128.190) [AS 5673] 20 msec 20 msec 16 msec 12 isi-usc-atm.ln.net (130.152.128.1) [AS 226] 20 msec 24 msec 20 msec 13 bah.isi.edu (128.9.160.26) [AS 226] 24 msec 24 msec 24 msec 14 flag.ep.net (198.32.4.13) [AS 226] 20 msec 20 msec 20 msec Its interesting how it has suddenly gone from !A to !X. Joe
On Wed, 21 Mar 2001 bmanning@vacation.karoshi.com wrote:
either there is a CEF problem (can reach other nodes on that subnet but not www.ep.net) -OR- something else is occuring.
Hello (Hopefully to someone at ISI).
I have been having issues reaching EP.net for a while; Your border serving your BBNcircuit is reporting address unreachable for 198.32.4.0/24. Since I cannot see your annoucements through PBI, I have no other path into ISI.
Are you currently having issues with your IGP? Or is there a reason why BBN customers cannot reach EP.net?
Thanks Ahead for Fixing this,
Joe
--- Joe Wood Flying Crocodile, Inc. Senior Network Engineer Network Operations <joew@flyingcroc.net> 2001 Sixth Avenue, Suite 3302 206.269.0190 Seattle WA 98121
--- Joe Wood Flying Crocodile, Inc. Senior Network Engineer Network Operations <joew@flyingcroc.net> 2001 Sixth Avenue, Suite 3302 206.269.0190 Seattle WA 98121
On Wed, 21 Mar 2001, Joe Wood wrote:
On Wed, 21 Mar 2001, John Fraizer wrote:
Joe, a LOT of providers don't accept 198.32.4.0/24. We see it on 2 out of four paths. The other two providers are filtering it.
I can understand this; However, if I see a path, I _should_ (in theory) be able to reach the destination network.
I'm not sure why routing policy is even being brought up right now.
People have been known to default into networks as a "oh crap" backup. In that case, even if there wasn't a BGP route in your tables to the net, you would hand it off to your "default" who may or may not have a bgp route to that network. It causes the same exact behavior you're seeing now. Prior to being multihomed, I ran into this trying to go to the EXACT same site because we were defaulting into a network that (STILL) filters 198.32.4.0/24.
Also note that ISIs border is now responding with !X:
PBI seems to be fine, perhaps another border router?
10 ded3-fe8-0-0.lsan03.pbi.net (206.13.29.130) [AS 5676] 8 msec 8 msec 12 msec 11 uscisi-usc-630375.cust-rtr.pacbell.net (209.232.128.190) [AS 5673] 20 msec 20 msec 16 msec 12 isi-usc-atm.ln.net (130.152.128.1) [AS 226] 20 msec 24 msec 20 msec 13 bah.isi.edu (128.9.160.26) [AS 226] 24 msec 24 msec 24 msec 14 flag.ep.net (198.32.4.13) [AS 226] 20 msec 20 msec 20 msec
Its interesting how it has suddenly gone from !A to !X.
Joe
It's working again for us. --- John Fraizer EnterZone, Inc
as it does for me (from the IETF) (flag.ep.net being at 198.32.4.13) but..... I have no problems with 198.32.4.21 or 198.32.4.22
Trace to www.ep.net dies here for us:
16 p0-0-0.lsanca1-cr3.bbnplanet.net (4.24.4.18) 105.426 ms 105.143 ms 104.380 ms 17 * * * 18 *
--- John Fraizer EnterZone, Inc
On Wed, 21 Mar 2001 bmanning@vacation.karoshi.com wrote:
either there is a CEF problem (can reach other nodes on that subnet but not www.ep.net) -OR- something else is occuring.
Hello (Hopefully to someone at ISI).
I have been having issues reaching EP.net for a while; Your border serving your BBNcircuit is reporting address unreachable for 198.32.4.0/24. Since I cannot see your annoucements through PBI, I have no other path into ISI.
Are you currently having issues with your IGP? Or is there a reason why BBN customers cannot reach EP.net?
Thanks Ahead for Fixing this,
Joe
--- Joe Wood Flying Crocodile, Inc. Senior Network Engineer Network Operations <joew@flyingcroc.net> 2001 Sixth Avenue, Suite 3302 206.269.0190 Seattle WA 98121
Joe, a LOT of providers don't accept 198.32.4.0/24. We see it on 2 out of four paths. The other two providers are filtering it. On Wed, 21 Mar 2001, Joe Wood wrote:
Hello (Hopefully to someone at ISI).
I have been having issues reaching EP.net for a while; Your border serving your BBNcircuit is reporting address unreachable for 198.32.4.0/24. Since I cannot see your annoucements through PBI, I have no other path into ISI.
Are you currently having issues with your IGP? Or is there a reason why BBN customers cannot reach EP.net?
Thanks Ahead for Fixing this,
Joe
--- Joe Wood Flying Crocodile, Inc. Senior Network Engineer Network Operations <joew@flyingcroc.net> 2001 Sixth Avenue, Suite 3302 206.269.0190 Seattle WA 98121
--- John Fraizer EnterZone, Inc
folks are encouraged to filter as they see fit. if folks would like to establish direct peering, please let me know.
Joe, a LOT of providers don't accept 198.32.4.0/24. We see it on 2 out of four paths. The other two providers are filtering it.
On Wed, 21 Mar 2001, Joe Wood wrote:
Hello (Hopefully to someone at ISI).
I have been having issues reaching EP.net for a while; Your border serving your BBNcircuit is reporting address unreachable for 198.32.4.0/24. Since I cannot see your annoucements through PBI, I have no other path into ISI.
Are you currently having issues with your IGP? Or is there a reason why BBN customers cannot reach EP.net?
Thanks Ahead for Fixing this,
Joe
--- Joe Wood Flying Crocodile, Inc. Senior Network Engineer Network Operations <joew@flyingcroc.net> 2001 Sixth Avenue, Suite 3302 206.269.0190 Seattle WA 98121
--- John Fraizer EnterZone, Inc
On Wed, Mar 21, 2001 at 10:07:33PM +0000, bmanning@vacation.karoshi.com wrote:
[John Fraizer]
Joe, a LOT of providers don't accept 198.32.4.0/24. We see it on 2 out of four paths. The other two providers are filtering it.
folks are encouraged to filter as they see fit. if folks would like to establish direct peering, please let me know.
It's often considered a Good Thing to not hear the networks of exchange points from peers/others. A conservative approach is to filter out announcements of EPs to which you are actually connected rather than all you can find; some folks just squash 198.32/16 and any other addresses they can find. It is worth noting that none of 198.32.2/24, 198.32.4/24 or 198.32/16 have IRR entries; that might adversely affect reachability in defaultless IRR-strict networks. Cheers, Joe -- Joe Provo Voice 508.486.7471 Director, Internet Planning & Design Fax 508.229.2375 Network Deployment & Management, RCN <joe.provo@rcn.com>
participants (4)
-
bmanning＠vacation.karoshi.com -
Joe Provo -
Joe Wood -
John Fraizer