RouterOS v5.0 RC4

NetworkPro · Mon Nov 22, 2010 10:04 pm

What's new in 5.0rc4 (2010-Nov-22 16:58):

*) radius - fixed Disconnect and CoA response signature generation;
*) winbox - make double click work in text fields again;
*) winbox - allow to drag windows outside of main one to the left;
*) winbox - make some settings look more consistent;
*) winbox - allot to specify IPv6 address in routing filter prefix;
*) winbox - make possible to open IPv6 routes without crashing;
*) winbox - improved item reordering in long lists;
*) winbox - improved SNMP configuration support;
*) winbox - added support for KVM configuration;
*) winbox - added support for Traffic Engineering configuration;
*) ovpn - make ovpn client work with OpenVPN v2.1.3;
*) lcd - support Crystalfontz 631,633
also support for Crystalfontz lcd contrast setting is added;
*) console - fixed missing return value of the ping command when executed
from a scheduler entry;
*) console - 'ping' command with specified value of 'interface' always forced
"arp-ping=yes", fixed;
*) routing - fixed problem with 'check-gateway' status update that could get
triggered when multiple routes with different values of 'target-scope'
and 'check-gateway' referenced the same gateway IP address;
*) store - allow to use external disks;
*) modem firmware directory can be specified in /port firmware
Gobi users should change this setting or directory name;
*) ups - support USB UPS on RB4xx as well;
*) snmp - fix BER encoding for some INTEGER based values;
*) snmp - provide proxy stats using SQUID-MIB;
*) snmp - provide ups info using UPS-MIB;
*) snmp - provide external storage information;
*) wireless nv2 - add missing statistics fields;
*) wireless - add per-chain signal strength fields;
*) added hotspot html variable "host-ip";
*) fixed pcq queue type;
*) fixed leds on RB750;

Torrent:
http://www.mikrotik.com/download/router ... c4.torrent

Regular download:
http://www.mikrotik.com/download.html

Let the testing begin...

mietus · Mon Nov 22, 2010 11:12 pm

first BUG in rc4

rb411ah

[admin@mt] > system health pri
voltage: 1245V

;-P

maybe it suppose to be a 12.45v

second (BUG?)

in winbox interface/ether1 bandwith reports 4294967295 earlier it was unlimited.

NetworkPro · Mon Nov 22, 2010 11:46 pm

Guys,

We need you to test in high load router with all kinds of configurations.

Schedule a test time with easy physical access to the routers and possibility to reinstall and restore a .backup.
In a low-traffic time, like at night, to minimize downtime to your service.

Scenarios I can think of that need testing:

- PCQ with high speeds - above 20 megabits
- NV2, QoS for NV2
- Scripts
- PtMP with encryption
- BGP with high load
- OSPF
- Dual Core, Dual CPU, Quad Core and up
- USB Store for main store, USB store for secondary store, all kinds of Store-combination scenarios
- Layer 7 and the old-school content matcher as well
- All scenarios for compatibility with other equipment
- SCSI Stores
- KVM, MetaRouter
- VMWarea and virtual environments with high traffic load for performance (just for fun, not officially supported)

Please report all issues, including with WinBox.

If possible please provide screenshots, supout.rif etc, send them to support@mikrotik.com.

Separately report the issues here in this thread.

Thank you.

P.S. Remember to give the router up to 5 minutes when it restarts to install the new version.

roadracer96 · Mon Nov 22, 2010 11:57 pm

802.1x wireless worked in 5.0b3 and stopped working in 5.0b4. passthrough to 2008 server RADIUS using certificates.

roadracer96 · Tue Nov 23, 2010 12:07 am

Whats weird... The RB433AH I have in my office for wireless was on 5.0rc3 and 802.1x worked fine. The RB433AH at my home has 5.0brc4 (Has had it for over a week now, pre release) and it has been working fine.... Ill upgrade it to 5.0rc4 (release) and see if it stops when I get home.

ayufan · Tue Nov 23, 2010 12:59 am

Yay! Torch fixed!

rmichael · Tue Nov 23, 2010 1:01 am

*) fixed pcq queue type;

What does that mean?

NetworkPro · Tue Nov 23, 2010 1:09 am

It means that you would help if you could please test it.

For example - you have a router with PCQ configured passing a lot of traffic. Install the latest RC4 and see if all is fine - traffic distribution and ping times. Compare to previous version.

If your clients have 20mbits and above, configured with PCQ, even better. Since this needs testing. Based on my experience.

Thank you.

NetworkPro · Tue Nov 23, 2010 1:22 am

I have just discovered:

- 100% CPU because of rebuilding web proxy cache, shows as idle in Profile

roadracer96 · Tue Nov 23, 2010 1:48 am

Yah. It stopped working at home too.. The 5.0rc4 build dated 11/05 I was running for 11 days worked, this 5.0rc4 Doesnt.

