*) fixed problem - WinBox crashed while opening VAP interface;
*) dhcp server - fixed possible inactive dhcp server in case of many
dhcp leases with address-pool enabled (broken in v4.7);
*) dhcp server - show non-printable agent-circuit-id and agent-remote-id
values in hexadecimal notation (the same way as client-id is shown);
*) api - can supply password to ‘/system/upgrade/upgrade-package-source/add’;
*) console - fixed bug that caused “cannot set …” error when using
some properties in ‘find’ commands;
*) api - ‘print’ command was not showing values of some properties
such as ‘servers’ in “/ip/dns”;
*) show old software id in export file header;
*) added support for secondary serial port on RB800/RB1100;
What’s new in 4.7:
*) fixed problem - wireless packet bridging with nstreme enabled
sometimes was very slow on RB1xx, RB5xx and RB4xx;
*) fixed problem - ipv6 traffic was not bridged if ipv6 package was not enabled;
*) ‘/user active’ now lists type of api connections as ‘api’
*) fixed getting interface stats in dude
*) fixed metarouter stability problem on RB400s & RB750s;
*) fixed metarouter - it didn’t work on RB1000 with 2Gb;
*) fixed metarouter - it locked up on RB800;
*) fixed problem - SFQ queues did not work on interfaces (wireless) if none
of simple or tree queues were added;
*) fixed RB800 temperature;
*) silentboot feature updated;
*) multicast - fixed possible crash during PIM startup;
*) ospf - changed “/routing ospf route” to show type 2 metric instead of
internal metric for type 2 external routes;
*) report platform name in “/sysrem resource”;
*) fixed problem - vlans were not working on RB750 ether1;
*) fixed mac address handling on RB750, some specific arp requests did not work;
*) more than two dns servers allowed in /ip dns;
*) sniffer and torch could process packet from other interfaces;
*) dns cache rotates order of records in reply messages;
*) ospf - fixed DR and BDR election;
Which is unfortunately not acceptable, and after numerious discussions, MT seems rather unwilling to change their practises… This, in conjunction with bugs never being fixed, is exactly why I have replaced every MT device I have in use with Ciscos… When MT’s release practises improoves, I will most definately reconsider.
What are you talking about? There is no change that “is not mentioned in the changelog”. It’s this kind of speculation talk that leads to such beliefs.
please tell me the ticket number of the problem you are referring to. there could be multiple issues with dhcp in v5 beta, so I don’t know which specifically you mean.