HE.net will parse out your AS-SET or export: line in AUT-NUM object.
See: http://routing.he.net/algorithm.html
Ideally, best case, you have:
AS-SET including your ASN and your downstream customers (if any)
ROUTE objects created for each prefix with origin set to the correct ASN
AUT-NUM for your ASN with an export line matching your as-set (ie: export: to ANY announce AS65535-AS-SET-OBJECT)
If you haven’t also update PeeringDB.com with your as-set info.
> On Jun 23, 2020, at 1:53 PM, Larry Larsen <[log in to unmask]> wrote:
>
> Good Afternoon;
>
> I am also using ARIN IRR and have setup an AUT-NUM object. I was told that I had to set it up to get updates to appear properly. The problem I have is not with my IP Addresses, but with my customers that have their own blocks and ASNs. HE is still rejecting them. I am not sure how to get the AUT-NUM or Route-Set to work for my customers.
>
> Thank you!
>
> Larry L. Larsen
> Director of Information Technology
> O: 712-271-5920 | F: 712-271-2727
> [log in to unmask]
>
>
> Connect | Empower | Erich
>
> 504 4th Street | Sergeant Bluff, IA 51054
> www.longlines.com
>
> -----Original Message-----
> From: MICE Discuss <[log in to unmask]> On Behalf Of Richard Laager
> Sent: Tuesday, June 23, 2020 1:44 PM
> To: [log in to unmask]
> Subject: [MICE-DISCUSS] IRR Filtering
>
> WARNING!! This message originated from an External Source. Please use proper judgment and caution when opening attachments, clicking links, or responding to this email.
>
> Context: Hurricane Electric is now doing IRR filtering now. My question isn't specific to HE's filtering, but is more about what the best practices are.
>
> I'm looking for clue, on or off list, about whether my AS should have an aut-num object. We already have an as-set object listing our AS as well as those of our transit customers. This as-set's name is listed in PeeringDB. We also already have a route-set object containing route objects for each of our prefixes.
>
> I've looked at some other networks and this approach (list an as-set in
> PeeringDB) seems to be the common case. I am only aware of a couple networks who are using an aut-num object.
>
> I'm cool with creating an aut-num object, but how much do I really need to fill in? That is, do I need to have import/export statements for literally every AS I peer with, or can I just use "from ANY accept ANY"
> and "to ANY announce AS-WIKTEL"? I don't want to create and have to maintain an aut-num that is more complex than necessary. I also don't want to break working traffic with peers who might pick up that aut-num object automatically.
>
> If it matters, I use the ARIN IRR. I was previously using email templates but would intend to switch (which I understand is permanent) to the web interface on my next modification.
>
> --
> Richard