17:57:19 radius,debug,packet sending Access-Request with id 33 to 172.16.102.3:1812 
17:57:19 radius,debug,packet     Signature = 0x1b568ebd9b5e4cb061f585c6f93cf4cc 
17:57:19 radius,debug,packet     Service-Type = 2 
17:57:19 radius,debug,packet     Framed-MTU = 1400 
17:57:19 radius,debug,packet     User-Name = "tim" 
17:57:19 radius,debug,packet     State = 0x6bcc087c0000013700011700fe800000 
17:57:19 radius,debug,packet       00000000c17aafd471f2106c00000004 
17:57:19 radius,debug,packet       14808cec 
17:57:19 radius,debug,packet     NAS-Port-Id = "wlan3" 
17:57:19 radius,debug,packet     Calling-Station-Id = "5C-59-48-DF-0D-2C" 
17:57:19 radius,debug,packet     Called-Station-Id = "02-0C-42-3A-C4-08:moshpit" 
17:57:19 radius,debug,packet     EAP-Message = 0x020502f40d0030818606082b06010505 
17:57:19 radius,debug,packet       073002867a687474703a2f2f70736733 
17:57:19 radius,debug,packet       2e706f736974697665736f6c7574696f 
17:57:19 radius,debug,packet       6e7367726f75702e6f66666963652f43 
17:57:19 radius,debug,packet       657274456e726f6c6c2f505347332e70 
17:57:19 radius,debug,packet       6f736974697665736f6c7574696f6e73 
17:57:19 radius,debug,packet       67726f75702e6f66666963655f706f73 
17:57:19 radius,debug,packet       6974697665736f6c7574696f6e736772 
17:57:19 radius,debug,packet       6f75702d505347332d43412e63727430 
17:57:19 radius,debug,packet       0d06092a864886f70d01010505000382 
17:57:19 radius,debug,packet       0101005125446993262b7372b8de0428 
17:57:19 radius,debug,packet       b6533616f6fecc7e82b750c832ec3cee 
17:57:19 radius,debug,packet       b6c70d958367baba8f49549e0ae70aa1 
17:57:19 radius,debug,packet       d082a963842d5fc6f485271074bf1fc5 
17:57:19 radius,debug,packet       5fd6b3e130f8e71bad26c0a052e915c6 
17:57:19 radius,debug,packet       908f88b9760c2a6cf7cd6bc6a0 
17:57:19 radius,debug,packet     EAP-Message = 0xcace4ce9ff8946dd13f8dc0d9effbb5f 
17:57:19 radius,debug,packet       a6aba33bf83e6e7b3bef2814443d1e60 
17:57:19 radius,debug,packet       ba47a7b4ae2de785e66666a75c0c24db 
17:57:19 radius,debug,packet       34a25bc922e3edde166345d485f37575 
17:57:19 radius,debug,packet       43aeeef4ea0b52e258d9cb6707eda49e 
17:57:19 radius,debug,packet       7a43801636944aa7d8bd9d91fed028c6 
17:57:19 radius,debug,packet       cadad2b52b9d9f5f6de30cbfb1e36d80 
17:57:19 radius,debug,packet       ab7be64e507c9829fe89a8db3b415398 
17:57:19 radius,debug,packet       6cfe8d695528fd5c1b139670699f7d7a 
17:57:19 radius,debug,packet       d4a6cc5929a610d6abf7c06117c4b85f 
17:57:19 radius,debug,packet       c9ac17be7c2316030100861000008200 
17:57:19 radius,debug,packet       8010d50ace8e497612c54d0daa4753e7 
17:57:19 radius,debug,packet       c71f7c314d3b149f9a3464a65cb37390 
17:57:19 radius,debug,packet       243eba1515adadffd9474480b30c3fbb 
17:57:19 radius,debug,packet       3764c503ba74d9d7d1b1e17bdaed9b79 
17:57:19 radius,debug,packet       abab1716b648a9a2fe156652df 
17:57:19 radius,debug,packet     EAP-Message = 0xffe6d447b57a3046e268b3bf6fc093d4 
17:57:19 radius,debug,packet       cdea27d49224dbd355eda7cd84360f8f 
17:57:19 radius,debug,packet       f9152a278f4e4b7f8d797f1302577735 
17:57:19 radius,debug,packet       952968ee16030100860f000082008003 
17:57:19 radius,debug,packet       fcae495f7a8a438c3d6f466a147962e9 
17:57:19 radius,debug,packet       8afe8698fc5e5983e74b142bc8caa6d4 
17:57:19 radius,debug,packet       e00b65bbafa5556090d5118ea563681b 
17:57:19 radius,debug,packet       e6f4604cb72123b1ffaeedc648f74047 
17:57:19 radius,debug,packet       efc22eeb6b15bb8086bd6b85fa034cea 
17:57:19 radius,debug,packet       4c1152163aceb45e0a87cd1f5cd37b34 
17:57:19 radius,debug,packet       b76fd3f5db51112491c6136c148fa566 
17:57:19 radius,debug,packet       f870ab6e65ff8e8965f9dbbecab31b14 
17:57:19 radius,debug,packet       03010001011603010030daf9369f9e14 
17:57:19 radius,debug,packet       3d0cf8ad718a0b415fb5502aed57fdf9 
17:57:19 radius,debug,packet       3922c0f6b4e86a130f8b954a0126d190 
17:57:19 radius,debug,packet       fa14ee3051b32276cca1 
17:57:19 radius,debug,packet     Message-Authenticator = 0xe8ecfd63e5b9f10ce26b8872f9844ba6 
17:57:19 radius,debug,packet     NAS-Identifier = "MikroTik" 
17:57:19 radius,debug,packet     NAS-IP-Address = 172.16.104.2 
17:57:19 radius,debug,packet received Access-Challenge with id 33 from 172.16.102.3:1812 
17:57:19 radius,debug,packet     Signature = 0xcb07231c70c80197ac2b41558c10957f 
17:57:19 radius,debug,packet     Session-Timeout = 30 
17:57:19 radius,debug,packet     EAP-Message = 0x010600450d800000003b140301000101 
17:57:19 radius,debug,packet       1603010030a6200e75a8635c7d1f3b71 
17:57:19 radius,debug,packet       79ccf2835a3d1413d5b12d1e4617d633 
17:57:19 radius,debug,packet       ba971a41ca09175864c1d3d56ccab424 
17:57:19 radius,debug,packet       b6a71b5b52 
17:57:19 radius,debug,packet     State = 0x6bcc087c0000013700011700fe800000 
17:57:19 radius,debug,packet       00000000c17aafd471f2106c00000004 
17:57:19 radius,debug,packet       14808cec 
17:57:19 radius,debug,packet     Message-Authenticator = 0x54df8ee66eaf3c65e46474c877c87b2a 
17:57:19 radius,debug received reply for 58:28 
17:57:19 radius,debug new request 58:29 code=Access-Request service=wireless called-id=02-0C-42-3A-C4-08:moshpit 
17:57:19 radius,debug sending 58:29 to 172.16.102.3:1812 
17:57:19 radius,debug,packet sending Access-Request with id 34 to 172.16.102.3:1812 
17:57:19 radius,debug,packet     Signature = 0x95ce7ecea6e0909ed48442e43b011fa1 
17:57:19 radius,debug,packet     Service-Type = 2 
17:57:19 radius,debug,packet     Framed-MTU = 1400 
17:57:19 radius,debug,packet     User-Name = "tim" 
17:57:19 radius,debug,packet     State = 0x6bcc087c0000013700011700fe800000 
17:57:19 radius,debug,packet       00000000c17aafd471f2106c00000004 
17:57:19 radius,debug,packet       14808cec 
17:57:19 radius,debug,packet     NAS-Port-Id = "wlan3" 
17:57:19 radius,debug,packet     Calling-Station-Id = "5C-59-48-DF-0D-2C" 
17:57:19 radius,debug,packet     Called-Station-Id = "02-0C-42-3A-C4-08:moshpit" 
17:57:19 radius,debug,packet     EAP-Message = 0x020600060d00 
17:57:19 radius,debug,packet     Message-Authenticator = 0x14875af03ff7da157dffc492de10730b 
17:57:19 radius,debug,packet     NAS-Identifier = "MikroTik" 
17:57:19 radius,debug,packet     NAS-IP-Address = 172.16.104.2 
17:57:19 radius,debug,packet received Access-Accept with id 34 from 172.16.102.3:1812 
17:57:19 radius,debug,packet     Signature = 0x49a84a151181e39e82d4c42718c2087d 
17:57:19 radius,debug,packet     Acct-Interim-Interval = 300 
17:57:19 radius,debug,packet     Framed-Protocol = 1 
17:57:19 radius,debug,packet     Service-Type = 2 
17:57:19 wireless,info 5C:59:48:DF:0D:2C@wlan3: disconnected, 802.1x authentication failed 
17:57:19 radius,debug,packet     EAP-Message = 0x03060004 
17:57:19 radius,debug,packet     Class = 0xce800b360000013700011700fe800000 
17:57:19 radius,debug,packet       00000000c17aafd471f2106c01cb877a 
17:57:19 radius,debug,packet       70c095a4000000000000098b 
17:57:19 radius,debug,packet     MS-Link-Utilizatoin-Threshold = 50 
17:57:19 radius,debug,packet     MS-Link-Drop-Time-Limit = 120 
17:57:19 radius,debug,packet     MS-MPPE-Send-Key = 0x82b799dc96602ff8f25ce58454e0ce1e 
17:57:19 radius,debug,packet       626525e5becb692cf5962d37202c89e8 
17:57:19 radius,debug,packet       a32f3f027120c6513f16f73ed13b4039 
17:57:19 radius,debug,packet       a330 
17:57:19 radius,debug,packet     MS-MPPE-Recv-Key = 0x82b8398d8c80098b263f79ae6820c356 
17:57:19 radius,debug,packet       69b3ac8a0e75f6c35b85e46ffdc4ee7b 
17:57:19 radius,debug,packet       d9af27ad578608fc455d1f208ea40dc9 
17:57:19 radius,debug,packet       0d82 
17:57:19 radius,debug,packet     Message-Authenticator = 0xe787623ecbafec675071dfc052d74133 
17:57:19 radius,debug received reply for 58:29

