In a message written on Fri, Aug 18, 2006 at 03:02:45PM -0400, Richard A
Steenbergen wrote:
> So, lets kick this Friday off right... I don't suppose anybody has noticed
> that Wikipedia is being blackholed by Cogent, and that it seems to be
> intentional? :)
Maybe they don't like: http://en.wik
Seeing as this has been going on for over 2h30m, no one can seem to get
ahold of any live bodies who can fix it, and the emails about it to the
noc contacts have gone unanswered, I'm reduced to trying the old public
embarassment approach...
Would Cox please stop announcing 128.0.0.0/1. Thanks.
On Fri, Aug 18, 2006 at 09:09:59PM +, Christopher L. Morrow wrote:
>
> On Fri, 18 Aug 2006, Geoffrey Pan wrote:
>
> > This space has been assigned to the same location, facility for years.
> >
>
> same location/facility doesn't mean that that place/people/thing still has
> authority to rout
Can someone from Cogent please contact me off list regarding to this
issue. Thank you.
Geoffrey Pan
RHCE, CISSP, CISM
gpancheetaweb.com
Christopher L. Morrow wrote:
same location/facility doesn't mean that that place/people/thing still has
authority to route the PA block... Like say the decided to stop having
Cogent as a provider? or stopped payments to Cogent? or some other sort of
snafu...
According to the lead developer, br
On Fri, 18 Aug 2006, Geoffrey Pan wrote:
> This space has been assigned to the same location, facility for years.
>
same location/facility doesn't mean that that place/people/thing still has
authority to route the PA block... Like say the decided to stop having
Cogent as a provider? or stopped
This space has been assigned to the same location, facility for years.
The blocks affected that I know of are..
207.142.131.0/24 -
207.142.136.0/24
Are all of them being reported as that now?
so.. is the problem that wikipedia's ip address is in a block of PA space
of Cogent's and they f
On Fri, 18 Aug 2006, Jeremy Chadwick wrote:
>
> Looks like some others may have noticed...
>
> 207.142.131.0/24 *[BGP/170] 00:26:46, localpref 100
> AS path: 701 3356 30217 I
so.. is the problem that wikipedia's ip address is in a block of PA space
of Cogent's and they f
Looks like some others may have noticed...
207.142.131.0/24 *[BGP/170] 00:26:46, localpref 100
AS path: 701 3356 30217 I
--
| Jeremy Chadwick jdc at parodius.com |
| Parodius Networkinghttp://www.parodius.com/ |
| U
Supposedly Cogent is working on this - I have space on this block
207.142.131.0/21 ( I believe is the allocation) which includes wiki,
miranda
Can someone on Cogent please comment on this . Thank you.
Geoffrey Pan
RHCE, CISSP, CISM
gpancheetaweb.com
Richard A Steenbergen wrote:
So, lets
On Fri, Aug 18, 2006 at 03:02:45PM -0400, Richard A Steenbergen wrote:
> So, lets kick this Friday off right... I don't suppose anybody has noticed
> that Wikipedia is being blackholed by Cogent, and that it seems to be
> intentional? :)
I'm not able to reach 207.142.136.174 (also via Cogent) e
So, lets kick this Friday off right... I don't suppose anybody has noticed
that Wikipedia is being blackholed by Cogent, and that it seems to be
intentional? :)
--
Richard A Steenbergen <[EMAIL PROTECTED]> http://www.e-gerbil.net/ras
GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF
On Aug 18, 8:31am [EMAIL PROTECTED] wrote:
> This isnt an intellectual excercise, its something that operationaly
> affects me. Perhaps it has, is, or will affect any of the operators who
> subscribe to this list.
>
> Since I may have to go to bat against the vendor on this one, I thought
> I
This is an automated weekly mailing describing the state of the Internet
Routing Table as seen from APNIC's router in Japan.
Daily listings are sent to [EMAIL PROTECTED]
For historical data, please see http://thyme.apnic.net.
If you have any comments please contact Philip Smith <[EMAIL PROTECTED
Danny McPherson wrote:
On Aug 17, 2006, at 10:57 PM, Joe Maimon wrote:
If A tries to peer with B, and B sends a BGP capability 64 to A, if A
does not support that capability what would proper and/or reasonable
behavior for A be?
Speaker A MAY send a NOTIFICATION message with Open
This report has been generated at Fri Aug 18 21:44:55 2006 AEST.
The report analyses the BGP Routing Table of an AS4637 (Reach) router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/as4637 for a current version of this report.
Recent Table Hist
Copies of this report are mailed to:
nanog@merit.edu
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
On 17 Aug 2006, at 21:45, Pekka Savola wrote:
[...]
Enhancement Requests haven't gotten through, but maybe gripes on
nanog will :-(
IME, griping about something on a mailing list, while typically
getting you an email from a techie at the company concerned
(especially if the gripe was fero
On Aug 17, 2006, at 10:57 PM, Joe Maimon wrote:
If A tries to peer with B, and B sends a BGP capability 64 to A, if
A does not support that capability what would proper and/or
reasonable behavior for A be?
Speaker A MAY send a NOTIFICATION message with Open
Message Error/Error Subcode "U
19 matches
Mail list logo
