Full ack. With MT I get a lot for my money. But as a typical user I want to get moreStill the best system around - hell even Motorola has a buggy mesh and that's been a problem for 2 years - of course there are work a rounds to that too but it is still there.
MT rocks and is still the best out there for my money!
As long as I keep every known version on archive and the strengths and weaknesses on file then I know what to use. Used to have the same problem with Cisco until I dumped every router in our network to go to Siemens GUI driven Systems. Had problems there too but had direct line to their R&D and could talk to them 24/7. This would be the only problem that I would have with MT but being that I have all the Previous versions - I'm not stuck and downgrade is simple and easy.
Right now v3.30 is the most stable except for 900mhz and that is v3.28. Have no clue why but it works.
Good luck,
Rod
Normis, that's exactly what I'm trying to explain. If you are going to take every release off-line due to a minor bug you will never release a new version again I guessdid you not see that we took off the v4.7 download as soon as we discovered a minor known bug? we don't have any other known bugs, except those that are reported after version build.
I also agree on v3.30 being the best (real) stable version (we have some routers still on 3.19 which was our former standard), but in this particular case we want to use 11nYou could try 3.30 pal.
I noticed this also after doing some traffic analysis.Having massive problems with hotspot and DNS on 4.7... DNS server stops responding after a while for no apparent reason, DNS client works fine.
No response from MT support as yet.
Downgrading to 4.6.. will see.
Apparently 3.31 is exactly the same as 3.30 but with support for the RB750 (probably just additional drivers)REEAAALLLLYYY! v3.31 not listed is interesting. Didn't know there was was such a critter.
Not necessarily a bad idea, but hackish. I think it'd be nicer to just make use of the bypass rule just above that:My buddy has the same issue... DNS just stops working. He was sick and tired of disabling and reenabling the hotspot so we scheduled this to run every few mins and it seems to have fixed things:
/ip firewall nat remove [/ip firewall nat find chain="hotspot" dst-port="53" ]
Basically just removing the DNS redirect and letting DNS pass. Any reason thats a bad idea?
chain=hotspot action=jump jump-target=pre-hotspot
/ip firewall nat add chain=pre-hotspot dst-port=53 action=accept protocol=53
/ip firewall nat add chain=pre-hotspot action=accept protocol=udp dst-port=53
http://forum.mikrotik.com/viewtopic.php?f=2&t=38515 has been around for at least a few months, no updates on the 4.7 changelog either. When do you anticipate this bug being fixed?did you not see that we took off the v4.7 download as soon as we discovered a minor known bug? we don't have any other known bugs, except those that are reported after version build.