RouterOS v3.14rc1 released

RouterOS v3.14rc1 released

You can download it from the MikroTik download page:
http://www.mikrotik.com/download.html

Changelog:
What’s new in 3.14rc1:

*) updated drivers, some of the changes:
synchronous cards should work in frame relay mode;
SIP connection tracking is more standards conformant;
valid TCP connection packets will not be marked as invalid;
*) mlppp - fixed problem when small packets could not be transmited
while more than 2 links were active;
*) bgp - fixed attribute flags checking;
*) fixed dhcp client - routes were not added back after lease expires
and then is acquired again;
*) fixed handling of multiple identical address-list entries
*) ospf could become unresponsive in some situations, fixed;
*) winbox - fixed problem: when moving multiple items at once,
correct order was not maintained;
*) fixed automatic fan control on RB600;
*) added ipv6 firewall address-list;
*) fixed some bugs in mesh protocol driver;
*) fetch tool - added basic HTTP authentication;
*) 6to4 tunnel - allow to specify remote address;

This version contains some significant driver updates, therefore we labeled it as an RC version, and left 3.13 on the download page.

What’s about export improvments?
What’s about snmp improvments?
Changelog is not full.

changelog is never full

and what about these 2 topics where are very awful
PPPOE DIE
very strange 3.x freeze and crash with pppoe unregister_netdevice

Ok. 3.14rc1 changelog in not full.

you didn’t get it - none of the version change logs include all changes. this is normal. this has been discussed before.

3.14 rc1 “cosmetic bug”:

  1. in /ip neighbor 3.14rc1 looks like 3.13.
  2. even password was set, 3.14rc1 requires to install a new password.

What exactly you are talking about ?

ip neighgbor print

INTERFACE ADDRESS MAC-ADDRESS IDENTITY VERSION

0 ether1 x.x.x.x 00:0C:42:02:15:52 4 SW 3.14rc1
1 ether1 x.x.x.x 00:0C:42:21:16:47 Sergejs… 3.10

Two things:

  1. Moving to a Release Candidate format for this release is fantastic. Exactly the right way to proceed and I hope it becomes standard practice.

  2. The fixes to MLPPoE are stunning, and I can’t believe how responsive MT was to this issue.

We are running one 3 line bond and one 5 line bond. Both work perfectly. Lines are 6Mb/800K in all cases.

Thanks!!!

George

Oh, sorry. My mistake.
Another problem:

  1. default ip address is not setup after /system reset
  2. new password is not requested after /system reset
  3. strange problem with snmp on x86 rb230 ros 3.14rc1:
snmpwalk -c public -v 1 192.168.88.1
End of MIB



/snmp
set contact="" enabled=yes engine-boots=1 engine-id="" location="" \
    time-window=15 trap-sink=0.0.0.0 trap-version=1
/snmp community
set public address=0.0.0.0/0 authentication-password="" \
    authentication-protocol=MD5 encryption-password="" encryption-protocol=\
    DES name=public read-access=yes security=none write-access=no
  1. clock settings exporting is not fixed! (time-zone-name settings is not exportable):
/system clock> print
            time: 17:29:51
            date: sep/12/2008
  time-zone-name: "Europe/Moscow"
      gmt-offset: +04:00
      dst-active: yes
[admin@MikroTik] /system clock> export
# sep/12/2008 17:29:56 by RouterOS 3.14rc1
# software id = V35A-3TT
#
/system clock manual
set dst-delta=+00:00 dst-end="jan/01/1970 00:00:00" dst-start=\
    "jan/01/1970 00:00:00" time-zone=+00:00
  1. snmp setting exporting is not fixed! (try to set up snmp community with special characters, export then import it):
 /snmp community> export
# sep/12/2008 17:29:01 by RouterOS 3.14rc1
# software id = V35A-3TT
#
/snmp community
set pub,lic address=0.0.0.0/0 authentication-password="" \
    authentication-protocol=MD5 encryption-password="" encryption-protocol=\
    DES name=pub,lic read-access=no security=none write-access=no
[admin@MikroTik] /snmp community> /snmp community
[admin@MikroTik] /snmp community> set pub,lic address=0.0.0.0/0 authentication-password="" \
\...     authentication-protocol=MD5 encryption-password="" encryption-protocol=\
\...     DES name=pub,lic read-access=no security=none write-access=no          invalid item number

any change about those issues in v3.14rc1 ? or not ? a reply please .

  1. system reset-configuration works fine for me.
  2. As far as I know there is no such feature in any version, but sounds like good feature request.

Maby in level 4,5,6 only? Not for demo?

[admin@MikroTik] > system reset-configuration
Dangerous! Reset anyway? [y/N]:
y
system configuration will be reset


RouterBIOS-200 v1.3.8 MikroTik (tm) 2003-2005

RouterBOARD 220 (CPU revision B1)
CPU frequency: 266 MHz
  Memory size:  64 MB

Press any key within 1 second to enter setup..

Booting IDE...
Loading system with initrd
MikroTik 3.14rc1
MikroTik Login: admin
Password:

  MMM      MMM       KKK                          TTTTTTTTTTT      KKK
   MMM    MMMM       KKK                          TTTTTTTTTTT      KKK            MMM MMMM MMM  III  KKK  KKK  RRRRRR     OOOOOO      TTT     III  KKK  KKK
  MMM  MM  MMM  III  KKKKK     RRR  RRR  OOO  OOO     TTT     III  KKKKK
  MMM      MMM  III  KKK KKK   RRRRRR    OOO  OOO     TTT     III  KKK KKK
  MMM      MMM  III  KKK  KKK  RRR  RRR   OOOOOO      TTT     III  KKK  KKK

  MikroTik RouterOS 3.14rc1 (c) 1999-2008       http://www.mikrotik.com/


