<HTML>
<HEAD>
<TITLE>RtConfig in IRRToolset v5.0.0</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Hi All,<BR>
<BR>
Not sure whether I should be writing to this list or a bug list somewhere.<BR>
<BR>
I’ve been moving over to IRRToolsetv5 this past week and while the coding is very much improved, I have noticed some strange behaviour. While peval still works fine rtconfig seems to treat the AS-SET AS-4739 as empty and returns ANY/NOT ANY on the prefixes. Not sure whether it is parsing it as a non-existent AS rather than an AS-SET. Change the AS-SET to another name, such as AS4739:AS-CUSTOMER and all works fine.<BR>
<BR>
The other thing that comes to mind is that IPv6 prefixes are not easily adjustable. If I have a /32 and allow a customer /40 upto /48 to advertise rtconfig either ignores it or seems to go away calculating every subprefix in IPv6 address space. I may want to allow customers to advertise upto /64 internally providing they tag appropriately. Also wondering whether to create blackhole routes so that even /128s could be advertised internally.<BR>
<BR>
Basically I would like similar policy functionality in IPv6 space as IPv4 but the current rendition of rtconfig doesn’t want to parse it properly and only returns the original /32 prefix eg <BR>
<BR>
from AS65518 at 2001:388:1::83 action community.append(7575:2131);<BR>
accept AS6262^0-64 AND <^PeerAS+$>;<BR>
<BR>
Regards<BR>
<BR>
Bruce<BR>
-- <BR>
street address: AARNet, POD 3, 20 Dick Perry Ave, Kensington, WA 6151, Australia <BR>
m. 0408 882 390 t. +61 8 9289 2212 e. <FONT COLOR="#0000FF"><U><a href="bruce.morgan@aarnet.edu.au">bruce.morgan@aarnet.edu.au</a></U></FONT> <BR>
w. www.aarnet.edu.au <BR>
<BR>
<BR>
</SPAN></FONT>
</BODY>
</HTML>