"Netflow" bug fixed in this version?
What's new in 4.6:
*) fixed - trafficflow was not started automatically after router reboot =)
I've tried this is in the past and never gotta uTorrent to pick up that I downloaded the files manually. Is there a trick you know of with uTorrent to allow downloading these files and seeding them if they didn't come from the original source?by the way, no torrent seeders again =)
I downloaded files from http, and seeding them via torrent
Torrent stalls at 54.3 percent. Do not see any Mikrotik IP's in the list of peers? You guys blocking p2p at your gateway? ;<)What's new in 4.6:
*) only accept dotted decimal notation for IP addresses. Use of numbers
with leading zero, numbers larger than 255 and non-decimal numbers
is not accepted (but still can ommit third or second and third numbers,
if they are zero);
*) email - user must enable tls explicitly
*) remove limit on number of multicast enabled interfaces, maximum was 32;
*) dhcp server - show last-seen time for leases;
*) dhcp server - do not create busy lease if client declines all IP addresses;
*) fixed - when closing winbox terminal window with active serial-terminal
console command, serial port sometimes was left in acquired state;
Also some Netinstall improvements for installation with USB flash drives.
http://www.mikrotik.com/download.html
I'd do the same as it would help, any instructions how to do this?by the way, no torrent seeders again =)
I downloaded files from http, and seeding them via torrent
Some other people have reported this, but so far most people (including myself) have had good luck with the files we have downloaded. Can you try downloading the packages again to see if you still have the problem? Also, what packages are you trying to install? The complete, or several of the individual packages?Something's gone horribly wrong.
I downloaded everything and uploaded the mips-be.npk to a 411 and rebooted.
I uploaded the powerpc.npk to a 600 and rebooted and I uploaded the mips-le.npk to a 532 and rebooted.
All three machines have come up with an error "system error - broken package" and then the name of the file that I uploaded.
I tried both ftp and copy / paste.
I downloaded a second set of files and still the same thing.
HELP!!!
I downloaded the http packages, not the torrent.don't download from the torrent, see above - the MT seed is gone, so somebody is seeding you their broken packages. The HTTP downloaded packages are fine. We will fix the seed ASAP, sorry guys
Still doesn't seem to work with Back to My Mac, though.Normis You forgot to mention that UPnP has been updated slightly in v4.6 (Xbox360 Live).
did you send us sniffer file from when it tries to make that dynamic NAT rule? please do thatStill doesn't seem to work with Back to My Mac, though.Normis You forgot to mention that UPnP has been updated slightly in v4.6 (Xbox360 Live).
Or my x86 either. That freezes after an L2TP session has been up for a couple of minutes - totally frozen, even at the console. Disable the L2TP client and it stays unfrozen.Nope. 4.6 definitely doesn't like my RB750
http://download.mikrotik.com/all_packages-x86-4.5.zipDoes anybody have any links to x86 version 4.5? I upgraded this from 3.30, so I've nothing in the x86 4.x tree.
Thank you.
Do you enabled MNDP on those interfaces ?Thank you.
Right. Downgraded to 4.5 and it works perfectly. Upgrade again and... CRASH. Downgrade again and it now works perfectly.
There's definitely something wrong with 4.6.
MNDP is only running on the local Ethernet interfaces, not the L2TP and PPP interfaces.Do you enabled MNDP on those interfaces ?
What ticket and what report? Compare changelogs for 4.5 and 4.6 and you will see one entrytell me the ticket number of this report, as I don't recall any reports about "bridged traffic with nstreme"
What rubbish.It's not fair to state "I tested and downgraded".
A network engineer does not just "test and downgrade" but should state exactly what he discovered in much greater detail!
Yes. I agree, and that is exactly what I do (see ticket 2010030466000103, for an example). But sending a description and a supout.rif is a far cry from stating "exactly what [was] discovered in much greater detail"Make supout.rif file and send to support with proper problem description instead of just complaining.
it does exist, but only for MikroTik internally. Support screens it from users, because many reported 'bugs' are just misconfigurationswhy don't you set up a bug tracking system (bugzilla) and make the whole process more transparent?
exactly trueit does exist, but only for MikroTik internally. Support screens it from users, because many reported 'bugs' are just misconfigurationswhy don't you set up a bug tracking system (bugzilla) and make the whole process more transparent?
Ah-ha, so it's our fault that MT aren't more open with us? May I venture to suggest that if the documentation were more complete, a large number of these misconfigurations wouldn't happen in the first place?Support screens it from users, because many reported 'bugs' are just misconfigurations
I have never used combined packages to upgrade the OS %) just install only necessary ones =)It so frustrating doing an operating system upgrade, then having to go back and remove IP6, Hotspot and other stuff that gets loaded by default during the upgrade.
With the added advantage to MikroTik that they'll still make money from hardware sales. In fact, I'd bet they'd make more money - if ROS is opened up, I would practically guarantee more people would want the hardware.Over time the two will split and you'll end up with something like Debian vs Ubuntu. You pays your money, you makes your choice.
But that's precisely my point. If the bugtracker was open to all and members of the community were made bug marshalls, most of the first line support questions would be answered by them and you could concentrate on developing the product.If you would see what kinds of mails we get everyday, you would reconsider this idea
this forum is a good example of the same idea. we have beginners, and we have experienced users helping them.But that's precisely my point. If the bugtracker was open to all and members of the community were made bug marshalls, most of the first line support questions would be answered by them and you could concentrate on developing the product.If you would see what kinds of mails we get everyday, you would reconsider this idea
Ah well. Maybe I'm just an idealist.
What ticket and what report? Compare changelogs for 4.5 and 4.6 and you will see one entrytell me the ticket number of this report, as I don't recall any reports about "bridged traffic with nstreme"
4.5
*) fixed Nstreme issues with bridged traffic
magically disappeared.
http://forum.mikrotik.com/viewtopic.php?f=2&t=38316
vs
http://www.mikrotik.com/download/CHANGELOG_4
no, you should assume that somebody messed up the changelog.Now there is no *) fixed Nstreme issues with bridged traffic
Should I assume its broken again?
If changelog can be messed up, I don't even wanna know what else can be.no, you should assume that somebody messed up the changelog.
I am pretty sure even you know this is not true. API covers just part of the MT functionality.and also regarding TuxBox or proper webbox - you can already use API to make configuration tool for any platform you want.