And downgrading back to the previous RC4 build dated 11/5 I had on it. Works like a champ.

18:20:49 radius,debug new request 58:13 code=Access-Request service=wireless called-id=02-0C-42-3A-C4-08:moshpit 
18:20:49 radius,debug sending 58:13 to 172.16.102.3:1812 
18:20:49 radius,debug,packet sending Access-Request with id 14 to 172.16.102.3:1812 
18:20:49 radius,debug,packet     Signature = 0x42a710e9f842bc23bdc13cec2c884990 
18:20:49 radius,debug,packet     Service-Type = 2 
18:20:49 radius,debug,packet     Framed-MTU = 1400 
18:20:49 radius,debug,packet     User-Name = "tim" 
18:20:49 radius,debug,packet     State = 0x6bde088e0000013700011700fe800000 
18:20:49 radius,debug,packet       00000000c17aafd471f2106c00000004 
18:20:49 radius,debug,packet       14808cfe 
18:20:49 radius,debug,packet     NAS-Port-Id = "wlan3" 
18:20:49 radius,debug,packet     Calling-Station-Id = "5C-59-48-DF-0D-2C" 
18:20:49 radius,debug,packet     Called-Station-Id = "02-0C-42-3A-C4-08:moshpit" 
18:20:49 radius,debug,packet     EAP-Message = 0x020502f40d0030818606082b06010505 
18:20:49 radius,debug,packet       073002867a687474703a2f2f70736733 
18:20:49 radius,debug,packet       2e706f736974697665736f6c7574696f 
18:20:49 radius,debug,packet       6e7367726f75702e6f66666963652f43 
18:20:49 radius,debug,packet       657274456e726f6c6c2f505347332e70 
18:20:49 radius,debug,packet       6f736974697665736f6c7574696f6e73 
18:20:49 radius,debug,packet       67726f75702e6f66666963655f706f73 
18:20:49 radius,debug,packet       6974697665736f6c7574696f6e736772 
18:20:49 radius,debug,packet       6f75702d505347332d43412e63727430 
18:20:49 radius,debug,packet       0d06092a864886f70d01010505000382 
18:20:49 radius,debug,packet       0101005125446993262b7372b8de0428 
18:20:49 radius,debug,packet       b6533616f6fecc7e82b750c832ec3cee 
18:20:49 radius,debug,packet       b6c70d958367baba8f49549e0ae70aa1 
18:20:49 radius,debug,packet       d082a963842d5fc6f485271074bf1fc5 
18:20:49 radius,debug,packet       5fd6b3e130f8e71bad26c0a052e915c6 
18:20:49 radius,debug,packet       908f88b9760c2a6cf7cd6bc6a0 
18:20:49 radius,debug,packet     EAP-Message = 0xcace4ce9ff8946dd13f8dc0d9effbb5f 
18:20:49 radius,debug,packet       a6aba33bf83e6e7b3bef2814443d1e60 
18:20:49 radius,debug,packet       ba47a7b4ae2de785e66666a75c0c24db 
18:20:49 radius,debug,packet       34a25bc922e3edde166345d485f37575 
18:20:49 radius,debug,packet       43aeeef4ea0b52e258d9cb6707eda49e 
18:20:49 radius,debug,packet       7a43801636944aa7d8bd9d91fed028c6 
18:20:49 radius,debug,packet       cadad2b52b9d9f5f6de30cbfb1e36d80 
18:20:49 radius,debug,packet       ab7be64e507c9829fe89a8db3b415398 
18:20:49 radius,debug,packet       6cfe8d695528fd5c1b139670699f7d7a 
18:20:49 radius,debug,packet       d4a6cc5929a610d6abf7c06117c4b85f 
18:20:49 radius,debug,packet       c9ac17be7c2316030100861000008200 
18:20:49 radius,debug,packet       80b101375460e709b07de19e352e1833 
18:20:49 radius,debug,packet       4c5d19cfd8cef06cea6641e16b495f1d 
18:20:49 radius,debug,packet       150793feb3382d50031a9b2aedd4d193 
18:20:49 radius,debug,packet       4d14e1a47f4505e394b33a53303dc227 
18:20:49 radius,debug,packet       d4c36598559db5c7bec5475782 
18:20:49 radius,debug,packet     EAP-Message = 0x41d52a60434256921f67c0906a948964 
18:20:49 radius,debug,packet       494e480a6b60e5cd8c6aca017640044c 
18:20:49 radius,debug,packet       4a1edb037fb1178db8fbf5252239fcb3 
18:20:49 radius,debug,packet       739bf78416030100860f00008200803c 
18:20:49 radius,debug,packet       210ece47c0e3e10d07715d4c99cc9a39 
18:20:49 radius,debug,packet       fb1cacd3fd125fd75d4b5fd4d82e650c 
18:20:49 radius,debug,packet       224b47c6567e7fbef8310c2fe1d5187a 
18:20:49 radius,debug,packet       0fbc23f0920c7701180e4ffdd2a5586d 
18:20:49 radius,debug,packet       17a6047ceef058a977212b0ebd58404a 
18:20:49 radius,debug,packet       3a71c76668bdb8d94f9a0e8c1ebe91df 
18:20:49 radius,debug,packet       78277a2a0fd3692f03dc1ed31b77d579 
18:20:49 radius,debug,packet       b46113c79be8785634fcc303ac317e14 
18:20:49 radius,debug,packet       03010001011603010030b3b03d28fc24 
18:20:49 radius,debug,packet       262efe9bcb69854241fb54cd1a0e8762 
18:20:49 radius,debug,packet       bfa3ee36fd07655760fc38c955652022 
18:20:49 radius,debug,packet       9cb129fd9a0e4071cc50 
18:20:49 radius,debug,packet     Message-Authenticator = 0xf6eaf5144a2e5f75300df20ed649d44f 
18:20:49 radius,debug,packet     NAS-Identifier = "MikroTik" 
18:20:49 radius,debug,packet     NAS-IP-Address = 172.16.104.2 
18:20:49 radius,debug,packet received Access-Challenge with id 14 from 172.16.102.3:1812 
18:20:49 radius,debug,packet     Signature = 0x82f1fe6b437092992ca8c7cf54aa3724 
18:20:49 radius,debug,packet     Session-Timeout = 30 
18:20:49 radius,debug,packet     EAP-Message = 0x010600450d800000003b140301000101 
18:20:49 radius,debug,packet       1603010030129f8a26fbc9fe86f1407e 
18:20:49 radius,debug,packet       9fb5cf59f4c9e6891f426095b662f3b9 
18:20:49 radius,debug,packet       e775c5f679ab7098e936a8655563a1be 
18:20:49 radius,debug,packet       50d8bf566b 
18:20:49 radius,debug,packet     State = 0x6bde088e0000013700011700fe800000 
18:20:49 radius,debug,packet       00000000c17aafd471f2106c00000004 
18:20:49 radius,debug,packet       14808cfe 
18:20:49 radius,debug,packet     Message-Authenticator = 0x15c9ad8eb759c73f4dbbee8bea5232dc 
18:20:49 radius,debug received reply for 58:13 
18:20:49 radius,debug new request 58:14 code=Access-Request service=wireless called-id=02-0C-42-3A-C4-08:moshpit 
18:20:49 radius,debug sending 58:14 to 172.16.102.3:1812 
18:20:49 radius,debug,packet sending Access-Request with id 15 to 172.16.102.3:1812 
18:20:49 radius,debug,packet     Signature = 0x3abb6bde0518e6b051345c23de805a6d 
18:20:49 radius,debug,packet     Service-Type = 2 
18:20:49 radius,debug,packet     Framed-MTU = 1400 
18:20:49 radius,debug,packet     User-Name = "tim" 
18:20:49 radius,debug,packet     State = 0x6bde088e0000013700011700fe800000 
18:20:49 radius,debug,packet       00000000c17aafd471f2106c00000004 
18:20:49 radius,debug,packet       14808cfe 
18:20:49 radius,debug,packet     NAS-Port-Id = "wlan3" 
18:20:49 radius,debug,packet     Calling-Station-Id = "5C-59-48-DF-0D-2C" 
18:20:49 radius,debug,packet     Called-Station-Id = "02-0C-42-3A-C4-08:moshpit" 
18:20:49 radius,debug,packet     EAP-Message = 0x020600060d00 
18:20:49 radius,debug,packet     Message-Authenticator = 0xab217d5aa7c7bafef832193b6ef9e023 
18:20:49 radius,debug,packet     NAS-Identifier = "MikroTik" 
18:20:49 radius,debug,packet     NAS-IP-Address = 172.16.104.2 
18:20:49 radius,debug,packet received Access-Accept with id 15 from 172.16.102.3:1812 
18:20:49 radius,debug,packet     Signature = 0xa025e275f2a847b8e1bd1ef5253e2fd6 
18:20:49 radius,debug,packet     Acct-Interim-Interval = 300 
18:20:49 radius,debug,packet     Framed-Protocol = 1 
18:20:49 radius,debug,packet     Service-Type = 2 
18:20:49 radius,debug,packet     EAP-Message = 0x03060004 
18:20:49 radius,debug,packet     Class = 0xcec80b7e0000013700011700fe800000 
18:20:49 radius,debug,packet       00000000c17aafd471f2106c01cb877a 
18:20:49 radius,debug,packet       70c095a400000000000009d3 
18:20:49 radius,debug,packet     MS-Link-Utilizatoin-Threshold = 50 
18:20:49 radius,debug,packet     MS-Link-Drop-Time-Limit = 120 
18:20:49 radius,debug,packet     MS-MPPE-Send-Key = 0x82c7a535689c99e3bfb5bc41e2ade978 
18:20:49 radius,debug,packet       012b8931027ed45b9ff831cb944f1a4d 
18:20:49 radius,debug,packet       fdda1420b98db0a82ca3f9fc32d3a6de 
18:20:49 radius,debug,packet       dcc6 
18:20:49 radius,debug,packet     MS-MPPE-Recv-Key = 0x82c8df98b9fffbd6b06bdd07522e6893 
18:20:49 radius,debug,packet       619ca8468b1a1e4becdc88e68d9a9461 
18:20:49 radius,debug,packet       7f979281cc1ab6d50348ba5a5ff74393 
18:20:49 radius,debug,packet       a484 
18:20:49 radius,debug,packet     Message-Authenticator = 0xf3e704078a33635a85dc682f22a1af2b 
18:20:49 radius,debug received reply for 58:14

