*) added missing ‘/ip dhcp-server alert get’ command;
*) fixed DHCP server to work with some non-RFC compliant DHCP clients;
*) improved robustness of serial port UPS handling; fixed value exponent
handling for USB UPS;
*) fixed problem with static ARP entries not added after reboot
on some interfaces;
*) graphing web interface is now a valid xhtml 1.0;
*) added support for Novatel Wireless CDMA card;
*) speed up route table updates in routing-test;
*) fixed crash in routing-test (introduced in 2.9.19);
*) fixed crash in user-manager if download-limit is used and radius packet
logging is enabled;
*) fixed handling of disabled packages by console setup;
Problem “*) fixed problem with static ARP entries not added after reboot
on some interfaces;” that I reported in ticket #2006051816000033 is NOT fixed in this release. Exact same problem as before.
Static ARP entry on RSTP bridge interface not effective after reboot. Must disable and re-enable for static arp entry to work.
We have 2 Test machines with routing-test. After a few hours with 2.9.25, we got bgp constantly renegotiating with neighbors. ??? downgraded to 2.9.24
Can I already smell 2.9.26?
Routing-test in 2.9.25 fixed many of our problems (speed is 100% better at updating routing table, discarded routes being advertised to peer, etc) yet when we disconnect/disable from a peer we get 100% CPU forever. Not all the time - but 1 out of 2-3. Putting together more supouts.
You know… This is starting to peeve me off actually.
MT seems much more phased by bringing out new releases every second day (just about), instead of taking their time and making SURE things work before they release it.
You’re doing no one a faviour by releaseing buggy software every week MT… Really. Get this right, plan your updates, and release it when it’s been tested properly. Personally, considering that there’s talk already about the .10 branch, I doubt very much whether MT will ever get a hold on 2.9… I’m dissapointed, to say the least