UPGRADE NOW FOR FULL SUPPORT
----------------------------
FULL SUPPORT benefits:
- receive technical support
- one year feature support
- one year online upgrades
    (avoid re-installation and re-configuring your router)
To upgrade, register your license "software ID"
 on our account server www.mikrotik.com

Current installation "software ID": 1Z8W-GGN

Please press "Enter" to continue!

[admin@MikroTik] > ip
[admin@MikroTik] /ip> address
[admin@MikroTik] /ip address> print
Flags: X - disabled, I - invalid, D - dynamic
 #   ADDRESS            NETWORK         BROADCAST       INTERFACE
[admin@MikroTik] /ip address>

6)Another BUG:
This is layer-7 pattern for snmp from official site: http://l7-filter.sourceforge.net/layer7-protocols/protocols/snmp.pat
It seems not working in RouterOS.
7) /tool sniffer packet in winbox double-click on packet is not fixed!

Any chance you (MT) addressed the issues with mangle and queuing that I sent in via Ticket#2008090766000066] ROS on Intel CPU V3.13 Queues

Where mangle is not working correctly and so PCQs are not working correctly?

R/

please also include the MD5 checksums of v3.14rc1

This one seems to be a lot better:

ROS 3.14rc1 logging

14:40:00 pppoe,ppp,debug <0006>: LCP close
14:40:00 pppoe,ppp,debug <0006>: LCP closed
14:40:00 pppoe,ppp,debug <0006>: CCP lowerdown
14:40:00 pppoe,ppp,debug <0006>: BCP lowerdown
14:40:00 pppoe,ppp,debug <0006>: BCP down event in starting state
14:40:00 pppoe,ppp,debug <0006>: IPCP lowerdown
14:40:00 pppoe,ppp,debug <0006>: IPCP closed
14:40:00 pppoe,ppp,info,account rcs_128_voip logged out, 430 5239 7013 32 78
14:40:00 pppoe,ppp,debug,packet <0006>: sent LCP TermReq id=0x2
14:40:00 pppoe,ppp,debug,packet administrator request
14:40:01 pppoe,ppp,debug <0006>: LCP timer
14:40:01 pppoe,ppp,debug,packet <0006>: sent LCP TermReq id=0x3
14:40:01 pppoe,ppp,debug,packet \F8_
14:40:01 pppoe,ppp,debug,packet \08nistrator request
14:40:01 pppoe,ppp,debug,packet <0006>: rcvd LCP TermAck id=0x2
14:40:01 pppoe,ppp,debug <0006>: LCP lowerdown
14:40:01 pppoe,ppp,info <pppoe-rcs_128_voip>: terminating… - administrator request
14:40:01 pppoe,debug,packet wlan2: sent PADT to 00:E0:4C:81:86:D1
14:40:01 pppoe,debug,packet session-id=0x0600
14:40:01 pppoe,ppp,debug <0006>: LCP lowerdown
14:40:01 pppoe,ppp,debug <0006>: LCP down event in initial state
14:40:01 pppoe,ppp,info <pppoe-rcs_128_voip>: disconnected

ROS 3.4 logging

14:58:22 pppoe,ppp,debug <0be7>: LCP close
14:58:22 pppoe,ppp,debug <0be7>: LCP closed
14:58:22 pppoe,ppp,debug <0be7>: CCP lowerdown
14:58:22 pppoe,ppp,debug <0be7>: BCP lowerdown
14:58:22 pppoe,ppp,debug <0be7>: BCP down event in starting state
14:58:22 pppoe,ppp,debug <0be7>: IPCP lowerdown
14:58:22 pppoe,ppp,debug <0be7>: IPCP closed
14:58:22 pppoe,ppp,info,account reges logged out, 10784 1972 71392 35 1121
14:58:22 pppoe,ppp,debug,packet <0be7>: sent LCP TermReq id=0x2
14:58:22 pppoe,ppp,debug,packet administrator request
14:58:23 pppoe,ppp,debug <0be7>: LCP timer
14:58:23 pppoe,ppp,debug,packet <0be7>: sent LCP TermReq id=0x3
14:58:23 pppoe,ppp,debug,packet Pr\0B\08nistrator request
14:58:24 pppoe,ppp,debug,packet <0be7>: rcvd LCP TermAck id=0x2
14:58:24 pppoe,ppp,debug <0be7>: LCP lowerdown
14:58:24 pppoe,ppp,info : terminating… - administrator request
14:58:24 pppoe,debug,packet wlan2: sent PADT to 00:12:0E:95:AD:5C
14:58:24 pppoe,debug,packet session-id=0xe70b
14:58:24 pppoe,ppp,debug <0be7>: CCP lowerdown
14:58:24 pppoe,ppp,debug <0be7>: CCP down event in starting state
14:58:24 pppoe,ppp,debug <0be7>: BCP lowerdown
14:58:24 pppoe,ppp,debug <0be7>: BCP down event in starting state
14:58:24 pppoe,ppp,debug <0be7>: IPCP lowerdown
14:58:24 pppoe,ppp,debug <0be7>: IPCP down event in starting state
14:58:24 pppoe,ppp,info : disconnected

We are testing 3.14rc1 with no problem so far. Thank you.
ps. Sorry earlier posts, too much pressure.

Ozelo

Thanx for the effort in any case guys.
The synchronous drivers will help us a lot.

Congratulations guys for adopting this release process!

Thanks a lot for being this open to users suggestions.

I join the others that hope for this to become standard procedure from now on.

Cheers, :slight_smile:

The freeze stuff still there on ROS 3.14rc1… :frowning:

i wait thatthe mt team fix the problem on next 3.14rc2. :confused:

regards