[sdnog] using RIPE atlas to check which DNS root your resolver prefers.

[Nishal Goburdhan]

> On 29 Dec 2014, at 09:30, Hiba Eltigani <higba6 at gmail.com> wrote:
> 
> I don't think it is something imposed by SIXP, it is most likely operators' internal policy to use community for their routing polices but M.Osama can give more info ;).
> 

well, that's easy to prove ... :-)

as operator #1, I can confirm that we are not sending routes with no-export attached. 

as operator #2, Tarig is seeing this.  either he is adding it, or, it's being done by the network in the middle (in this case the SIXP). 

Tarig, are you adding no-export ? 




> --n.
> 
>> On Dec 29, 2014 9:45 AM, "Nishal Goburdhan" <nishal at controlfreak.co.za> wrote:
>> On 29 Dec 2014, at 07:36, Tarig Yassin <tariq198487 at hotmail.com> wrote:
>> > > if you want to send me the particular communities that you think that the KRT node is originating that needs to be stripped
>> >
>> > I mean "no-export" community
>> >
>> > BGP routing table entry information of 192.203.230.0/24:
>> >  "Community:no-export"
>> 
>> 
>> hrm..that's odd!
>> i can confirm that this is not something that we are doing  (as i explained;  it can't be anyway, since there's a middle ASN between us...)
>> so it's got to be something that the L3 IXP operator is doing.
>> 
>> this is also very wrong;  basically, it's imposing a routing policy that the route originator (in this case, PCH) did not intend.
>> now the ET story makes more sense (also;  this is still bad for your customer).   so yes, we definitely need to get this removed.
>> 
>> perhaps m.osama can help explain ?
>> 
>> --n.
>> _______________________________________________
>> Sdnog mailing list
>> Sdnog at sdnog.sd
>> http://lists.sdnog.sd/mailman/listinfo/sdnog
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sdnog.sd/pipermail/sdnog/attachments/20141229/00d5a9dd/attachment.html>