Re: BTinternet problems?
Mike wrote: We're receiving multiple complaints about problems reaching anything @bt. Is anyone else experiencing this? GrrrThree days later, BT is now telling their customers that somehow, this is our fault. I find it rather odd that everyone in the world can reach us, *except* BT customers, yet it is our fault. You appear to be excessively deaggregating your space. Perhaps they are doing the responsible thing by filtering it? As announced, 13345 has 92 prefixes originated. After aggregation, there are 44 prefixes. There appear to be a couple of holes which you aren't announcing, which would further reduce this to 38 (after aggregation.) The space from the Colorado Internet Cooperative Association seems to be somewhat haphazard leading to the bulk of the remainder, and they aren't originating 207.174.0.0/16 at all, which may lead to issues. In this day and age of many people not doing the right thing, it is likely that one only see's the effects when looking at someone actually doing the right thing. I'ld suggest cleaning up your announcements and seeing if the problem persists. If nothing else, you become a part of the solution.
Re: BTinternet problems?
[EMAIL PROTECTED] wrote: You appear to be excessively deaggregating your space. Perhaps they are doing the responsible thing by filtering it? I had a /20 from which BT was unreachable, and a /24 working just fine, so this seems doubtful, unless they are doing it to be spiteful and punitive alone. I say had because we have since withdrawn almost all announcements that AS7018 was learning from AS19694 and temporarily fixed the problem. It still exists, and it is clear now that the problem lies somewhere between AS7018 and AS2856. AS7018 says that my traceroutes are confusing to them, so I have pretty much given up hope of ever seeing a resolution to this. As announced, 13345 has 92 prefixes originated. After aggregation, there are 44 prefixes. Policy for most of those were set prior to my involvement with BGP here. I have managed to prevent the (otherwise forgone) deaggregation of 204.188.96.0/20 and 199.45.236.0/22 since my involvement at this level. I am also working to prepare an application for PI space from ARIN and the end result will be to reduce our total # of prefixes. Due to topology, aggregation of the remainder at this time would require several hundred clients to renumber immediately. Yes, I know this sucks. Yes, I am working towards a solution. No, it isn't going to happen tomorrow. Yes, I feel the pain every time I look at what we advertise. Mike
Re: BTinternet problems?
On Thu, 19 Jun 2003, Mike wrote: I have sent mail to every address @BT that looks like it might possess clue, to no avail. This is a general plea for help- if anyone has an idea of how I might resolve this, I would be very grateful... Point the customer at www.traceroute.org? HTH, Rich
Re: BTinternet problems?
Mike wrote: We're receiving multiple complaints about problems reaching anything @bt. Is anyone else experiencing this? GrrrThree days later, BT is now telling their customers that somehow, this is our fault. I find it rather odd that everyone in the world can reach us, *except* BT customers, yet it is our fault. NB, this only affects some of our address space (I received one confirmation report that another AS is also affected by this). I have tried four different peers, and it doesn't make a difference where I send outbound packets. I have sent mail to every address @BT that looks like it might possess clue, to no avail. This is a general plea for help- if anyone has an idea of how I might resolve this, I would be very grateful... From inside BT, looking at one of our clients colo'd servers: C:\WINDOWS\Desktoptracert www.indianmatches.com Tracing route to www.indianmatches.com [204.144.133.198] over a maximum of 30 hops: 1 192 ms 110 ms27 ms rase4nrp4.kingston.broadband.bt.net [217.32.11.81] 214 ms14 ms13 ms 217.41.195.2 327 ms14 ms14 ms core1-pos4-1.kingston.ukcore.bt.net [62.6.40.193] 414 ms13 ms14 ms core1-pos5-1.ilford.ukcore.bt.net [195.99.120.198] 514 ms14 ms13 ms transit1-pos3-0.ilford.ukcore.bt.net [194.72.20.226] 696 ms82 ms82 ms transit2-pos7-0.newyork.ukcore.bt.net [194.72.20.154] 7 t2c2-ge6-2.us-nyb.concert.net [166.49.150.29] reports: Destination host unreachable. Trace complete Well, no duh Going to www.concert.net I read Concert, the ATT and BT global communications venture, was legally closed on 1 April 2002. Ok, so WTF are they sending packets for us that way then??? Mike
Re: BTinternet problems?
Mike wrote: I have sent mail to every address @BT that looks like it might possess clue, to no avail. This is a general plea for help- if anyone has an idea of how I might resolve this, I would be very grateful... On a hunch, I shut down one of our peering sessions which was passing our routes to ATT. Suddenly things seem to be working again... Thanks to all who've responded, I think we have a better idea of where the problem is now. Mike
Re: BTinternet problems?
BT operate 2856 in the UK, and 5400 internationally 5400 used to be concert which was a BT/ATT venture which is now solely run by BT under their brand - hence I guess why the msg on concert.net Email contact sent offlist.. Steve On Thu, 19 Jun 2003, Mike wrote: Mike wrote: We're receiving multiple complaints about problems reaching anything @bt. Is anyone else experiencing this? GrrrThree days later, BT is now telling their customers that somehow, this is our fault. I find it rather odd that everyone in the world can reach us, *except* BT customers, yet it is our fault. NB, this only affects some of our address space (I received one confirmation report that another AS is also affected by this). I have tried four different peers, and it doesn't make a difference where I send outbound packets. I have sent mail to every address @BT that looks like it might possess clue, to no avail. This is a general plea for help- if anyone has an idea of how I might resolve this, I would be very grateful... From inside BT, looking at one of our clients colo'd servers: C:\WINDOWS\Desktoptracert www.indianmatches.com Tracing route to www.indianmatches.com [204.144.133.198] over a maximum of 30 hops: 1 192 ms 110 ms27 ms rase4nrp4.kingston.broadband.bt.net [217.32.11.81] 214 ms14 ms13 ms 217.41.195.2 327 ms14 ms14 ms core1-pos4-1.kingston.ukcore.bt.net [62.6.40.193] 414 ms13 ms14 ms core1-pos5-1.ilford.ukcore.bt.net [195.99.120.198] 514 ms14 ms13 ms transit1-pos3-0.ilford.ukcore.bt.net [194.72.20.226] 696 ms82 ms82 ms transit2-pos7-0.newyork.ukcore.bt.net [194.72.20.154] 7 t2c2-ge6-2.us-nyb.concert.net [166.49.150.29] reports: Destination host unreachable. Trace complete Well, no duh Going to www.concert.net I read Concert, the ATT and BT global communications venture, was legally closed on 1 April 2002. Ok, so WTF are they sending packets for us that way then??? Mike
BTinternet problems?
Yes, it appears they had problems: Power failure leads to BTo blackout By Tim Richardson Posted: 17/06/2003 at 11:46 GMT http://theregister.com/content/22/31248.html
