Re: Prepending with another ASN you don't own

>> this is called path poisoning. an italian friend used it in his phd >> thesis. a few friends and i used it to detect use of default across >> the internet. > > I've done this in the past as a work-around for insufficient BGP > community support. Just prepending the AS I wanted to ignore the

Re: Prepending with another ASN you don't own

On Fri, 16 Dec 2016, Randy Bush wrote: this is called path poisoning. an italian friend used it in his phd thesis. a few friends and i used it to detect use of default across the internet. I've done this in the past as a work-around for insufficient BGP community support. Just prepending

Re: Prepending with another ASN you don't own

On 17 Dec 2016, at 0:13, Job Snijders wrote: There are providers who inspect the AS_PATH's contents and make decisions to reject (ignore) a route announcement or not based on the presence of certain values. +1 --- Roland Dobbins

Re: Prepending with another ASN you don't own

Hi Andrew, On Thu, Dec 15, 2016 at 01:54:34PM -0500, Andrew Imeson wrote: > Is it acceptable to prepend using another networks ASN as long as your > ASN is the last one in the path? I can think of a few scenarios where > this is helpful. Your milage may vary. You risk introducing breakage

Re: Prepending with another ASN you don't own

this is called path poisoning. an italian friend used it in his phd thesis. a few friends and i used it to detect use of default across the internet. but 42 people will scream "that's my AS!" of course, as it is your prefix, that is ASinine :) ramdu

Re: Prepending with another ASN you don't own

Even in that case I believe you should encapsulate between two instances of your own ASN. Your example follows this but the text says only about the last one in the path, while having both last and at least one previous is better since you won't be implying that some other AS has connection to yet