What's new in 2.9.27:
*) added WISPr Radius attribute support to hotspot;
*) fixed booter setting damaging on MIPS based routerboards,
bug was introduced in 2.9.18;
*) fixed hotspot to handle lost leases in a more graceful way;
*) changed serial terminal prefix key to Ctrl-A;
*) fixed special-login;
*) fixed Interface column in WinBox VRRP Table;
*) fixed BGP connection establishment when router ID is not explicitly set;
*) changed webproxy-test logging topics from "webproxy,info" to
"webproxy,account";
*) ppp client acquires serial port only when dialing in, not immediately;
*) improved vrrp gratuitous arp sending, fixed vrrp enable/disable bug
*) added support for Novatel U740 (Wireless HSDPA Modem);
*) fixed NTLM authentication in webproxy-test;
*) fixed default route distribution in OSPF;
*) fixed graphing bug related to periodic hard disk writes;
Re: v2.9.27 released
Any details available about this feature? I'd like to get some testing underway asap.*) added WISPr Radius attribute support to hotspot;
http://www.cisco.com/en/US/products/ps6 ... bfa91.html Some info there...
-
-
BrianHiggins
Forum Veteran
- Posts: 720
- Joined:
- Location: Norwalk, CT
- Contact:
*) fixed booter setting damaging on MIPS based routerboards,
bug was introduced in 2.9.18;
*) fixed hotspot to handle lost leases in a more graceful way;
*) fixed special-login;
*) ppp client acquires serial port only when dialing in, not immediately;
*) improved vrrp gratuitous arp sending, fixed vrrp enable/disable bug
*) fixed NTLM authentication in webproxy-test;
*) fixed default route distribution in OSPF;
*) fixed graphing bug related to periodic hard disk writes;*) fixed BGP connection establishment when router ID is not explicitly set;
*) fixed graphing bug related to periodic hard disk writes;
since it seems that nearly everyone has requested a better change log for 2.10, what is the reason we can't start requesting that now for 2.9.x? It's not like the new version will suddenly generate, or allow a more detailed change log, that's just something the guys at MT have to do.
the above are the issues that were listed that I do not feel are adequitly explained, and I would like someone at MT to give us a detailed description of each item.
I suggest that in the future we all require MT to release better descriptions and details with the change log, or we start emailed support for that, with each version they release.
bug was introduced in 2.9.18;
*) fixed hotspot to handle lost leases in a more graceful way;
*) fixed special-login;
*) ppp client acquires serial port only when dialing in, not immediately;
*) improved vrrp gratuitous arp sending, fixed vrrp enable/disable bug
*) fixed NTLM authentication in webproxy-test;
*) fixed default route distribution in OSPF;
*) fixed graphing bug related to periodic hard disk writes;*) fixed BGP connection establishment when router ID is not explicitly set;
*) fixed graphing bug related to periodic hard disk writes;
since it seems that nearly everyone has requested a better change log for 2.10, what is the reason we can't start requesting that now for 2.9.x? It's not like the new version will suddenly generate, or allow a more detailed change log, that's just something the guys at MT have to do.
the above are the issues that were listed that I do not feel are adequitly explained, and I would like someone at MT to give us a detailed description of each item.
I suggest that in the future we all require MT to release better descriptions and details with the change log, or we start emailed support for that, with each version they release.
I think for those why actually was waiting for particular bugfix, bugs are adequitly explained.
I, for example, was interested only in OSPF fixes, I reported a bug, i made some debug logging, send several supout.rif files
Why do you need any other information about old bug (or DEAD bug) ?
Bug list must have short representation of every fix, thats all!
I, for example, was interested only in OSPF fixes, I reported a bug, i made some debug logging, send several supout.rif files
Why do you need any other information about old bug (or DEAD bug) ?
Bug list must have short representation of every fix, thats all!
-
-
oriondotnet
Frequent Visitor
- Posts: 65
- Joined:
-
-
Alessio Garavano
Member
- Posts: 306
- Joined:
- Location: Corrientes, Argentina
- Contact:
Hi, i think your problem is by loggingi made the upgrade ..
before i can c the web-proxy-test actions in the LOG ..
now there is nothing in the log accept the system actions ??
how can i view the web-proxy-test acyions again in the log ??
*) changed webproxy-test logging topics from "webproxy,info" to
"webproxy,account"
2 RB532 and 2 P4 upgraded without problem
Regards!
Alessio
-
-
oriondotnet
Frequent Visitor
- Posts: 65
- Joined:
I think you should try it - you should help the Mikrotik support by revealing the bugs and testing the fixes.need some info on BGP, still bugged??
thank you
In other case you can wait for the completely debuged version forever.
And, as we know, there is no such thing as "completely debuged version" in software
-
-
BrianHiggins
Forum Veteran
- Posts: 720
- Joined:
- Location: Norwalk, CT
- Contact:
Virtual AP Deleted
I just upgraded one of my APs that had a virtual AP running on it. previous version was 2.9.18. the virtual AP was deleted in the upgrade process... I just emailed support about the issue...
may be un-related bug but worth noting:
i have a wds wrap 2c acting as a single radio repeater with another hard wired 2c wrap. it reboots some times after like 1 or 2 min of down time, but for the first time 4 days ago it went for like 8 hours then came back. All of this is on 2.9.22.
Today i upgraded to 2.9.27 (11 hours ago) and everything went great, until about 2 hour ago when i lost the wds again. MAYBE UNRELATED TO UPDATE and just some radio / antenna foolishness, but im 400 miles away and its not critical.
i did had to do the update to all the ap's due to the propritary extentions and intel chipset issue....i still think that this bug/fix/feature should have been "announced" better or louder..
joe
i have a wds wrap 2c acting as a single radio repeater with another hard wired 2c wrap. it reboots some times after like 1 or 2 min of down time, but for the first time 4 days ago it went for like 8 hours then came back. All of this is on 2.9.22.
Today i upgraded to 2.9.27 (11 hours ago) and everything went great, until about 2 hour ago when i lost the wds again. MAYBE UNRELATED TO UPDATE and just some radio / antenna foolishness, but im 400 miles away and its not critical.
i did had to do the update to all the ap's due to the propritary extentions and intel chipset issue....i still think that this bug/fix/feature should have been "announced" better or louder..
joe
Yeah right. standard routing package works fine, but filtering didn't workI think you should try it - you should help the Mikrotik support by revealing the bugs and testing the fixes.need some info on BGP, still bugged??
thank you
In other case you can wait for the completely debuged version forever.
And, as we know, there is no such thing as "completely debuged version" in software
Now what? combine that two please, standard routing bgp,rip,ospf + routing-test filtering
Who is online
Users browsing this forum: FrankMüller and 27 guests