Jon Lewis <[EMAIL PROTECTED]> writes:
> You might consider something like bgp maxas-limit 75 to exchange that
> log message for the less scarey
> Oct 22 06:34:09: %BGP-6-ASPATH: Long AS path ...
>
> As an added bonus, you ignore their route while they're playing such
> games.
Which is exactly wh
Sounds like some automated scripts that didn't do any sanity checking.
Process pulls the current BGP table, checks for the longest path, and
then prepends the AS that many times to guarantee everyone takes the
other path. But if two ISPs are doing this, well, the paths get longer
and longer. I ju
Jon Lewis said the following on 23/10/08 12:39:
> Is there something silly going around? I doubt I'm the only one
> noticing these being triggered by our generous maxas-limit setting.
>
> Oct 9 23:01:46: %BGP-6-ASPATH: ... 27754 27754 27754 ...
> Oct 17 11:10:40: %BGP-6-ASPATH: ... 43413 43413 4
Not using that prepended route is exactly what the point of the prepend
is, so that's not "punishment".
It may, in fact, be exactly what they're trying to get you to do.
>-Original Message-
>From: Jon Lewis [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, October 22, 2008 8:17 PM
>To: Mike Le
On Wed, Oct 22, 2008 at 3:16 PM, Ernie Rubi <[EMAIL PROTECTED]> wrote:
> Hi folks,
>
> So I'm a network engineer and a law student and have decided to write a
> short note for one of our International Law classes based on UDRP and ICANN
> issues.
>
> I'd like to request input from the community as
Except when their primary path goes away and relatively few networks
install the prepended route. It's all conjecture, but I like the 'in
effort to defeat local pref' option.
On Thu, Oct 23, 2008 at 10:53 AM, Tomas L. Byrnes <[EMAIL PROTECTED]> wrote:
> Not using that prepended route is exactly w
* Suresh Ramasubramanian:
> For the "mailops is not operational" folks.. it involves parsing dns
> txt records, so .. well, please grit your teeth and read on, this gets
> interesting
By the way, BIND 9 is supposed to throw away this type of malformed
RDATA, so if you run BIND 9, this is only rel
Ernie,
Martin's suggestions (go rummage around the Berkman dump) is a good one.
Not too far from you is someone who actually is a leading figure in this
somewhat arcane field, Prof. Froomkin at Miami Law. There've been a
couple of papers over the years that are good sources too. Drop a note
t
Hi,
If there are any long haul Ethernet providers on the list, can you
contact me offlist?
I'm looking for 10GE from Dallas to Ashburn.
Thanks.
-Konstantin
On Fri, 24 Oct 2008, Philip Smith wrote:
Jon Lewis said the following on 23/10/08 12:39:
Is there something silly going around? I doubt I'm the only one
noticing these being triggered by our generous maxas-limit setting.
Oct 9 23:01:46: %BGP-6-ASPATH: ... 27754 27754 27754 ...
Oct 17 11:10:4
Thanks,
A further question, is it mandatory for all the aggregated information
be appended at the AS path, is it possible for some aggregations do
not propagate outside? By this, I mean some ASes completely conceal
their aggregated ASes when propagation.
thanks a lot.
On Wed, Oct 22, 2008 at 10:3
Nathan Ward wrote:
...
> 2) If Teredo relays are deployed close to the service (ie. content,
> etc.) then performance is almost equivalent to IPv4. 6to4 relies on
> relays being close to both the client and the server, which requires
> end users' ISPs to build at least *some* IPv6 infrastructure, m
On 10/23/08 6:39 PM, "Tony Hain" <[EMAIL PROTECTED]> wrote:
> A properly
> implemented client will do the longest prefix match against that set, so a
> 6to4 client will go directly to the content provider's 6to4 router, while a
> native client will take the direct path.
Not quite.
Say the ser
In message <[EMAIL PROTECTED]>, Alain Durand writes
:
>
>
>
> On 10/23/08 6:39 PM, "Tony Hain" <[EMAIL PROTECTED]> wrote:
>
> > A properly
> > implemented client will do the longest prefix match against that set, so a
> > 6to4 client will go directly to the content provider's 6to4 router, whi
On 23 Oct 2008, at 18:46, Alain Durand wrote:
On 10/23/08 6:39 PM, "Tony Hain" <[EMAIL PROTECTED]> wrote:
A properly
implemented client will do the longest prefix match against that
set, so a
6to4 client will go directly to the content provider's 6to4 router,
while a
native client will t
Alain Durand wrote:
On 10/23/08 6:39 PM, "Tony Hain" <[EMAIL PROTECTED]> wrote:
A properly
implemented client will do the longest prefix match against that set, so a
6to4 client will go directly to the content provider's 6to4 router, while a
native client will take the direct path.
16 matches
Mail list logo
