all of those can be put in place using scripting and ros api right now 
But it’s still not TR-069 isn’t it . Scripting is per device , and time consuming . Consider managing thousands of RouterBoard , Scripting is good if you have a few CPE , but when your talking about mass deployment you need TR-069, no help desk is going to take a support call and put a customer on hold while you script something up . 
you’re right, it’s not TR-069. scripting is a lot more powerful stuff.
of course it needs a head start of coding, it’s not something out of the box. but auto-provisioning can be
done using different approaches.
no one stops us to actually create a similar environment/ecosystem with ROS scripting, to provide the same
look & feel as TR-069. if you need it right now, let’s make one. when you have to deal with 1000s of devices
it (the home-brew approach) will be a lot more efficient than doing everything manually while waiting for MTIK to implement TR-069
BTW, i would not compare the average TR-069 governed CPE feature set to something that ROS offers right now.
That is just re-inventing the wheel. Why develop new ecosystem when one already exists . ISP already have TR-069 asset in the business and interfaced with OSS/BSS systems, re-inventing (home-brew) is not feasible.
At the end of the day , this is a feature request , end user should have the option to choose what best fits the network and business. TR-069 is my feature request for V7.
fair enough
Not sure this one has been mentioned, but I really need fastpath in VPLS endpoints for VPLS faster than 1Gbps.
I’ve had to switch back to basic OSPF routing to obtain the 8-9Gbps speeds i used to have before implementing end to end MPLS/VPLS.
Small thing: for multiple WAN envoronments it should exists some kind of predefined policy or on/off switch, about incomming and outgoing traffic. When something goes in from WAN1 should go out by WAN1, when something goes in frome WAN2 should go out by WAN2 and so on…
It’s easy. Mangle the connection and route the packets back according to the routing marks.
When combining PPPoE Client WAN and static IP address WAN it’s not so easy, look
/ip firewall mangle
add action=mark-connection chain=prerouting comment=“WAN1 FWD” in-interface=ppp-WAN1 new-connection-mark=wan1_conn passthrough=no
add action=mark-routing chain=prerouting comment=“WAN1 FWD” connection-mark=wan1_conn new-routing-mark=to_wan1 passthrough=no
add action=mark-connection chain=prerouting comment=“WAN2 FWD” in-interface=ppp-WAN2 new-connection-mark=wan2_conn
add action=mark-routing chain=prerouting comment=“WAN2 FWD” connection-mark=wan2_conn new-routing-mark=to_wan2 passthrough=no
add action=mark-connection chain=input comment=“WAN1 IN OUT” in-interface=ppp-WAN1 new-connection-mark=wan1_conn
add action=mark-routing chain=output comment=“WAN1 IN OUT” connection-mark=wan1_conn new-routing-mark=to_wan1 passthrough=no
add action=mark-connection chain=input comment=“WAN2 IN OUT” in-interface=ppp-WAN2 new-connection-mark=wan2_conn
add action=mark-routing chain=output comment=“WAN2 IN OUT” connection-mark=wan2_conn new-routing-mark=to_wan2 passthrough=no
/ip route
add check-gateway=ping distance=2 gateway=ppp-WAN1 routing-mark=to_wan1
add check-gateway=ping distance=3 gateway=ppp-WAN2 routing-mark=to_wan2
add check-gateway=ping comment=MAIN distance=1 gateway=10.1.0.1
add distance=1 dst-address=10.0.0.11/32 gateway=eth6_WAN1
add distance=1 dst-address=10.0.0.12/32 gateway=eth7_WAN2
… and when I tried to set up routing mark for address 10.1.0.1, the route fails.
Could you help me please?
Also usable will be some kind of checkbox for hairpin NAT in NAT rule creation.
Hi,
Maybe very old request, but… Metarouter support on microSD card.
Your problem is that the connection-marking rules need to also have the criteria: connection-mark=no-mark
If not, then you can re-mark connections and break the routing policy.
Login by ssh key in WinBox will be really helpfull too.
Requesting IPv6 policy based routing.
Dear MT Team
I think User manager is most power full tool in future because every isp need radius with accounting, country wise payment gateway, sms api integration, plans flexibility etc.
So Kindly improve in further upcoming updates.
Hello!
802.11ad cards support, and GPS syncing would be great!
Ovpn tls-auth and improved ovpn client in general so the connection compatibility is better..
These functions need definitely. And they need not only to us but also to you - mikrotik team, for that would have a more competitive product and a more extensive sales geography. I think when you had MUM tour in Asia have often been asked about the ISIS protocol. Oh Asians very love it
AS & BGP info in Netflow v5 export.
Sent from my SM-G925F using Tapatalk
ISIS is very common in large provider networks the world over. It will be great to see ISIS support in RouterOS.
But for now I will be happy to just see RouterOS v7 beta get released