What's new in 2.9.25:
*) 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;
))
yes, it should be fixed.
http://forum.mikrotik.com/viewtopic.php?t=8299
Install 2.9.25 and try with intel cards.
http://forum.mikrotik.com/viewtopic.php?t=8299
Install 2.9.25 and try with intel cards.
Proprietary-extensions in wireless menu
?? Proprietary-extensions in wireless menu ??
Hello,
what does this mean ?
Thanks
Ian
Hello,
what does this mean ?
Thanks
Ian
RB532+RB502 - tarpit problem?
>There was problem with Firewall rule that uses action=tarpit. We will fix > that in v2.9.25, you can wait till that.
>
>Regards,
>Uldis
it is fixed in 2.9.25 or not?
>
>Regards,
>Uldis
it is fixed in 2.9.25 or not?
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.
Also updated ticket via e-mail.
Please correct ASAP, this is killing us.
Dave
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.
Also updated ticket via e-mail.
Please correct ASAP, this is killing us.
Dave
-
-
NetTraptor
Frequent Visitor
- Posts: 76
- Joined:
- Location: Athens Greece
- Contact:
-
-
oriondotnet
Frequent Visitor
- Posts: 65
- Joined:
rpingar.. check this out http://forum.mikrotik.com/viewtopic.php?t=8793 , looks like Intel Dual port problem not Mikrotik... already try on FreeBSD also have same problem.
any new news on driver about Intel pro1000 DUAL?
Regards
thanks
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
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
QUEUE data LOST
Is fixed bug, which was in 2.9.24: After reboot I lost all queue data. I aum using this for FUP. So is here any version which does not have this bug? 
http://forum.mikrotik.com//viewtopic.php?p=39817savage, can you send all information about your problem to support? other customers say that vrrp started working in latest versions.And still no mention of a working VRRP... -shrugs- Are we ever going to see working redundancy / high availability?
supout.rif file should be from 2.9.25
Just one of many posts about VRRP not working since .23 - the above actually states .25 not working. Before I even consider a possible rollout of updated software for testing, I read the changelog to see if a (my?) specific issue was fixed in the current version... That's how intelligent upgrades are done:
1) Determine whether a patch / update resolves your problem
2) Implement the patch / update in a test environment
3) Test the patch / update in a test environment
4) If happy, continue the rollout.
MT does not even pass point 1 above... I don't see a need for the rest.
If VRRP has been worked on, and is working in .25 - why is it not in the changelog? I don't 'trail' software when I know it. It was broken on previous versions, there's no mention that it's been fixed, I continue to presume it's not working.
The above has also been confirmed not to work by other members on the forum. I don't see the point of breaking my own network by installing software on it that doesn't work?