Me thinks the changes made in RADIUS somehow FUBAR'd it.

Also, My RB1100 was running fine for 10 days not dropping ethernet connections. I upgraded it from the 5.0RC4 I had before THIS 5.0RC4 and also upgraded the boot loader. Now It drops link to my RB433AH, DSL modem, and D-Link DES-3028 approximately ever 4-5 minutes for 2 seconds. I just downgraded to 5.0RC2 on my 1100 and the problem persists. Then subsequently upgraded it to 5.0RC4 dated 11/9 which previously worked and everything is fine.... (Scratch that. Not fine. Just took longer. Trying to dowgrade firmware to 2.27 from 2.28 Wil report back)

So... Summary.

5.0RC4 mipsbe build date 11/05 works for WPA-EAP, 5.0RC4 build date 11/22 does not.
5.0RC4 powerpc build date 11/09 w/ FW 2.27 on RB1100 keeps link on ports 11-13, 5.0RC4 powerpc build date 11/22 w/ FW 2.28 seems to revert back to previous behavior of dropping link. Trying 11/09 5.0RC4 w/ FW 2.27...

What pain in my nuts.. All I wanted to do was watch some Netflix tonight... GACK!

roadracer96 · Tue Nov 23, 2010 1:53 am

And the interface dropped off again...

