<div dir="ltr">Dear Frank,<br><div>I asked customer to add their own AS in side their AS-SET: <a href="https://apps.db.ripe.net/db-web-ui/query?searchtext=AS-ASIATECH">https://apps.db.ripe.net/db-web-ui/query?searchtext=AS-ASIATECH</a></div><div>But the problem exist and that prefix is filtered: <a href="https://members.tehran-ix.ir/lg/rs1-ipv4/routes/protocol/pb_as43754_vli26_ipv4">https://members.tehran-ix.ir/lg/rs1-ipv4/routes/protocol/pb_as43754_vli26_ipv4</a></div><div><br></div><div><table class="gmail-table gmail-table-striped gmail-text-monospace" style="box-sizing:inherit;border:0px solid rgb(218,225,231);border-collapse:collapse;width:766px;margin-bottom:1rem;color:rgb(33,37,41);font-size:14px;font-family:SFMono-Regular,Menlo,Monaco,Consolas,"Liberation Mono","Courier New",monospace"><tbody style="box-sizing:inherit;border:0px solid rgb(218,225,231)"><tr style="box-sizing:inherit;border:0px solid rgb(218,225,231);background-color:rgba(0,0,0,0.05)"><td style="box-sizing:inherit;border-width:1px 0px 0px;border-style:solid;border-color:rgb(222,226,230) rgb(218,225,231) rgb(218,225,231);padding:0.75rem;vertical-align:top"><a href="http://185.141.213.0/24">185.141.213.0/24</a></td></tr><tr style="box-sizing:inherit;border:0px solid rgb(218,225,231)"></tr></tbody></table><br class="gmail-Apple-interchange-newline"></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Apr 20, 2020 at 10:35 AM Frank Habicht <<a href="mailto:geier@geier.ne.tz">geier@geier.ne.tz</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Shahab,<br>
<br>
it's better if they (43754) fix the AS-SET to include their own ASN.<br>
That way they will also fix filter generation on their upstream or any<br>
bilateral peer.<br>
Everybody else generating filters from the AS-SET does also not do the<br>
AND, so your suggestion would fix it only for the IXP route servers, not<br>
for the other places.<br>
<br>
Greetings,<br>
Frank<br>
<br>
On 20/04/2020 08:58, Shahab Vahabzadeh wrote:<br>
> Nick,<br>
> I think I find the problem, Customer AS Number (AS43754) must be inside<br>
> AS-SET?!<br>
> They (and Me) thought that only AS numbers behind customers must be there.<br>
> Maybe you can AND it in your queries, Customer AS Number + AS-SET.<br>
> Thanks<br>
> <br>
> On Mon, Apr 20, 2020 at 10:25 AM Shahab Vahabzadeh <<a href="mailto:me@shahabv.com" target="_blank">me@shahabv.com</a><br>
> <mailto:<a href="mailto:me@shahabv.com" target="_blank">me@shahabv.com</a>>> wrote:<br>
> <br>
> Nick,<br>
> Our IRRDB source for all customers is RIPE.<br>
> Thanks<br>
> <br>
> On Mon, Apr 20, 2020 at 10:23 AM Shahab Vahabzadeh <<a href="mailto:me@shahabv.com" target="_blank">me@shahabv.com</a><br>
> <mailto:<a href="mailto:me@shahabv.com" target="_blank">me@shahabv.com</a>>> wrote:<br>
> <br>
> Dear Nick,<br>
> Now for customer Asiatech (AS43754) we have IPv4 and IPv6<br>
> Peering Macro which is AS-ASIATECH.<br>
> And also as I check the ripe database there is a valid route<br>
> object for <a href="http://185.141.213.0/24" rel="noreferrer" target="_blank">185.141.213.0/24</a> <<a href="http://185.141.213.0/24" rel="noreferrer" target="_blank">http://185.141.213.0/24</a>> with<br>
> AS43754 itself.<br>
> So why is there an error for this prefix?<br>
> Thanks<br>
> <br>
> On Sun, Apr 19, 2020 at 1:53 PM Nick Hilliard (INEX)<br>
> <<a href="mailto:nick@inex.ie" target="_blank">nick@inex.ie</a> <mailto:<a href="mailto:nick@inex.ie" target="_blank">nick@inex.ie</a>>> wrote:<br>
> <br>
> Shahab Vahabzadeh wrote on 19/04/2020 08:34:<br>
> > You are right but what is your idea about this prefix:<br>
> <a href="http://185.141.213.0/24" rel="noreferrer" target="_blank">185.141.213.0/24</a> <<a href="http://185.141.213.0/24" rel="noreferrer" target="_blank">http://185.141.213.0/24</a>> ?<br>
> > There is a route object in ripe with AS43754 and this AS<br>
> belongs to the<br>
> > customer himself.<br>
> > But again it's filter with two tag: Prefix Filtered,<br>
> Origin AS Filtered<br>
> <br>
> The list of IRRDB prefixes is built using the "IPv4 Peering<br>
> Macro" and<br>
> "IRRDB Source" in the Customer profile.<br>
> <br>
> If the "IPv4 Peering Macro" field is blank, then it uses the AS.<br>
> <br>
> The artisan irrdb:update-prefix-db command uses the bgpq3<br>
> command to<br>
> populate the local database using the peering macro and the<br>
> source list.<br>
> <br>
> The first thing to do is check the information that's going<br>
> into the<br>
> local database.<br>
> <br>
> - you need to check that the "IPv4 Peering Macro" is set to<br>
> what the<br>
> customer specifies<br>
> <br>
> - make sure the irrdb source looks correct. Probably it<br>
> should be set<br>
> to "RIPE".<br>
> <br>
> - you need to make sure that there is a route: object in<br>
> the IRRDB for<br>
> the prefix that you're checking.<br>
> <br>
> You can find out what bgpq3 thinks by calling it directly<br>
> using the<br>
> parameters specified in IXP Manager, e.g. if you've set the<br>
> as-set to be<br>
> blank, it will use the AS itself:<br>
> <br>
> > % bgpq3 -S RIPE AS43754 | grep <a href="http://185.141.213.0/24" rel="noreferrer" target="_blank">185.141.213.0/24</a><br>
> <<a href="http://185.141.213.0/24" rel="noreferrer" target="_blank">http://185.141.213.0/24</a>><br>
> > ip prefix-list NN permit <a href="http://185.141.213.0/24" rel="noreferrer" target="_blank">185.141.213.0/24</a><br>
> <<a href="http://185.141.213.0/24" rel="noreferrer" target="_blank">http://185.141.213.0/24</a>><br>
> > %<br>
> <br>
> This means that there's a route: object in the RIPE IRRDB,<br>
> which is a<br>
> good start.<br>
> <br>
> The next thing would be to check the AS-SET that you're<br>
> using in IXP<br>
> Manager for this customer, along with the IRRDB source list:<br>
> <br>
> > % bgpq3 -S "<IRRDB source list>" <IPv4 peering macro> |<br>
> grep <a href="http://185.141.213.0/24" rel="noreferrer" target="_blank">185.141.213.0/24</a> <<a href="http://185.141.213.0/24" rel="noreferrer" target="_blank">http://185.141.213.0/24</a>><br>
> <br>
> If this comes up blank, then you've identified that the<br>
> problem is that<br>
> you're using the wrong IRRDB source, the wrong AS set or<br>
> else that the<br>
> customer hasn't configured their AS set properly.<br>
> <br>
> Nick<br>
> <br>
> <br>
> <br>
> -- <br>
> <br>
> Cheers, Shahab<br>
> <br>
> <br>
> <br>
> -- <br>
> <br>
> Cheers, Shahab<br>
> <br>
> <br>
> <br>
> -- <br>
> <br>
> Cheers, Shahab<br>
> <br>
> _______________________________________________<br>
> INEX IXP Manager mailing list<br>
> <a href="mailto:ixpmanager@inex.ie" target="_blank">ixpmanager@inex.ie</a><br>
> Unsubscribe or change options here: <a href="https://www.inex.ie/mailman/listinfo/ixpmanager" rel="noreferrer" target="_blank">https://www.inex.ie/mailman/listinfo/ixpmanager</a><br>
> <br>
_______________________________________________<br>
INEX IXP Manager mailing list<br>
<a href="mailto:ixpmanager@inex.ie" target="_blank">ixpmanager@inex.ie</a><br>
Unsubscribe or change options here: <a href="https://www.inex.ie/mailman/listinfo/ixpmanager" rel="noreferrer" target="_blank">https://www.inex.ie/mailman/listinfo/ixpmanager</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><br></div><div>Cheers, Shahab</div></div></div></div></div>