MikroTik

What's new in 3.10:

*) added Multilink PPP to PPPoE client - just specify multiple interfaces
to enable it;
*) added ability to add dynamicly PPTP, L2TP & PPPoE client addresses
to firewall address-list, specified in ppp profile,
or via RADIUS in Mikrotik:19;
*) added address-list attribute support in user-manager;
*) added fan control for RB433;
*) console:
fixed 'interface wireless print detail', now shows the same output as
'interface wireless print basic';
fixed print to file, now writes complete contents, fixed resource leak;
show name of running scripts in '/system script job', update
'last-started' value;
could not use item names for '/interface ovpn-server' and
'/interface ovpn-client', fixed;
fixed problems with export:
some settings were not included in full export, such as
'/interface wireless nstreme');
some settings had duplicate entries with an error, such as
'/system ntp client' when ntp package was enabled;
long parameter values were incorrectly split across multiple lines;
export now quotes all values that are split across multiple lines, it
also adds line split before all newline characters, which improves
readability of exported script sources;
*) api - some properties were included multiple times in getall responses;
*) port - properly tag all inactive ports;
*) port - fixed memory leak that was triggered by addition/removal of
USB serial ports;
*) changed post-boot critical log messages - write a separate log entry
explainig the cause of an non-administrative reboot, such as watchdog
ping timeout, even if system rebooted cleanly;
*) fixed user-manager 'database rebuild' command to correct database errors;
*) fixed bug - user-manager customer password was not decoded
correctly when database backup was transferred
between Intel/RB100/RB500 and RB300/RB400/RB600/RB1000;
*) fixed bug - "/blink" command did not work on RB300/RB600/RB1000;
*) allow to configure OSPF authentication key ID;
*) allow to include bridge interface in a mesh interface;
*) ipsec - added Dead Peer Detection;
*) fixed some random crashes on RB411 & RB433;
*) fixed bug - OpenVPN could corrupt data on high load and force other end to disconnect;
*) fixed bug - DHCP server did not return DHCP options in response to
DHCPINFORM request;

upgraded from 3.9 to 3.10 (rb 333)

jan/01/1970 01:00:06 system,info installed routeros-powerpc-3.10
jan/01/1970 01:00:06 system,error,critical System rebooted because of kernel failure
jan/01/1970 01:00:06 system,info router rebooted

next reboot and device working good (i think) ;]

Hi,
Does anyone tests new feature ?

added Multilink PPP to PPPoE client

As I understand, finaly thay have added support for multiple PPPoE interfaces over single Wireless link ?

I count 8 new features and 15 bug-fixes.

Think I'll stick with 2.9.51 for the moment.

I count 8 new features and 15 bug-fixes.

Think I'll stick with 2.9.51 for the moment.

Don't forget the total amount of bug fixes in the ros3.x family! Already 3.10 in less then half a year???
I´ll bet the management of MT plays golf with a certain B.Gates to learn the tricks of selling an operating system to its users!

And we users, also called ¨the unpaid test society¨, we are all too happy to download the latest gadget OS in our toys every time again. We will fall on our face, hurt our nose but hey, what the hack! The latest is yet again better then before!

The only trick MT hasn't learned from Bill is that we might even be willing to pay for it! We, the dummies in the field simply want the best, whatever that might mean...?!

?... going back to 2.9.xx? Nooooh, we don't want to go back to the good old days.... no, that's for oldies!
No we, we are young, fast and notorious... we want updates, the more the better..... we only take the best!
Actually we are fools....

No offence...

upgraded from 3.9 to 3.10 (rb 333)

jan/01/1970 01:00:06 system,info installed routeros-powerpc-3.10
jan/01/1970 01:00:06 system,error,critical System rebooted because of kernel failure
jan/01/1970 01:00:06 system,info router rebooted

next reboot and device working good (i think) ;]

make the support output file after this kernel panic and send it to support@mikrotik.com

upgraded from 3.9 to 3.10 (rb 333)

make the support output file after this kernel panic and send it to support@mikrotik.com

got this problem on some of mine 133 411 and 333

check mail :>

Yep, I have kernel panic as well when upgradeing to 3.10 from 3.6(I think)...

Output via Serial Cable:
kernel not found
trying bootp protocol...................

Hmmm

I went into the boot setup menu I reselected "boot from NAND and then ethernet" (which is was already on and I believe is the default setting) and turned on NetInstall. I got far enough to load 3.6 firmware back onto the board (which runs smoothly). Upgrading to 3.9 right now, and if that goes smoothly I'll try 3.10 again, see if I can duplicate the issue.

If it doesn't I'll report that as well. Maybe it's just 3.6->3.10 that doesnt' work effectively.

Same thing from 3.9->3.10,

RouterBOOT booter 2.12

RouterBoard 411A

CPU frequency: 300 MHz
Memory size: 64 MB

Press any key within 2 seconds to enter setup..
kernel not found
trying bootp protocol..........................................................

Via other threads I found that by updating the boot loader to 2.16 for RB500 series boards, that 3.10 goes on smoothly.

Is there a bootloader update for the RB400 series boards?