I dunno what to do here... It WAS working for days on end, then on the first reboot afterwards, it stops...

mars · Tue Nov 23, 2010 1:57 am

nv2 protocol is dropping the links as well
was ok in first rc4 release
no wds
ptp link

NetworkPro · Tue Nov 23, 2010 2:01 am

mars, please elaborate
- WDS/no WDS?
- PtMP / PtP ?

Chupaka · Tue Nov 23, 2010 2:24 am

*) fixed pcq queue type;
What does that mean?

+1

MT Staff, please clarify a bit...

rmichael · Tue Nov 23, 2010 2:30 am

It means that you would help if you could please test it.

For example - you have a router with PCQ configured passing a lot of traffic. Install the latest RC4 and see if all is fine - traffic distribution and ping times. Compare to previous version.

If your clients have 20mbits and above, configured with PCQ, even better. Since this needs testing. Based on my experience.

Thank you.

Do you know what was broken with PCQ? I have not noticed a problem (or blamed it on something else) but would like to know what was fixed so I can look for symptoms.

thanks.

janisk · Tue Nov 23, 2010 8:59 am

PCQ was worked on to improve performance on high and low throughput sites. In addition, it received some multi-core tweaks.

janisk · Tue Nov 23, 2010 9:18 am

first BUG in rc4

rb411ah

[admin@mt] > system health pri
voltage: 1245V

;-P

maybe it suppose to be a 12.45v

can you try this board with higher voltage PSU, something like 18V or 24V? And are you sure you are running latest build. Anyway, create supout.rif file and send it to support@mikrotik.com

mangust · Tue Nov 23, 2010 11:32 am

RB750:

alexspils · Tue Nov 23, 2010 11:45 am

RB411AH, 24V PSU

Tue Nov 23, 2010 11:59 am

Chupaka, how do you like the winbox changes ?

Beccara · Tue Nov 23, 2010 12:07 pm

I have to say very nice on the winbox fix's, v6 route crashing was a major PITA along with the v6 route filters. The TE interface is awesome and SNMP was a nice surprise!

Now can we have v6 winbox?

Tue Nov 23, 2010 12:09 pm

RB750:

It doesn't have a voltage monitor!

Chupaka · Tue Nov 23, 2010 12:55 pm

Chupaka, how do you like the winbox changes ?

thanks, much more handy =)

let's go further: Terminal window. open Terminal, type something. Alt+Tab to another window, Alt+Tab back to Winbox. Winbox window is active, Terminal window is selected. type something. oops

you must click Terminal window - nothing changes visually, but now you can type again =)

axiang · Tue Nov 23, 2010 8:47 pm

/ Ip dns cache part of the problem
If you modify a particular configuration using the command
Some configuration will be lost or reset

NetworkPro · Tue Nov 23, 2010 10:23 pm

axiang give more information

YazzY · Wed Nov 24, 2010 1:41 am

Me thinks the changes made in RADIUS somehow FUBAR'd it.

Same here, Radius authentication of PPTP users stopped working. It works with RC2 and RC3.

Wed Nov 24, 2010 10:04 am

