changed: *j...@relianceglobalcom.com* 20091117
source: RADB
Best Regards, João Butzke.
Em 13/09/2017 08:05, Matthew Huff escreveu:
It appears that Reliance Globalcom (AS6157) added an RADB entry for our prefix
(129.77.0.0/16) when we were a peer of theirs years ago, and it was never
2017, at 7:10 AM, Job Snijders wrote:
>
> On Wed, 13 Sep 2017 at 13:08, Matthew Huff wrote:
>
>> It appears that Reliance Globalcom (AS6157) added an RADB entry for our
>> prefix (129.77.0.0/16) when we were a peer of theirs years ago, and it
>> was never removed wh
On Wed, 13 Sep 2017 at 13:08, Matthew Huff wrote:
> It appears that Reliance Globalcom (AS6157) added an RADB entry for our
> prefix (129.77.0.0/16) when we were a peer of theirs years ago, and it
> was never removed when we ended the relationship. We are ASN 14607.
>
> I&#x
It appears that Reliance Globalcom (AS6157) added an RADB entry for our prefix
(129.77.0.0/16) when we were a peer of theirs years ago, and it was never
removed when we ended the relationship. We are ASN 14607.
I've reached out to their support, but does anyone have a suggestion on
.236)
> Origin IGP, localpref 100, valid, external, best
> Community: 7018:2000 7018:34011
>
>
> Thanks,
>
> Chuck
>
>
> -Original Message-
> From: Courtney Smith [mailto:courtneysm...@comcast.net]
> Sent: Tuesday, December 11, 2012 5:38 PM
On Tue, Dec 11, 2012 at 10:17 AM, Christopher Morrow
wrote:
> On Tue, Dec 11, 2012 at 10:00 AM, Eric Krichbaum wrote:
>> Absolutely. I'd rather see it done responsibly. It's hard to get rid of
>> bad data/incorrect data/stale data and it shouldn't be. If done properly,
>> it would be much frie
>
> Anyone,
>
>
>
>Hopefully this is a simple question about RADB. I'm
> supporting a small wireless ISP, they just recently added a second upstream
> connection - Charter (AS 20115). The IP space was originally issued by the
> other upstream Windstream (AS 7029). Looking at
On Tue, Dec 11, 2012 at 10:11 AM, Chuck Church wrote:
> -Original Message-
>>From: Eric Krichbaum [mailto:e...@telic.us]
>>Sent: Tuesday, December 11, 2012 8:31 AM
>>To: 'Chuck Church'; nanog@nanog.org
>>Subject: RE: RADB entry
>
>>While not
opher.mor...@gmail.com] On
> Behalf Of Christopher Morrow
> Sent: Tuesday, December 11, 2012 8:51 AM
> To: Eric Krichbaum
> Cc: Chuck Church; nanog@nanog.org
> Subject: Re: RADB entry
>
> On Tue, Dec 11, 2012 at 8:31 AM, Eric Krichbaum wrote:
>> The origin being entered by a
-Original Message-
>From: Eric Krichbaum [mailto:e...@telic.us]
>Sent: Tuesday, December 11, 2012 8:31 AM
>To: 'Chuck Church'; nanog@nanog.org
>Subject: RE: RADB entry
>While not 100% accurate, it is very common. The origin being entered by a
provider as their o
ssage-
From: christopher.mor...@gmail.com [mailto:christopher.mor...@gmail.com] On
Behalf Of Christopher Morrow
Sent: Tuesday, December 11, 2012 8:51 AM
To: Eric Krichbaum
Cc: Chuck Church; nanog@nanog.org
Subject: Re: RADB entry
On Tue, Dec 11, 2012 at 8:31 AM, Eric Krichbaum wrote:
> The origi
On Tue, Dec 11, 2012 at 8:31 AM, Eric Krichbaum wrote:
> The origin being entered by a
> provider as their own allows them to add the prefix (and have it accepted by
> anyone who filters them by prefix generated) without being forced to add a
> downstream (and downstream's downstreams) AS to thei
huckchu...@gmail.com]
Sent: Tuesday, December 11, 2012 7:23 AM
To: nanog@nanog.org
Subject: RADB entry
Anyone,
Hopefully this is a simple question about RADB. I'm
supporting a small wireless ISP, they just recently added a second upstream
connection - Charter (AS
Anyone,
Hopefully this is a simple question about RADB. I'm
supporting a small wireless ISP, they just recently added a second upstream
connection - Charter (AS 20115). The IP space was originally issued by the
other upstream Windstream (AS 7029). Looking at a few resources s
14 matches
Mail list logo
