Is there already support for 4 byte ASN? Since we received the email from ARIN I have done a little research and I see nothing stating that Mikrotik is already compatible with 4 byte ASNs. If it is not supported, is there any future version that is being planned to support this, and will it be released on the 2.9 and v3 code, or will it strictly be v3? If it is already supported, starting at what version was it supported?
If it will be added then only on v3
Have anyone confirmed that 32 bit ASN’s are working in v3? I looks like the field will accept a xxxxx.xxxxx formatted asn, but does it work?
Thanks,
MM
32 bit ASNs are available in routing-test package
it is mandatory so it must be added to routing package too!
please MT work in this way.
Regards
Ros
New features are added only to routing-test.
when routing-test will be metged into the stable?
regards
v4.0beta1 changelog says:
What’s new in 4.0beta1:
*) added support for MetaROUTERs;
*) all test packages are regular ones;
*) console - can mix named and unnamed arguments, can use names for unnamed
argument values. For example all of the following commands are
accepted now:
/ping 10.11.12.13 count=4
/ping address=10.11.12.13 count=4
/ping count=4 10.11.12.13
… so wait ~1,5 year, and 4.0 release will be there =)
nice thing, they don’t seems to do business with it.
Ros.
So you don’t see that this is a joke?
well… how long did it take to release v3 final? =)
p.s. rpingar, what supresses you from using routing-test package?
p.p.s. maybe it’s better to rename ‘-test’ to something like ‘-next’? this ‘test’ scares people =)
or maybe routing-improved 
I was reading up on this yesterday… as I understand it starting this month the RIRs will be assigning 4 byte ASN numbers to fill requests. I don’t know if thats true, but if it is, MT can’t wait 1.5 years to get it implemented in the base routing package. Who knows … probably scare tactics at work here : )
The regular package contains tested and working features. I we start adding new stuff there, there will be people who will complain that we break stability in favor of cutting edge stuff … that’s exactly where the test package comes in. It’s working perfectly fine, sometimes even better than the regular one. And only this package gets the latest features, until they are done implementing and are working fine
our local rir ripe ncc is giving out 4byte asns by default since 1.1.2009. only in this case i would definitely vote for this feature in the normal routing-package, as when using mt as a router with bgp you won’t be able to reach new networks and this is pretty bad, as it is not only a cosmetic but more a business affecting problem.
and we are not talking about a small percentage of mt-customers, everybody who uses bgp (and that should almost every wisp with more than 1000 customers, only if used for multihoming) is affected, even if they do not know it 
but as soon as problems arise and techs from other isps debug those problems with them, they will soon find this thing and blame mt for not implementing something that should be supported since years. i know this is also the case for quagga (who integrated the patch about a year ago) and also cisco and juniper are not supporting 4byte asns in every aspect of their software. but it is supported since years.
i know backporting features is not a good thing, but backporting something that is immediately needed and that should be integrated since years is worth the work.