Me thinks the changes made in RADIUS somehow FUBAR'd it.
Same here, Radius authentication of PPTP users stopped working. It works with RC2 and RC3.

please provide us more infromation - just checked RouterOS v5.0rc4 PPTP server is working fine with RADIUS server.

axiang · Wed Nov 24, 2010 7:08 pm

Oh, that is the case
. . For example, I set the DNS service has 3 IP. .
I use the command to modify cache-max-ttl
Then the third will be lost IP Services

. . .
I have some static content and then some of the project started some of the disabled
Modified so as static also followed changes TTL ttl
Use the command [find] ttl = 1h is disabled then all the content will be enabled

-------------------------

[admin@Xiang] /ip dns> pri
servers: 211.162.61.235,211.162.62.1,211.162.62.2
allow-remote-requests: yes
max-udp-packet-size: 1024
cache-size: 204800KiB
cache-max-ttl: 1h
cache-used: 1033KiB
[admin@Xiang] /ip dns> set cache-max-ttl=1h
[admin@Xiang] /ip dns> pri
servers: 211.162.61.235,211.162.62.1
allow-remote-requests: yes
max-udp-packet-size: 1024
cache-size: 204800KiB
cache-max-ttl: 1h
cache-used: 1033KiB
[admin@Xiang] /ip dns>

----------------------

petro25 · Wed Nov 24, 2010 7:19 pm

111111 · Thu Nov 25, 2010 1:12 am

is something has been changed to SNMP v1 my cacti stop to draw
when i change to SNMP v2 all ok except disk and memory graphs

also some updates hire http://mikrotik.com/download/Mikrotik.mib

roadracer96 · Thu Nov 25, 2010 6:03 am

I upgraded one of my SSTP routers today... Everything works, but now its saying cryptobinding skipped. I use MSCHAPv2 for auth and previously, using MSCHAPv2 made the cryptobinding thing go away. Th

22:57:14 sstp,info <sstp-0>: waiting for call... 
22:57:35 sstp,info <sstp-0>: authenticated 
22:57:36 sstp,info no mppe keys, cryptobinding skipped 
22:57:52 sstp,info <sstp-0>: connected 
22:57:52 sstp,info,account xxx logged in, 1.2.3.4

The RADIUS reply is giving MPPE keys....

22:54:34 radius,debug new request 1b:b6 code=Access-Request service=ppp called-id=0.0.0.0 
22:54:34 radius,debug sending 1b:b6 to 1.2.3.4:1812 
22:54:34 radius,debug,packet sending Access-Request with id 113 to 1.2.3.4:1812 
22:54:34 radius,debug,packet     Signature = 0xed1bc3ed4e3ca156acdfbd0ee8f88f38 
22:54:34 radius,debug,packet     Service-Type = 2 
22:54:34 radius,debug,packet     Framed-Protocol = 1 
22:54:34 radius,debug,packet     NAS-Port = 61 
22:54:34 radius,debug,packet     NAS-Port-Type = 0 
22:54:34 radius,debug,packet     User-Name = "xxxxxx" 
22:54:34 radius,debug,packet     Calling-Station-Id = "1.2.3.4" 
22:54:34 radius,debug,packet     Called-Station-Id = "0.0.0.0" 
22:54:34 radius,debug,packet     MS-CHAP-Challenge = 0x057077b55a60ac51a95981582f258529 
22:54:34 radius,debug,packet     MS-CHAP2-Response = 0x0100843c881577d2c2ef2ec4e2570e78 
22:54:34 radius,debug,packet       f4b900000000000000001524ba565384 
22:54:34 radius,debug,packet       d94898aed69f35d3cb9575249349f405 
22:54:34 radius,debug,packet       c395 
22:54:34 radius,debug,packet     NAS-Identifier = "vpn-2" 
22:54:34 radius,debug,packet     NAS-IP-Address = 1.2.3.4 
22:54:34 radius,debug,packet received Access-Accept with id 113 from 1.2.3.4:1812 
22:54:34 radius,debug,packet     Signature = 0x840ecc2c002fb43ccce0f4f10a635950 
22:54:34 radius,debug,packet     Framed-Protocol = 1 
22:54:34 radius,debug,packet     Framed-Compression = 1 
22:54:34 radius,debug,packet     Framed-IP-Address = 1.2.3.4 
22:54:34 radius,debug,packet     Idle-Timeout = 300 
22:54:34 radius,debug,packet     Session-Timeout = 0 
22:54:34 radius,debug,packet     MS-CHAP2-Success = 0x01533d31413731423942443132413437 
22:54:34 radius,debug,packet       30304146363737434444383531443530 
22:54:34 radius,debug,packet       4643453533334246414630 
22:54:34 radius,debug,packet     MS-MPPE-Recv-Key = 0xd558edbf68032cbcb22c5d22055ba958 
22:54:34 radius,debug,packet       6bb05f9c00b24d810624330d960aad7d 
22:54:34 radius,debug,packet       00ee 
22:54:34 radius,debug,packet     MS-MPPE-Send-Key = 0xd99fd236643e3a1de1b350900e5f05f7 
22:54:34 radius,debug,packet       511a6272998373aa358d3f159abc2b05 
22:54:34 radius,debug,packet       96e9 
22:54:34 radius,debug,packet     MS-MPPE-Encryption-Policy = 1 
22:54:34 radius,debug,packet     MS-MPPE-Encryption-Type = 6 
22:54:34 radius,debug received reply for 1b:b6

Alessio Garavano · Thu Nov 25, 2010 9:37 am

Grrrrrr! first RB upgraded at 20km and OUT of reach! DIED! tomorrow go to see what´s up!

NetworkPro · Thu Nov 25, 2010 9:46 am

That's why you should update a test one with physical access first. As I already mentioned in my second post in this topic.

YazzY · Thu Nov 25, 2010 11:53 am

Me thinks the changes made in RADIUS somehow FUBAR'd it.
Same here, Radius authentication of PPTP users stopped working. It works with RC2 and RC3.
please provide us more infromation - just checked RouterOS v5.0rc4 PPTP server is working fine with RADIUS server.

