I’ve bought a Huawei e3372h-320 USB LTE modem which doesn’t work with v6.48.2 - known problem reported several times on here. Solutions are a) send it back, b) switch it to stick mode and c) use RouterOS v7. It indeed works fine with RouterOS v7 and at first glance, everything I need it to do seems to work. Switching to stick mode feels like a step backwards.
Couple of questions on v7 - when is the planned launch date of the non-beta version and would I be mad to consider installing it in production?
It will be used at a wedding venue where they want a failover for their payment card readers - they are going cash-only when they are allowed to re-open in the UK. Their leased line connection is very reliable but it would be even worse if the router failed so they couldn’t take payments.
Forget. It’s still alpha quality, even not beta. However, it works quite stable for some basic things. But advanced RouterOS features do not work at all.
Rather a depressing series of posts. My background has never really been on the network side although I was quite adept at Juniper firewalls. So I’ve never got seriously involved in high-end Cisco kit leaving that to my network specialist. Is Cisco or anyone else as programmable as RouterOS? I know most of the Ubiquiti kit I’ve used isn’t anything special configuration wise.
If RouterOS did fade away, I think the world would have lost a bit of a shining star. But then again, not the first time the “best” hasn’t won in the long run
I wouldn’t be too worried about that. I have a fairly complex setup at home and aside from a few things RouterOS v7 is stable enough for me at home - it only recently became stable enough with the beta5 release. Previously I would try to run it and I would get spontaneous reboots every day or sometimes more often. I think we are likely to see a first “stable” release early next year, at the rate things have been going. There isn’t actually that much more they have to do - the biggest missing piece was MPLS which was added in the latest beta. Now they just have to tackle the remaining bugs or features not fully implemented.
That said, like the others, I would not suggest using v7beta in any mission critical situation. So for your particular use case, I would recommend playing it safe and using RouterOS v6 if you can.
As of this post, it has been less than two months since the 7.1beta5 release. The time between betas has been fluctuating, no evidence that development has been slowing down. The important thing is what features they have been adding in the new betas in that amount of time, which is actually quite a bit.
Which is not something I would consider a major feature. At the moment they mostly have to finish filling in the blanks - all of the minor features, or fixing bugs with the major features.
Well, for people like me who need this to be able to use the router to watch tv over a fiber connnection ( using a separate vlan ) it is a real showstopper.
There are two things that are not great with ROSv7:
stability and functionality which is already available in v6. This is the important one and should definitely be worked on first to roll out v7 (sort of a stable release). It will form a good base for further development which was increasingly troublesome in v6 due to it’s aged base
new features (such as IGMP proxy or wave2 wifi) which are important to some users and should be developed eventually. However new features are not IMHO as important as things mentioned in previous bullet.
I certainly hope MT devs are focusing on bullet #1 because any new features without stable base are completely useless to most users.
Yes, this is the same thing that I was pointing out to others. Everybody was asking for new features right away like ipsec VTI and other such things. I do want to see new features, and appreciate the new features like wireguard and VXLAN but the sooner that ROS v7 stabilizes the sooner that we can all benefit from the new kernel.
I do think MikroTik is focusing on #1 but there is a vocal minority of users who seem to want MikroTik to instead be focusing on adding every new kitchen sink feature before the first stable release.
I can agree with this regarding new features, but IGMP-proxy is a feature that allready was in ROS, maybe not a core function so the focus should be on core functionality and stability and then on already existing features and only then on totally new stuff.
I can’t see igmp-proxy taking anywhere near as long as MPLS to implement on ROS 7. I strongly suspect, aside from fixing bugs in MPLS/OSPF/BGP, that those are the sorts of features that are likely to be tackled next.
Have a look at my recent post about getting LTE failover working in a Chateau. You could adapt it for your LTE module. Recursive routing doesn’t work like the Olden Days in ROS7, yet. I needed it to be robust so that it works reliably at a hotel and the staff don’t get a in flap when the WAN goes down and they can still do email and bookings and VoIP calls over LTE.
