Mikrotik ROS4.13 Changelog
Change log is here.
*) added USB power reset feature;
I know several people will be happy to see this feature. It allows you to reboot 3G modems attached to the mikrotik without having to reboot the whole router. Some people were experiencing issues with the initialization of the modem, so this should fix the issue nicely.
*) added support for nv2 in wireless-nv2 package;
It looks like they have ported Nv2 over to the 4.X train…I didn’t expect to see this. I figured Nv2 would be used to push people to version 5.
I get confused, a bit, why Mikrotik keeps trying to add features to existing released firmware (non-beta), while they are working on new releases i.e. 5.0RC3. They must have a lot of people going back and forth between the two releases trying to get things to work properly.
Personally, I would rather see them focus on the new beta/RC versions and get them working acceptably and leave the previous versions alone.
I’m sure, opinions will vary… 🙂 🙂
@Tim
Just my $.02 here, but I think it is somewhat shrewd of them. They have gotten Nv2 nailed down enough to have it “ready” for production. They are putting a lot of stock into the new protocol and want it to appear as if they have a solid working protocol ready for prime time. So, instead of waiting for beta 5 to go gold, they are back porting the working Nv2 and have it live in a solid code train.
Now if they would just use GPS time sync for slots 🙂 🙂
@Tim
Is anything ever good enough for you…you ingrate! 😛
I want what I want, and I want it now !!! And really cheap too.. 🙂 🙂
Maybe there was lack of testing of nv2 because ppl were afraid of v5.x.
Now they can test and MT can get feedback faster, so that all will be ready for v5.x stable release.
@Rudolff
Indeed sir, good point.
Is 4.13 an actual “release”, or is it beta? I understand what you are saying, but if they wanted customers to test the firmware, than by that implication it’s still beta. But I don’t think it was presented that way. I could be wrong..
Greg, I’m not exposed to Cisco’s update structure. I’m sure they charge for their updates, but how do they handle betas? Mostly, just curious…
@Tim
I’m under the impression that it is stable enough for prime time. At least I would hope it is.
Cisco doesn’t really do the beta thing. They have different classes of code train, though. Some are marked as experimental and I tend to avoid those. Some are marked with a T for technology…which means they implemented a specific new feature. Any significant piece of code is back ported to more mature trains once it is completely solid.
Here at the Datacenter, we generally run service provider trains. They may not have all of the newest technological features, but they are solid.
RB411U + USB760
[rob@RB411u] > /system resource usb power-reset
ERROR: USB power reset not implemented on this hardware
🙁
I’ve had issues with this RB and a Verizon USB760 modem for awhile now and was hoping this would update would at least be an easier way to restart the modem. I wonder exactly what USB devices it actually does reset the power on?
Rob
Perhaps the 411 is the device that’s not supported?
Normis posted a vague reference to that in this thread: http://forum.mikrotik.com/viewtopic.php?f=2&t=46319
He says for “future” routerboards so I’m guessing that none of the RB’s with USB support this. Sux cause this is a big problem for me with the RB411U and the USB760. 🙁
Rob
Rob,
It does sound like Normis is saying future routerboards and maybe this has nothing to do with it, but I’ll throw it out here just for the heck of it: is your firmware up to date?
Bobby,
Good suggestion but I’ve tried updating the firmware already. I’ve updated everything I could think of, sent supout files in, stood on one leg, etc… and nothing has worked. It’s annoying as heck having to unplug the modem or reboot the RB over and over for it to recognize it again and I had hopes this would at least give us a little better “hack” to get it working.