Did you check with MSCHAPv2 ?

Thu Nov 25, 2010 2:11 pm

please contact support - we will provide you with a test release where the radius problem should be fixed.

Alessio Garavano · Thu Nov 25, 2010 6:14 pm

Grrrrrr! first RB upgraded at 20km and OUT of reach! DIED! tomorrow go to see what´s up!

All was because the RB had the 4.13 with the "wireless-NV2" package enabled and the "wireless" disabled, in the upgrade the nv2 package not exist and the wireless staying disabled...

Bridge Filters is not working yet... for now i am using "Use IP Firewall" to add AntiDHCP and Isolations controls in Layer 2

NetworkPro · Thu Nov 25, 2010 9:53 pm

All was because the RB had the 4.13 with the "wireless-NV2" package enabled and the "wireless" disabled, in the upgrade the nv2 package not exist and the wireless staying disabled...

The most often cause to travel to a router since the old versions of 2.8. Extra caution is needed when upgrading over wireless. Could be overcome with a script.

Alessio Garavano · Thu Nov 25, 2010 10:05 pm

All was because the RB had the 4.13 with the "wireless-NV2" package enabled and the "wireless" disabled, in the upgrade the nv2 package not exist and the wireless staying disabled...
The most often cause to travel to a router since the old versions of 2.8. Extra caution is needed when upgrading over wireless. Could be overcome with a script.

Share an example please!

roadracer96 · Fri Nov 26, 2010 4:01 am

Can someone post the download link for the "fixed" 5.0rc4? With working RADIUS? I could downgrade, but there are a couple fixes in RADIUS that I want to use... Already emailed support, but dont wanna wait for them to email me the link.

mipsbe and powerpc.

Fri Nov 26, 2010 7:52 am

Can someone post the download link for the "fixed" 5.0rc4? With working RADIUS? I could downgrade, but there are a couple fixes in RADIUS that I want to use... Already emailed support, but dont wanna wait for them to email me the link.

mipsbe and powerpc.

http://www.mikrotik.com/download/share/ ... 5_0rc5.npk
http://www.mikrotik.com/download/share/ ... 5_0rc5.npk
http://www.mikrotik.com/download/share/ ... 5_0rc5.npk
http://www.mikrotik.com/download/share/ ... 5_0rc5.npk

Fri Nov 26, 2010 11:35 am

http://www.mikrotik.com/download/share/ ... 5_0rc5.npk
http://www.mikrotik.com/download/share/ ... 5_0rc5.npk
http://www.mikrotik.com/download/share/ ... 5_0rc5.npk
http://www.mikrotik.com/download/share/ ... 5_0rc5.npk

Did anyone noticed this (attachment) ?? O_o

Fri Nov 26, 2010 11:52 am

interesting, it looks like PCQ is getting some fancy updates.

Chupaka · Fri Nov 26, 2010 6:05 pm

OMFG!.. seems like they are working on PCQ hardly - nice to hear that!

stanioomega · Fri Nov 26, 2010 11:57 pm

Can someone post the download link for the "fixed" 5.0rc4? With working RADIUS? I could downgrade, but there are a couple fixes in RADIUS that I want to use... Already emailed support, but dont wanna wait for them to email me the link.

mipsbe and powerpc.
http://www.mikrotik.com/download/share/ ... 5_0rc5.npk
http://www.mikrotik.com/download/share/ ... 5_0rc5.npk
http://www.mikrotik.com/download/share/ ... 5_0rc5.npk
http://www.mikrotik.com/download/share/ ... 5_0rc5.npk

All packages pls ...

Chupaka · Sat Nov 27, 2010 3:08 am

there's no separate packages for inofficial versions. wait for RC5 release

NetworkPro · Sun Nov 28, 2010 10:03 pm

MikroTik guys,

please share the UserManager npk
with each RC you share,
if you think its safe for me to test it IN PRODUCTION.

Thank you.

Sun Nov 28, 2010 11:20 pm

I hope rc5 has DHCPv6 support, IPv6 has become reality for us much quicker than anticipated, and we need DHCPv6 as that is what most ISP's here are using.

AlexKV · Mon Nov 29, 2010 1:09 pm

Hyper-V (legacy network adapter)
4.XX - all OK
5.0 beta - network card ether1 detected, I can assign IP addr, but all packets (in/out through this ether1) unreachable.

axiang · Mon Nov 29, 2010 1:37 pm

Encountered a problem
In / ip firewall nat
Finally, I double-click an item arranged in
Unexpected situations occurred in a particular nat entry has been moved to the position of unpredictable
Double-click the last one is equal to the project if the same mobile operating normally
There is no operational errors I tried many times

janisk · Mon Nov 29, 2010 2:37 pm

Hyper-V (legacy network adapter)
4.XX - all OK
5.0 beta - network card ether1 detected, I can assign IP addr, but all packets (in/out through this ether1) unreachable.

if you can, create supout.rif file from version that it is not working with. (even maybe rc5) and send it to support@mikrotik.com, so we can check what is happening (or not) and fix this. Just add full explanation on what the problem is to the e-mail also.

edit: or check your your virtual machine ( as i suspect it could be) try to set other type of interface.

ayufan · Mon Nov 29, 2010 2:58 pm

edit: or check your your virtual machine ( as i suspect it could be) try to set other type of interface.

I can confirm that 5.0 doesn't work on Hyper-V while 4.x works.

Regarding changing interface type. There are only two:
- legacy network adapter - emulates network device, uses drivers included in linux kernel
- network adapter - requires special drivers and uses vmbus for communication (much, much faster)

Kamil

janisk · Mon Nov 29, 2010 3:45 pm

if you are completely sure, send supout.rif file as i asked in my previous post.

AlexKV · Mon Nov 29, 2010 4:21 pm

Hyper-V (legacy network adapter)
4.XX - all OK
5.0 beta - network card ether1 detected, I can assign IP addr, but all packets (in/out through this ether1) unreachable.
if you can, create supout.rif file from version that it is not working with. (even maybe rc5) and send it to support@mikrotik.com, so we can check what is happening (or not) and fix this. Just add full explanation on what the problem is to the e-mail also.
edit: or check your your virtual machine ( as i suspect it could be) try to set other type of interface.

I send extended mail to support without supout.rif - I can not save it without network.

PS: I use ONLY "legacy network adapter".
I try it on 2 Hyper-V server (HP, DELL) with different hardware nic's.

mangust · Mon Nov 29, 2010 5:26 pm

I send extended mail to support without supout.rif - I can not save it without network.

make supout.rif on 5.x, downgrade do 4.x , send to MT Team

log · Tue Nov 30, 2010 11:32 am

Traffic show stats only for Tx, strange because at other side shows ok, first is AP bridge second is station wds.
AP:

AP.jpg

At the same time:

station.jpg

mjoksimovic · Tue Nov 30, 2010 6:00 pm

Routers are freezing constantly if using NV2 or NV2 NSTREME instead classic NSTREME. This is happening on every of 48 x86 machines on the network. RBs working ok. Tried to disable multi-cpu=no on machines which have single core and to reduce hw-retries to lower values, for example to 10 but nothing. If bandwidth through links becomes in full load, routers disconnect from links and it is not possible anything but power unplugging and reswitching on. We use 5GHz-A, 40MHz channel.

NSTREME working perfectly on 4.13 and 5.0RC4 and pre-RC5.

alexspils · Tue Nov 30, 2010 8:15 pm

enable watchdog with automatic supout and send file to mikrotik if you want to help fix this

petro25 · Wed Dec 01, 2010 2:54 pm

problem dude 4 beta 1
os 5 RC 4

omidkosari · Wed Dec 01, 2010 3:16 pm

any chance to support pppoe option 82 in rc5 ? http://forum.mikrotik.com/viewtopic.php?f=2&t=42698

NetworkPro · Wed Dec 01, 2010 4:15 pm

petro23,

what exactly is the problem, please explain in more detail.

Thank you.

petro25 · Wed Dec 01, 2010 6:20 pm

At inclusion of control by means of the program dude it is sharp down throughput of a communication channel and increase ping between points by radio with 4 мс to 12 мс.

Chupaka · Wed Dec 01, 2010 6:29 pm

and what about CPU load?

petro25 · Wed Dec 01, 2010 7:28 pm

dudle on
rb 433 - cpu 60- 75 %
rb 411 - cpu 45- 60%
rb 800 - cpu 25- 40 %
rb 600 - cpu 75 - 80 %
rate 56 Mb

dudle off
rb 433 - cpu 56- 63 %
rb 411 - cpu 40- 50 %
rb 800 - cpu 25- 38 %
rb 600 - cpu 50 - 57 %
rate 56 Mb

brdge + WDS no route no nat

petro25 · Wed Dec 01, 2010 7:48 pm

rb 800
http://178.49.144.5:12111/graphs/

rb 600
http://178.49.144.6/graphs/

mindaugasr · Thu Dec 02, 2010 9:26 am

Hello,
I have issue with traffic flow in rc4, in rc3 works fine, does anyone have problems with traffic flow and rc4?
Flow stop after some time, incorrect flow, not complete and so on...
Thanks

omega-00 · Thu Dec 02, 2010 11:23 am

*) added hotspot html variable "host-ip";

What's this for and what does it do?

Thu Dec 02, 2010 12:38 pm

*) added hotspot html variable "host-ip";
What's this for and what does it do?

It shows you the IP address which is equivalent of the "Address" variable of the Hostpot/Hosts table.

timtasse · Thu Dec 02, 2010 1:07 pm

hi,

i have a great problem with rc4 and rc5pre.
i think the ssh daemon is crashing.

after reboot or restarting the ssh service under "ip service dis ssh ; ip service en ssh",
it works for 10 seconds and then the port is closed, you can see this with tcptraceroute on port 22
then i have done a downgrade to rc3 and ssh works but there dont work my firewall rules,
it has accepted all packets - very evil.

now i have beta6 and all works fine.

is there some problems known ?

Thu Dec 02, 2010 1:26 pm

hi,

i have a great problem with rc4 and rc5pre.
i think the ssh daemon is crashing.

after reboot or restarting the ssh service under "ip service dis ssh ; ip service en ssh",
it works for 10 seconds and then the port is closed, you can see this with tcptraceroute on port 22
then i have done a downgrade to rc3 and ssh works but there dont work my firewall rules,
it has accepted all packets - very evil.

now i have beta6 and all works fine.

is there some problems known ?

please check your email - we sent you a new test release which has fixes to ssh. Please report back after testing that.

timtasse · Thu Dec 02, 2010 2:03 pm

hi,

i have a great problem with rc4 and rc5pre.
i think the ssh daemon is crashing.

after reboot or restarting the ssh service under "ip service dis ssh ; ip service en ssh",
it works for 10 seconds and then the port is closed, you can see this with tcptraceroute on port 22
then i have done a downgrade to rc3 and ssh works but there dont work my firewall rules,
it has accepted all packets - very evil.

now i have beta6 and all works fine.

is there some problems known ?
please check your email - we sent you a new test release which has fixes to ssh. Please report back after testing that.

i have installed the new version.
all works fine -> SSH works and all firewall rules are work

thx

NetworkPro · Thu Dec 02, 2010 10:43 pm

RC4 - Working with Mangle - there seems to be a bug with WinBox that moves the Mangle rules to the top automagically. Which is wrong of course.

indnti · Fri Dec 03, 2010 1:01 am

RC3 and RC4 doesn't work for us. The router RB433UAH has an UMTS Connection on USB port. It's a Huwai/Vodafone K4505. The router reboots if watchdog is enabled or stops working on both the UMTS and lan interface. There is no informative entries in the log about this failures. I will send a supot file to the support.

NetworkPro · Fri Dec 03, 2010 1:26 am

Please try the newly released on the download page RC5

and please tell us with which version it is totally working for you with this configuraion.

Thank you.

Who is online