v6.35rc [release candidate] is released, new wireless package!

Mon Mar 21, 2016 1:09 pm

heydude, what country setting you have specified in the CAPsMAN configuration as it selected 5740mhz as a center channel?

Mon Mar 21, 2016 1:13 pm

Hello
can any one have any clue what about this error
Untitled.png

It looks like the connection before the CAPsMAN and CAP was lost and CAP initiated a new connection to the CAPsMAN.

heydude · Mon Mar 21, 2016 2:11 pm

heydude, what country setting you have specified in the CAPsMAN configuration as it selected 5740mhz as a center channel?

Thanks for the tip. The country setting is really the problem. In the configuration I set it to Switzerland. So, strangely it selects 5740MHz as center channel, which is not allowed. If I set country to Germany it selects something like 5180, then it works fine. So, there might be a frequency table problem in the country settings.
Hope this will be fixed soon...

raffav · Mon Mar 21, 2016 4:12 pm

) winbox - added support for route action in mangle rules;

what is the usage of this new action ?
like a round-map on Cisco ?

juanvi · Mon Mar 21, 2016 7:40 pm

Cant' find:
Version 6.35rc34 has been released.

Changes since previous version:
*) capsman - added 802.11g/n band

[juanvi@xxx] /caps-man> configuration set channel.band=
2ghz-b  2ghz-b/g  2ghz-b/g/n  2ghz-onlyg  2ghz-onlyn  5ghz-a  5ghz-a/n  5ghz-a/n/ac  5ghz-onlyac  5ghz-onlyn

RafGan · Tue Mar 22, 2016 12:20 am

Next problem with wireless-rep and 6.35rc: point to point - one bridge with eth & wlan on both sides. Two VLANs on bridge, one of them is a multicast VLAN (IPTV, IGMP on switch connected to AP), second VLAN is an unicast VLAN. When STB is off, unicast works really great - about 160Mbs (AC mode, tcp speedtest on PC), but when STB is turning on, all trafiic goes down to minimal rate (max 6Mbs). Almost no access to AP, station RX & TX rates looks good (866Mbs) but on AP, TX is 6Mbs. Telnet waits "for a caffe", winbox too. Revert back to 6.34.2 and CM2 - all works OK on this same configuration (from a long, long time on A/N and AC devices).
I was trying: /system routerboard upgrade, multicast helper, multicast buffering, bridge filters, wireless channels and wireless channel width, wireless NV2, nstreme, 802.11 - nothing better. On eoip tunnel is ok (6.35RC) -but I don't like it with IPTV.

Any ideas?

Regards,
RafG

Siona · Tue Mar 22, 2016 7:44 am

Version 6.35rc34 has been released.

Changes since previous version:
*) capsman - added 802.11g/n band;
*) chr - added support for VLAN on Hyper-V;
*) hotspot - fix possible deadlock;
*) hotspot - improved html page resistance against attacks;
*) l2tp & pppoe - fixed user traffic accounting when fastpath was used;
*) pppoe - fixed crash when removing <l2tp> pppoe service;
*) winbox - added init-delay option to routerboard settings;
*) winbox - added sfp-mac for GPON interfaces;
*) winbox - added support for route action in mangle rules;

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

Problem with disconnecting wifi under capsmana with Intel cards introduced in rc33 is still persist in rc34. It occurs less frequently. I noticed it only once whole yesterday evening.

iakor · Tue Mar 22, 2016 10:03 am

Good day!

With wireless-rep package there is a problem: http://forum.mikrotik.com/viewtopic.php?t=81750#p528087

I have trouble with connection to router - time after time connection is interrupted (i can not ping, winbox disconnects after less then 10 min), but wifi is not (i did not see any messages with "wireless" in log).
I tried to understand root cause:
I did reconfigure my router - WiFi interface configured only like AP (internet is on ethernet interface) - i still gots disconnects from WiFi.
I do not change configuration of the router, but disabled wireless-rep package and enabled wireless-fp package - and WiFi becomes stable (i did not lost pings, winbox connected a long time.)

I updated to the last release (6.35rc34 (testing)). But the result is the same - From time to time router disconnects.

Tue Mar 22, 2016 10:53 am

juanvi - Do you use wireless-rep package?

juanvi · Tue Mar 22, 2016 10:58 am

juanvi - Do you use wireless-rep package?

Using cm2

darkprocess · Tue Mar 22, 2016 11:01 am

Same issue here with the rep package

Tue Mar 22, 2016 11:28 am

You must have at least 635rc34 and wireless-rep package on CAP device and also on CAPsMAN:

*) capsman - added 802.11g/n band;
*) wireless-rep - added 802.11g/n only band;

Cha0s · Tue Mar 22, 2016 12:27 pm

You must have at least 635rc34 and wireless-rep package on CAP device and also on CAPsMAN:

*) capsman - added 802.11g/n band;
*) wireless-rep - added 802.11g/n only band;

Any news about mAP Lite clock drift?

http://forum.mikrotik.com/viewtopic.php ... 31#p527731
http://forum.mikrotik.com/viewtopic.php ... 80#p527880

Tue Mar 22, 2016 3:16 pm

Version 6.35rc35 has been released.

Changes since previous version:
*) chr - fixed kernel crash when virtual ethernet was not connected to anything in Hyper-V;
*) chr - implemented kernel crash saving to autosupout.rif (will utilize additional 24Mb of RAM);
*) romon - fix romon discovery after of romon ID change;
*) userman - fixed www crash;
*) wireless - fix crash on nstreme-dual interface stats update;

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

kometchtech · Tue Mar 22, 2016 4:26 pm

Flapping to and to apply RB3011 to the ROS35rc35 interface.
And trying to get the supout.rif file at the same time, it is LCD display buggy restarted without permission.

[Ticket#2016032266000631]

juanvi · Tue Mar 22, 2016 6:07 pm

Version 6.35rc35 has been released.
*) userman - fixed www crash;

What a small changelog with big (for me) things inside! I thought would never come! Can't wait for testing!
_______________________________________________________

 by strods » 22 Mar 2016, 10:28

You must have at least 635rc34 and wireless-rep package on CAP device and also on CAPsMAN:

*) capsman - added 802.11g/n band;
*) wireless-rep - added 802.11g/n only band;

Running 6.35rc34 with cm2 package I've found the gn mode under capsman provisioning but is missing under config:

[juanvi@xxx] > caps-man provisioning set hw-supported-modes=
a  a-turbo  ac  an  b  g  g-turbo  gn

[juanvi@xxx] /caps-man> configuration set channel.band=
2ghz-b  2ghz-b/g  2ghz-b/g/n  2ghz-onlyg  2ghz-onlyn  5ghz-a  5ghz-a/n  5ghz-a/n/ac  5ghz-onlyac  5ghz-onlyn

Can explain it better please?

Thanks

Siona · Tue Mar 22, 2016 10:05 pm

Version 6.35rc35 has been released.

Changes since previous version:
*) chr - fixed kernel crash when virtual ethernet was not connected to anything in Hyper-V;
*) chr - implemented kernel crash saving to autosupout.rif (will utilize additional 24Mb of RAM);
*) romon - fix romon discovery after of romon ID change;
*) userman - fixed www crash;
*) wireless - fix crash on nstreme-dual interface stats update;

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

Still the same - disconnecting laptop with intel card.

Wed Mar 23, 2016 11:49 am

Version 6.35rc37 has been released.

Changes since previous version:
*) chr - fixed Hyper-V booting from SCSI;
*) chr - fixed Hyper-V on windows 8/10 reboot loop;
*) chr - implemented automatic storage increase on disk image size increase;
*) chr - no more installation on first boot;
*) lte - supported modems now use unsolicit events for network monitoring;
*) rb3011 - fixed high cpu load breaks ethernet stats;
*) rb3011 - fixed link down messages;
*) winbox - hotspot default-trial user shows profile as "unknown" in Winbox;

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

Siona · Wed Mar 23, 2016 12:03 pm

What about disconnecting issue?

kometchtech · Wed Mar 23, 2016 12:10 pm

Just my environment has confirmed the phenomenon might end up flapping from the ether6 to the ether10 interface.

Routerboard:RB3011
ROS6.35rc37

[Ticket#2016032266000631]

My best regards.

hedele · Wed Mar 23, 2016 1:53 pm

Version 6.35rc37 has been released.
*) lte - supported modems now use unsolicit events for network monitoring;

Unfortunately, this still breaks compatibility with Huawei ME909s (Ticket#2016032166000454)

jdsousa · Wed Mar 23, 2016 3:54 pm

When I install Version 6.35rc37 x86 and when HD boot gives kernel panic and can not start the system again.

Thanks.

Thu Mar 24, 2016 9:23 am

Version 6.35rc40 has been released.

Changes since previous version:

*) bonding - fixed crash when creating vlans on bonding interface;
*) bonding - fixed mac-address disappearance after reboot in specific setups;
*) chr - fixed reboots with license and queues;
*) chr - implemented automatic storage increase on disk image size increase;
*) fastpath - improved vlan fastpath;
*) map lite - added hardware WPS button support;
*) ppp - fixed ppp interface reconnect when uPnP was used;
*) quickset - fixed situations when hidden password was passed as ******* from winbox and webfig;
*) quickset - fixed wan interface selection on CCR1009-8G-1S-1S+;
*) quickset - use 5Ghz interface instead of 2GHz interface on SXT Lite5 ac;
*) routing - fixed routing-marks were not erased from memory when they are not being used;
*) winbox - added init-delay option to routerboard settings;

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

Thu Mar 24, 2016 9:24 am

Version will require at least Winbox 3.4:
http://forum.mikrotik.com/viewtopic.php?f=21&t=106142

Thu Mar 24, 2016 12:27 pm

Version 6.35rc41 has been released.

Changes since previous version:
*) bonding - fixed mac-address disappearance after reboot in specific setups;
*) chr - fixed reboots with license and queues;
*) quickset - fixed invalid date adjusted the signal threshold for the signal chart and refresh rate;

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

nkourtzis · Thu Mar 24, 2016 1:39 pm

Version 6.35rc40 has been released.

Changes since previous version:

[...]
*) winbox - added init-delay option to routerboard settings;

After upgrading, the option has dissapeared from routerboard settings.

pietroscherer · Thu Mar 24, 2016 1:56 pm

Version 6.35rc35 has been released.

Changes since previous version:
*) chr - fixed kernel crash when virtual ethernet was not connected to anything in Hyper-V;
*) chr - implemented kernel crash saving to autosupout.rif (will utilize additional 24Mb of RAM);
*) romon - fix romon discovery after of romon ID change;
*) userman - fixed www crash;
*) wireless - fix crash on nstreme-dual interface stats update;

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

Thanks especially for RoMON fix

Thu Mar 24, 2016 2:35 pm

nkourtzis - At first we implemented checkbox. Afterwards we improved it and now it shows up only on devices which has this feature.

kometchtech · Thu Mar 24, 2016 2:41 pm

Version 6.35rc41 has been released.

Changes since previous version:
*) bonding - fixed mac-address disappearance after reboot in specific setups;
*) chr - fixed reboots with license and queues;
*) quickset - fixed invalid date adjusted the signal threshold for the signal chart and refresh rate;

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

It does not resolve the behavior to flapping at the RB3011 interface.

[Ticket #2016032466000172]

Siona · Thu Mar 24, 2016 2:50 pm

Still problem with rep package with disappearing wifi access (wifi interface shows as connected but not work).

darkprocess · Thu Mar 24, 2016 2:58 pm

Same here. Connected but no traffic. Has to disconnect and reconnect

Thu Mar 24, 2016 3:10 pm

Version 6.35rc42 has been released.

Changes since previous version:
*) chr - fixed bridge firewall;
*) chr - make shutdown request from hyper-v work (might fix other hypervisor as well);
*) dude - fixed dude login logging, no more shows as winbox login;
*) timezone - fixed reboot by watchdog when selecting timezones from the end of list

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

Siona · Thu Mar 24, 2016 3:15 pm

Where can I find previous version of rc files? Need 6.35rc19.

Zorro · Thu Mar 24, 2016 10:37 pm

Where can I find previous version of rc files? Need 6.35rc19.

http://download2.mikrotik.com/routeros/ ... e-6.19.zip ?

Siona · Fri Mar 25, 2016 12:37 am

Thanks!

bajodel · Fri Mar 25, 2016 1:11 pm

Version 6.35rc41 has been released.
..[CUT]..
If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.
It does not resolve the behavior to flapping at the RB3011 interface.

[Ticket #2016032466000172]

Version 6.35rc42 ..port flapping on 3011 persist (ports 6-10), device unusable

mszulc · Fri Mar 25, 2016 8:31 pm

I had the same 'non working' wifi problem as described by others with rep package.

End user device works good for some time and suddenly looses connectivity while showing wifi as connected. Simple disconnect/connect solves the problem for some time (5-10 minutes). If left with no intervention for some time the connectivity comes back in a few minutes - and this cycle happens again.
Revert to cm2 solves permanently.

Tested on 2011 and hap ac for 2 and 5 ghz with wpa2 psk, local config, no capsman.

I'm not sure but I feel like this mostly happens (or is more frequent) on iOS devices, but this could be not true - more testing required.

benoga · Fri Mar 25, 2016 9:27 pm

i can confirm the wifi disconnect some times with all our 4 android devices. router is ccr1009 with capsman to hap ac wifi. look like not only iOS problem.
installed version 6.35rc42 rep package.

Beone · Sat Mar 26, 2016 1:24 pm

V6.35rc42 with cm2 package and capsman also results in regularly wifi latency spikes to 1 sec and 2 seconds.

Reverting back the CAPSMAN to v6.34.3 while leaving the caps on v6.35rc42 resolves this latency spike issue. We use centralised forwarding on CCR

Cha0s · Sat Mar 26, 2016 2:01 pm

Version 6.35rc41 has been released.
..[CUT]..
If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.
It does not resolve the behavior to flapping at the RB3011 interface.

[Ticket #2016032466000172]

Version 6.35rc42 ..port flapping on 3011 persist (ports 6-10), device unusable

Also confirmed here.

Downgraded back to 6.35rc29 and the problem was resolved.

bajodel · Sat Mar 26, 2016 2:27 pm

Version 6.35rc42 ..port flapping on 3011 persist (ports 6-10), device unusable
Also confirmed here.
Downgraded back to 6.35rc29 and the problem was resolved.

I'm quite new to 3011 so I went back to 6.34.3, flapping resolved but I've encountered some strange 'loop' alert on bridges witch have VLANs (temp "bad fixed" moving VLANs onto real interfaces instead of bridge ones)

Thanks Cha0s for hint ..since I'm actually on lab testing, I can move to 6.35rc trunk again stopping at rc29 (for now).

Also, I cannot succeed in partitioning my lab 3011, probably a known issue but better to note here..

IntrusDave · Sun Mar 27, 2016 5:40 am

Where can I find previous version of rc files? Need 6.35rc19.
http://download2.mikrotik.com/routeros/ ... e-6.19.zip ?

actually...

http://download2.mikrotik.com/routeros/6.35rc19/all_packages-mipsbe-6.35rc19.zip

change the "mipsbe" to the platform you need.

KBV · Mon Mar 28, 2016 9:13 am

CRL do not work correctly
Self-signed certificates do not contain CRL when working through winbox - CRL field not available.
When signing via CLI this is no problem.

But CRL is still not working correctly when you export / import the certificate- then CRL contains inappropriate information.

Zorro · Mon Mar 28, 2016 12:41 pm

Where can I find previous version of rc files? Need 6.35rc19.
http://download2.mikrotik.com/routeros/ ... e-6.19.zip ?
actually...
Code: Select all
http://download2.mikrotik.com/routeros/6.35rc19/all_packages-mipsbe-6.35rc19.zip
change the "mipsbe" to the platform you need.

yeah, right. i just picked MIPSBE because probability and propagation between gear.
year later that might be "ARM", for example.

nkourtzis · Tue Mar 29, 2016 4:04 pm

Requests for CAPsMAN bug fixes and new features, based on my experience with the current RC version:

1. {Nice to have} Add "CCQ", P Throughput" and "Signal to Noise", "Encryption" and "Group Encryption" and "WMM Enabled" fields to CAPsMAN Registration Table.

2. {Feature} Add "Frequency Mode", "WMM Support", "Multicast Buffering", "Keepalive frames", "Adaptive Noise Immunity" and "AMPDU Priorities" to CAPsMAN Config Settings.

3. {BUG} Make "Multicast Helper=full" in CAPsMAN slave interfaces work (now the interfaces stay in default setting).

4. {BUG} Make "Country=no_country_set" work on CAPsMAN 5GHz 802.11ac interfaces (it works on 2.4GHz, but on 5GHz ones it results in "no supported band" error message, regardless of the band and frequency settings).

5. {Feature} Add a scan/freq usage feature in CAPsMAN, with an aption to run in the background. Right now, if one wants to scan, they have to detach the physical interface from the Manager, do the scan and re-attach it. [In the future, use this info to auto-adjust CAP channels and power levels.]

6. {Annoying} Stop CAPsMAN from creating virtual interfaces on CAPs with name "wlanXXX" where XXX is a number which is incremented every time the interface is disabled and re-enabled.

7. {Nice to have} Let the user rename the virtual interfaces on the CAPs, like he/she can do with physical interfaces.

m94646602 · Tue Mar 29, 2016 6:05 pm

Requests for CAPsMAN bug fixes and new features, based on my experience with the current RC version:

1. {Nice to have} Add "CCQ", P Throughput" and "Signal to Noise", "Encryption" and "Group Encryption" and "WMM Enabled" fields to CAPsMAN Registration Table.

2. {Feature} Add "Frequency Mode", "WMM Support", "Multicast Buffering", "Keepalive frames", "Adaptive Noise Immunity" and "AMPDU Priorities" to CAPsMAN Config Settings.

3. {BUG} Make "Multicast Helper=full" in CAPsMAN slave interfaces work (now the interfaces stay in default setting).

4. {BUG} Make "Country=no_country_set" work on CAPsMAN 5GHz 802.11ac interfaces (it works on 2.4GHz, but on 5GHz ones it results in "no supported band" error message, regardless of the band and frequency settings).

5. {Feature} Add a scan/freq usage feature in CAPsMAN, with an aption to run in the background. Right now, if one wants to scan, they have to detach the physical interface from the Manager, do the scan and re-attach it. [In the future, use this info to auto-adjust CAP channels and power levels.]

6. {Annoying} Stop CAPsMAN from creating virtual interfaces on CAPs with name "wlanXXX" where XXX is a number which is incremented every time the interface is disabled and re-enabled.

7. {Nice to have} Let the user rename the virtual interfaces on the CAPs, like he/she can do with physical interfaces.

+1 +1 +1 Band Steering. Many times, I often need to complete the work by hand.

diorges · Tue Mar 29, 2016 9:50 pm

MikroTik dont recognize ospfv3 bits from edgerouter, mikrotik should ignore unrecognized bits and process the packet normally as decribed in the RFC,

Look at RFC https://tools.ietf.org/html/rfc5340#appendix-A.2

napismizpravu · Tue Mar 29, 2016 11:59 pm

6.35rc42 - RB433UAH (power 24V 2A)

uptime 5 days error system ...crash proxy, drive disk add duplicate USB1 ...FTP to USB1 void...ftp to disk6 contents USB1

reboot RB433UAH disk OK... disk6 disappeared, USB1 functional

jondavy · Wed Mar 30, 2016 7:40 am

Requests for CAPsMAN bug fixes and new features, based on my experience with the current RC version:

1. {Nice to have} Add "CCQ", P Throughput" and "Signal to Noise", "Encryption" and "Group Encryption" and "WMM Enabled" fields to CAPsMAN Registration Table.

2. {Feature} Add "Frequency Mode", "WMM Support", "Multicast Buffering", "Keepalive frames", "Adaptive Noise Immunity" and "AMPDU Priorities" to CAPsMAN Config Settings.

3. {BUG} Make "Multicast Helper=full" in CAPsMAN slave interfaces work (now the interfaces stay in default setting).

4. {BUG} Make "Country=no_country_set" work on CAPsMAN 5GHz 802.11ac interfaces (it works on 2.4GHz, but on 5GHz ones it results in "no supported band" error message, regardless of the band and frequency settings).

5. {Feature} Add a scan/freq usage feature in CAPsMAN, with an aption to run in the background. Right now, if one wants to scan, they have to detach the physical interface from the Manager, do the scan and re-attach it. [In the future, use this info to auto-adjust CAP channels and power levels.]

6. {Annoying} Stop CAPsMAN from creating virtual interfaces on CAPs with name "wlanXXX" where XXX is a number which is incremented every time the interface is disabled and re-enabled.

7. {Nice to have} Let the user rename the virtual interfaces on the CAPs, like he/she can do with physical interfaces.

+1
and too, show Radio-name(for mikrotik stations), Distance, Traffic graphic, signal-sthrength table,ping, mac-ping, torch, mac-telnet buttons

bug: in winbox gui, on wireless interface, not show button CAP if package wireless-cap is not installed/enabled

bug: in winbox gui on interfaces in the "+" button rename the latest interface type for "interfaces" to "Controlled AP, or CAP"

Wed Mar 30, 2016 11:18 am

Version 6.35rc43 has been released.

Changes since previous version:

*) fastpath - fixed show rx-bits-per-second on all VLAN interfaces;
*) nand - implemented once a week nand refresh to improve stored data integrity (will increase sector writes);

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

NetworkPro · Wed Mar 30, 2016 11:38 am

nand - implemented once a week nand refresh to improve stored data integrity (will increase sector writes)

Also for USB Flash in x86 ?

Wed Mar 30, 2016 11:41 am

uuuu...

*) nand - implemented once a week nand refresh to improve stored data integrity (will increase sector writes);

looks like v6.35 suddenly become my new favorite version.

slv · Wed Mar 30, 2016 12:12 pm

Hi

I have 3011 and strange issues with port based VLANs [Ticket#2016031766000506] - could someone confirm same problems?
I have separate topic for that problem http://forum.mikrotik.com/viewtopic.php?f=2&t=106049

Regards
Slawek

sam1275 · Wed Mar 30, 2016 1:52 pm

When will this version become release?

Wed Mar 30, 2016 6:10 pm

V6.35rc42 with cm2 package and capsman also results in regularly wifi latency spikes to 1 sec and 2 seconds.

Reverting back the CAPSMAN to v6.34.3 while leaving the caps on v6.35rc42 resolves this latency spike issue. We use centralised forwarding on CCR

What setup you have on the CAPsMAN for the CAP interface?

What is your wireless client and what OS you use?

Beone · Wed Mar 30, 2016 9:10 pm

when upgrading back to v6.35rc42 to try to reproduce, we didnt see the same behavior anymore.

CAPSMAN platform: ccr1009
caps: rb951g/rb951ui/hap ac lite
client: MacOS 10.11.4 - macbookair 7,2 - Broadcom BCM43xx 1.0 (7.21.95.175.1a6)

diorges · Wed Mar 30, 2016 10:16 pm

@strods

And what about the problem with OSPFv3 with EdgeRouter, mikrotik reject EdgeRouter OSPFv3 because of a flag AF which EdgeRouter sends, but in RFC says that unrecognized bits should be ignored.

ofca · Thu Mar 31, 2016 7:09 am

Was central user control/access point protection/locking from capsman already suggested?
It's kinda boring to login to 40+ access points to password protect them.

Awax · Thu Mar 31, 2016 1:07 pm

FastTrack doesn't work at RB750G.

Fri Apr 01, 2016 10:04 am

Version 6.35rc44 has been released.

Changes since previous version:
*) chr - try to renew expired license once a hour instead of 100h;
*) defconf - fixed default configuration for SXT LTE;
*) lte - improve situation when SXT modem never finds operator;
*) lte - supported modems now use unsolicited events for network monitoring;
*) rb3011 - make ether6-ether10 work if SFP module is present on bootup;
*) trafficgen - fixed console arguments;

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

PatrickKan · Fri Apr 01, 2016 12:11 pm

There is a serious bug introduced in rc44 for my CCR1036. After upgrade reboot, the L2MTU values for both sfp+ ports changed to 1580 from their original values of 9014. To make matter worse, neither Winbox nor console allows you to change the L2MTU back to their original values.

Fri Apr 01, 2016 3:05 pm

Version 6.35rc45 has been released.

Changes since previous version:

*) hotspot - make video tag work properly on hotspot login.html page
*) ipsec - fixed crash on policy update;
*) ppp - fixed ppp crash if lcp packets were lost and authentication got delayed;

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

RafGan · Fri Apr 01, 2016 11:08 pm

My two STX 5AC are death after upgrade to this version! No access, so no suppot.rif. Tomorrow netinstall.

Fri Apr 01, 2016 11:58 pm

Since rc42 our test CCR1036 has stopped on "starting kernel" when rebooting after the update.

fallenwrx · Sat Apr 02, 2016 1:51 am

same issue, upgraded from 6.35rc44 to 6.35rc45, fails to boot falls back to backup partition

mkorban · Sat Apr 02, 2016 6:29 am

same issue with 91xG 2HPnD
After the update the router is unavailable.
netinstall not help restore operability
reset is also not effective - sound can be heard, blinking LEDS forming, but a router is not available.

cREoz · Sat Apr 02, 2016 11:33 am

On update from 6.35rc43 to 6.35rc45 my RB951G-2HnD got boot-loop

How i can recover him?

mistry7 · Sat Apr 02, 2016 12:09 pm

On update from 6.35rc43 to 6.35rc45 my RB951G-2HnD got boot-loop
How i can recover him?

On my CRS too, need to netinstall

Shak7 · Sat Apr 02, 2016 12:58 pm

Same thing here with RB2011UiAS-2HnD-IN. Tried many times to Netinstall. The router always tries Ethernet boot, fails then says kernel failure before rebooting itself.

raffav · Sat Apr 02, 2016 5:39 pm

same thing on BASEBOX2 and RB450G

on RB450 using serial pot i get the kernel panic information that no system found
so i think that when start the process uninstalling the old one an installing the news on it crash so there is no system at all
via netinstall i was able to put rc45 up with no problem

RafGan · Sat Apr 02, 2016 8:03 pm

My two STX 5AC are death after upgrade to this version! No access, so no suppot.rif. Tomorrow netinstall.

Netinstall to 6.34.4 - works good again

easyspot · Sat Apr 02, 2016 8:23 pm

Last time using 6.35rc, ended with link dead for 1 day. Must do netinstall on both side. Now using 6.32.4 to keep out of trouble. No more rc version for me

Shak7 · Sat Apr 02, 2016 9:01 pm

Same thing here with RB2011UiAS-2HnD-IN. Tried many times to Netinstall. The router always tries Ethernet boot, fails then says kernel failure before rebooting itself.

Worked flawlessly with Netinstall 6.34.4
Thanks to Raf G !

Cha0s · Sun Apr 03, 2016 11:04 am

*) rb3011 - make ether6-ether10 work if SFP module is present on bootup;

Does this resolve the port flapping issue that appeared on some rc after rc29?

If yes, did anyone manage to upgrade to the latest rc without 'bricking' their board?
There are a few reports not being able to boot afterwards.

Florian · Sun Apr 03, 2016 9:02 pm

I'm staying on rc43, rc45 seems risky...

upower3 · Sun Apr 03, 2016 11:10 pm

Well, (at least) on weak devices like hAP lite I used to see 0 volts as voltage. Very sad to see that:

http://prntscr.com/anqej6

But as far as I know this is not even this RC problem. Any fix to come?

By the way when it comes to voltage if it is possible to see which power source is used on more powerful devices that have both PoE-in and power source? I'd be pretty happy to see "voltage" and "Power input" as two separate value (to have it in SNMP will be the best idea, great to monitor the power source health).

bajodel · Mon Apr 04, 2016 2:03 am

*) rb3011 - make ether6-ether10 work if SFP module is present on bootup;
Does this resolve the port flapping issue that appeared on some rc after rc29?

If yes, did anyone manage to upgrade to the latest rc without 'bricking' their board?
There are a few reports not being able to boot afterwards.

My lab rb3011 is working flawlessly with this new rc ..port flapping fixed

mbfound · Mon Apr 04, 2016 5:36 am

Anyone lose wireless on 6.35rc45?

It completely disappeared on a 951Ui-2HnD. Reboot and resetting didn't help. Downgrading to stable fixed it.

Upgrading to RC again now to see if it happens again.

IntrusDave · Mon Apr 04, 2016 5:53 am

Anyone lose wireless on 6.35rc45?

It completely disappeared on a 951Ui-2HnD. Reboot and resetting didn't help. Downgrading to stable fixed it.

Upgrading to RC again now to see if it happens again.

Not here. I have 3 RB's with wifi running with no issue.

w0lt · Mon Apr 04, 2016 5:55 am

Upgrading to ROS v6.35rc45 has caused so many problems (bricking units), packages missing that I have spent the past few days just cleaning up the mess.
I have downgraded all but one router (that I can't reach now) to v6.34.4. So far, so good.
I realize this is rc revisions but is someone at Mikrotik deliberately trying to sabotage the firmware?

Think I'll stick with non-rc for a while till I'm convinced Tik is releasing nonvolatile firmware.

PeterDoBrasil · Mon Apr 04, 2016 6:03 am

yes, rc 45 is very problematic

nkourtzis · Mon Apr 04, 2016 8:56 am

Upgrading to ROS v6.35rc45 has caused so many problems (bricking units), packages missing that I have spent the past few days just cleaning up the mess.
I have downgraded all but one router (that I can't reach now) to v6.34.4. So far, so good.
I realize this is rc revisions but is someone at Mikrotik deliberately trying to sabotage the firmware?
Think I'll stick with non-rc for a while till I'm convinced Tik is releasing nonvolatile firmware.

Keep in mind that is is called release CANDIDATE, that is, not released yet. If you want stability, stay with the stable version.

whitbread · Mon Apr 04, 2016 11:08 am

Sure but RC is not Test; so a bricked unit is not be expected usually...

If something is not working you rather expect to downgrade to your last working version and not to start from scratch.

PatrickKan · Mon Apr 04, 2016 11:18 am

I tried both 6.35r44 and r45 on my ccr1036 and crs226. Here were the combinations of problems:

6.35r44:
1. On CCRr1036 - it messed up the MTU and L2MTU values for both SFP+ ports and broke both SFP+ links. The worst of all, neither Winbox nor console was able to restore the original L2MTU values.
2. On CRS226 - it sent the unit into bootloop after reboot and netinstall had to be used to restore to older releases.

6.35r45:

1. On CCRr1036 - it messed up the MTU and L2MTU values for both SFP+ ports and broke bothl SFP+ links. The worst of all, both Winbox and console were unable to restore the original L2MTU values.

2. On CRS226 - it didn't cause bootloop.

I am back to 6.35r43 now.

Hope it helps.

juanvi · Mon Apr 04, 2016 11:19 am

I disagree: For me RC=TEST

Mon Apr 04, 2016 11:24 am

RC are essentially "Nighty Builds", don't rely on them in important networks.

whitbread · Mon Apr 04, 2016 2:27 pm

No problem for me apart from the naming. I am a SOHO user only and nobody else than me is relying on my infrastructure.

vortex · Mon Apr 04, 2016 2:39 pm

RC are essentially "Nighty Builds", don't rely on them in important networks.

Then they are not RC. Similar naming problem as "Current".

notToNew · Mon Apr 04, 2016 2:55 pm

Then they are not RC. Similar naming problem as "Current".

Right! Current RC-Branch should go to "development"...

vortex · Mon Apr 04, 2016 3:14 pm

And I am thinking "Current" is maybe 2 things in one: Feature + RC

Nightly -> Beta -> RC -> Feature -> Bugfix

kometchtech · Mon Apr 04, 2016 3:38 pm

And I am thinking "Current" is maybe 2 things in one: Feature + RC

Nightly -> Beta -> RC -> Feature -> Bugfix

+1

Mon Apr 04, 2016 3:43 pm

Each developer of software have it's own unique way to classify software releases.
Big thanks to MikroTIK to transfer to 3 stage release (RC, Current, bugfix) it is sufficient for all my needs.

I'm testing new RC mainly because of
*) nand - implemented once a week nand refresh to improve stored data integrity (will increase sector writes);

i have upgraded ~50 oldest devices in the network and it looks like 4 of them was too far gone, so netinstall was necessary, after it all devices worked perfectly, i was even able to keep config on all of them. Anyone else have noticed something similar? after v6.35rc43

nkourtzis · Mon Apr 04, 2016 4:25 pm

My experience was similar. Two out of around 40 devices were "bricked" by RC45, requiring a netinstall. One of them (a RB2011UiAS-RM) stuck on reboot and when power-cycled it came up but the system was corrupted (it was not even reporting a ROS version) but basic (hardware) interfaces and bridges were working. Not the ppp ones though. The other one, a hAP AC, was bootlooping no matter what. Retaining the current config during netinstall worked, at least in the hAP AC (for the other one I had kept a config file).

One other thing that I noticed (not related to the above problem) was that when all three chains are enabled on the 2.4GHz interface of the hAP AC, not all devices can associate. For example two phones, one with Android and the other with Windows Phone could not connect. When I turned off chain 2 (the third chain) devices which were not associating before, could connect successfully. Same with chain 1, although sync speeds seemed to be lower in this case. The 5GHz interface does not seem to have such a problem. I think (I am not sure though) that this is something that occured lately. Unfortuantely, it was not reported earlier so I cannot give any further info. But my observation above was made yesterday.

vortex · Mon Apr 04, 2016 5:06 pm

Given by the regressions and the number of iterations on the Current stream, I would say it is Beta+Feature, actually.

Which would be more damning evidence of the bad RC naming.

vortex · Mon Apr 04, 2016 5:29 pm

Basically:

- Almost all the fixes in the Current stream should be for new features or bugs still present in Bugfix.
- Most of the time RC should move to Current with 0 or 1 iterations.

Mon Apr 04, 2016 5:31 pm

Big thanks to MikroTIK to transfer to 3 stage release (RC, Current, bugfix) it is sufficient for all my needs.

It is much, much better than older approach.

vortex · Mon Apr 04, 2016 5:39 pm

Big thanks to MikroTIK to transfer to 3 stage release (RC, Current, bugfix) it is sufficient for all my needs.
It is much, much better than older approach.

But it seems it is still not good enough for some people who can't just stay on Bugfix.

vortex · Mon Apr 04, 2016 5:56 pm

Actually, there should be 2 real RC streams, one for Bugfix, and one for Current.

Mon Apr 04, 2016 6:00 pm

Vortex and co. You can't keep everyone happy, and you never will.
Please, find the old topic about the release system and post your feelings about it there. Hijacking technical topics only delays the problem solving.

vortex · Mon Apr 04, 2016 6:07 pm

Yes, people can be made happy.

The current release approach is still bad compared to the typical lifecycle of popular products and projects.

RyperX · Mon Apr 04, 2016 6:12 pm

I also had the problem that the router couldnt reboot after the update (2011UiAS-2HnD)
Unplugged power and after replug the router startet.

I know it was my fault that i didnt checked the forum before installation but i dont understand why mikrotik still deliver this update when there are much more problems then normal.
It would be enough to disable the update and wait for next release.

juanvi · Mon Apr 04, 2016 6:53 pm

Stop this debate and enjoy RC releases! Feel proud yourselves because you're helping Mikrotik in making best networking products ever seen! They let us be a part of the developement with the RC channel! As the others do?

RafGan · Tue Apr 05, 2016 12:43 am

Stop this debate and enjoy RC releases! Feel proud yourselves because you're helping Mikrotik in making best networking products ever seen! They let us be a part of the developement with the RC channel! As the others do?

That is true. If you install RC, you must think about risk and revert back to working versions in unusually issues. My SXTs are on top of the roofs - no such a big thing with it - 30 minutes per one, but I can tell people on this forum, that something wrong is with this version of ROS RC. Next RC will be installed on my home MT, then on SXTs. I don't know other marks that releases RC firmwares. Maybe MT should do RC for registered RC/beta testers?

vortex · Tue Apr 05, 2016 1:41 am

The problem is not that it is RC, but that it is NOT.

It is not even beta, because Current is beta-level, IMHO.

pbr3000 · Tue Apr 05, 2016 3:37 am

The problem is not that it is RC, but that it is NOT.

It is not even beta, because Current is beta-level, IMHO.

I need to echo macgaiver: go to the right topic (or create a new) and post your complains in there. No offenses, just to don't mess up this topic.

And to all who are experiencing bugs: send your reports to support@mikrotik.com because (repeating mikrotik staff) this forum is officially "from and to" mikrotik users only.

My latest bug report was:
From 6.34 changelog:
*) snmp - add oid from ucd mib for total cpu load OID 1.3.6.1.4.1.2021.11.52.0;
And this oid don't works anymore on the v6.35rc42 (CCR1009) and above. Untested in prior 6.35rc versions.

I had some lab gears bricked too on v6.35rc45, but I don't sent bug reports because it should be too obvious to mikrotik team.

vortex · Tue Apr 05, 2016 4:24 am

I already created a new topic, but people keep discussing the issue here instead.

paoloaga · Tue Apr 05, 2016 11:50 am

Nightly -> Beta -> RC -> Feature -> Bugfix

Too many branches encumber the devs. I think that actual situation is far better than before, we should just understand the naming convention used by MT or maybe they can just change it:

RC => Development
Current => Latest features
Bugfix => Long Term/Stable

I am very happy about the new management of software releases.

Tue Apr 05, 2016 1:27 pm

Version 6.35rc46 has been released,

Changes since previous version:

*) lcd - fixed branding packet logo drawing on startup;
*) lte - replaced signal-strength with rssi in info command;
*) nand - fixed reboot loop after upgrade to >v6.35rc43;
*) ppp - fixed some clients can not connect due to LCP restart;
*) tool fetch - fixed https cleanup on user stop while handshaking;
*) winbox - make build with latest lte changes;
*) wireless-rep - fixed latency issues with Intel 2.4GHz wireless clients

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

napismizpravu · Tue Apr 05, 2016 3:39 pm

RB433UAH (power 24V 2A) upgrade 6.35rc43 > 6.35rc46 = netinstall (karnel panic)

netinstall all_packages-mipsbe-6.35rc46 working

Siona · Tue Apr 05, 2016 3:57 pm

same here. after downgrade to 6.34.4 and installing 6.35 rc46 working fine util usb lte (3372) connecting.

Tue Apr 05, 2016 5:11 pm

RB411 .. no problems

raffav · Tue Apr 05, 2016 6:01 pm

Is any one having problem with vlan/trunk on the RC46? on CRH?

PeterDoBrasil · Wed Apr 06, 2016 5:07 am

I also had the problem that the router couldnt reboot after the update (2011UiAS-2HnD)
Unplugged power and after replug the router startet.

I know it was my fault that i didnt checked the forum before installation but i dont understand why mikrotik still deliver this update when there are much more problems then normal.
It would be enough to disable the update and wait for next release.

I threw my router in the trash, 2011UiAS-2HnD

IntrusDave · Wed Apr 06, 2016 5:21 am

I also had the problem that the router couldnt reboot after the update (2011UiAS-2HnD)
Unplugged power and after replug the router startet.

I know it was my fault that i didnt checked the forum before installation but i dont understand why mikrotik still deliver this update when there are much more problems then normal.
It would be enough to disable the update and wait for next release.
I threw my router in the trash, 2011UiAS-2HnD

LOL haven't heard about Netinstall?

2frogs · Wed Apr 06, 2016 6:23 am

I have 2x 951Ui-2HnD that are non-responsive after updating to v6.35rc45. One of them came back up partially, it had the the entire RoS Package disabled in it. I made a supout.rif and re-enabled the package and now it is completely non-responsive.

pbr3000 · Wed Apr 06, 2016 7:16 am

I have 2x 951Ui-2HnD that are non-responsive after updating to v6.35rc45. One of them came back up partially, it had the the entire RoS Package disabled in it. I made a supout.rif and re-enabled the package and now it is completely non-responsive.

The v6.35rc45 was especially bugged...

rzirzi · Wed Apr 06, 2016 7:48 am

RC46 i VERY problematic after update...
After automatic update under "check for updates" at my RB493G (mipsbe-separate packages) - some packages gone, only "system" has upgraded to rc46, i have had to power unplug/plug to make it working, then put missing rc46 packages at winbox. VERY problematic is version RC46!

Wed Apr 06, 2016 12:11 pm

Version 6.35rc47 has been released.

Changes since previous version:
*) tile - fixed performance regression on switch chip (introduced in 6.33rc18);
*) tile - fixed l2mtu change (introduced in 6.35rc);

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

Wed Apr 06, 2016 1:08 pm

Everyone who is still experiencing issues with upgrade/downgrade. In version 6.35rc46 we introduced fix:
*) nand - fixed reboot loop after upgrade to >v6.35rc43;

This fixed reboot loop, but you have to remember that within upgrade you can not have rc43-rc45 version involved. For example, upgrade from rc45 to rc46 could still crash because you try to upgrade from problematic version which does not have this fix included.

Florian · Wed Apr 06, 2016 5:06 pm

Everyone who is still experiencing issues with upgrade/downgrade. In version 6.35rc46 we introduced fix:
*) nand - fixed reboot loop after upgrade to >v6.35rc43;

This fixed reboot loop, but you have to remember that within upgrade you can not have rc43-rc45 version involved. For example, upgrade from rc45 to rc46 could still crash because you try to upgrade from problematic version which does not have this fix included.

So if we are in rc43-45, we have to downgrade first ?

mistry7 · Wed Apr 06, 2016 5:42 pm

Everyone who is still experiencing issues with upgrade/downgrade. In version 6.35rc46 we introduced fix:
*) nand - fixed reboot loop after upgrade to >v6.35rc43;

This fixed reboot loop, but you have to remember that within upgrade you can not have rc43-rc45 version involved. For example, upgrade from rc45 to rc46 could still crash because you try to upgrade from problematic version which does not have this fix included.
So if we are in rc43-45, we have to downgrade first ?

no, best way is to use netinstall

Wed Apr 06, 2016 6:09 pm

Correction, use regular update, but keep netinstall nearby.

I re-upgraded my 40 devices to the latest build and all of them were fine. (first time around there were few that needed Neinstall, but they were running 6.7-6.9). So might be NAND memory issue, that that fix is designed to solve (it periodically reads and re-writes sectors, to ensure data integrity, so we can assume there were devices that lost integrity already)

jondavy · Wed Apr 06, 2016 6:16 pm

please add CCQ column in caps-manager in registration-table,
I just need this vital information to be able to migrate all my sectors of my wisp to CAP
to be able to control the CCQ of customers quickly

Wed Apr 06, 2016 6:48 pm

Version 6.35rc48 has been released.

Changes since previous version:

*) address-list - fixed crash in low memory situations;
*) dhcp6-client - fixed wrong error message;
*) mipsbe - (excluding RB4xx and CRS series) fixed rare ethernet tx buffer corruption;
*) wireless-rep - fixed latency issues with Intel wireless clients;

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

ka4opi4a · Wed Apr 06, 2016 8:45 pm

Just broke my HAP AC after upgrade from previous rc version. I don't have much time, but I have no luck with net install. Also not discoverable over winbox. Please help...

Wed Apr 06, 2016 10:07 pm

When everyone who bricked a device by update would send it to mikrotik back for warranty repair, it would make mikrotik to think and test twice before releasing harmful versions to public.

ka4opi4a · Wed Apr 06, 2016 10:28 pm

Just manage to net install it somehow... And install 6.35rc48. It's working normall, but the wifi speed on the 5 ghz using intel 7260ac is just like on the current channel. With the previous rc the speed was really good ~ 400 mbps.

Siona · Wed Apr 06, 2016 11:52 pm

RB 433GL - not working when USB LTE modem connected - H3372 HiLink.

Florian · Thu Apr 07, 2016 12:30 am

Everyone who is still experiencing issues with upgrade/downgrade. In version 6.35rc46 we introduced fix:
*) nand - fixed reboot loop after upgrade to >v6.35rc43;

This fixed reboot loop, but you have to remember that within upgrade you can not have rc43-rc45 version involved. For example, upgrade from rc45 to rc46 could still crash because you try to upgrade from problematic version which does not have this fix included.
So if we are in rc43-45, we have to downgrade first ?

no, best way is to use netinstall

Well I just upgraded the normal way from rc43, no problem on my ccr1009.

I'm lucky I guess.

notToNew · Thu Apr 07, 2016 9:25 am

When everyone who bricked a device by update would send it to mikrotik back for warranty repair, it would make mikrotik to think and test twice before releasing harmful versions to public.

I hope that they pay no cent for sending in a device which is bricked because you installed a nightly build.
Just stay at the current version unless you are willing to learn how to use netinstall.

mahury · Thu Apr 07, 2016 9:40 am

Thanks to all, that mikrotik made from 6.2 to 6.32 & 6.34.4 . There is some great impruvements of stability was made.

I also has problem with 6.35 rc44 or rc45 on my 951G with boot loop.
It was fixed with netinstall & some PXE server.
Now I am on 6.34.4 and do not shure to go back to RC.

Can be PXE server be integrated to netintall for easy recover? Or write some more in manual? For idiots.

abis · Thu Apr 07, 2016 9:55 am

Thanks to all, that mikrotik made from 6.2 to 6.32 & 6.34.4 . There is some great impruvements of stability was made.

I also has problem with 6.35 rc44 or rc45 on my 951G with boot loop.
It was fixed with netinstall & some PXE server.
Now I am on 6.34.4 and do not shure to go back to RC.

Can be PXE server be integrated to netintall for easy recover? Or write some more in manual? For idiots.

Stay there until [stable] release

Awax · Thu Apr 07, 2016 12:27 pm

Dear engineers of Mikrotik, it is possible to hope that you implement the work of "FastTrack" on RB750G

Thu Apr 07, 2016 1:39 pm

I stay with bugfix only on productive devices considering the stable to be beta and rc to be alpha. Making tests in lab before any update and updating in vawes and only if really necessary. Using partitions on devices where it is possible to be able to boot the backup when whatever problem occurs after update. I don't remember any fatal accident due to update on productive devices I have ever made.

jondavy · Thu Apr 07, 2016 3:37 pm

if I change
/system logging action set 0 memory-lines=1000 name=memory target=memory
per
/system logging action set 0 memory-lines=10000 name=memory target=memory

the router works for a while, but after crashes, no more traffic goes by, so if I restart
the router hangs in all previous versions
tested RB2011UiAS
versions:
6.35rc42
6.34.4 (stable)
6.32.4 (bugfix)

edit:
after almost one days he again caught the traffic
when I open the terminal and try to ping a host appears (no buffer space available),
it seems that this was not

notToNew · Fri Apr 08, 2016 10:06 am

Did someone try to this new feature?
>> wireless background scan
I wanted to script a background scan for known Wifi-APs and if found, connect to it automatically.
The Microtik is in a car, and I know several Wifi along the road (while stopping the car!).
The Idea was: Scan for known ssid's (or MAC..) and if found one, set wlan2 to the known credentials.

Fri Apr 08, 2016 11:06 am

Dear engineers of Mikrotik, it is possible to hope that you implement the work of "FastTrack" on RB750G

It IS supported on all RB7xx

Fri Apr 08, 2016 12:13 pm

Dear engineers of Mikrotik, it is possible to hope that you implement the work of "FastTrack" on RB750G
It IS supported on all RB7xx

It works on our RB750GL but not on our RB750G

Awax · Fri Apr 08, 2016 1:47 pm

Dear engineers of Mikrotik, it is possible to hope that you implement the work of "FastTrack" on RB750G
It IS supported on all RB7xx
It works on our RB750GL but not on our RB750G

Yes, exactly so, 750 works 750G no

Fri Apr 08, 2016 3:10 pm

I found one

on old board shelf, just betweer RB230 and RB532.

, Yes you are right, this board is using same CPU as RB4xx series, so fastpath is not supported. you need ar72xx CPU at least ar71xx doesn't have the support.

Awax · Fri Apr 08, 2016 3:46 pm

I found one on old board shelf, just betweer RB230 and RB532. , Yes you are right, this board is using same CPU as RB4xx series, so fastpath is not supported. you need ar72xx CPU at least ar71xx doesn't have the support.

It turns out that it is possible not to hope that fasttrack will work at RB750G ?

ЭХ Mikrotik... and I had hoped and believed...

derr12 · Fri Apr 08, 2016 11:35 pm

Is there any word when/if ANI will get support in capsman?

yottabit · Sun Apr 10, 2016 11:18 pm

I'd really appreciate a working config that I can dig through to understand.

My other problem is finding a sequence of steps to get from the factory-default RBmAPL-n2D WISP AP configuration to one where the (only) Ethernet interface is on the LAN without losing Winbox connectability. (I can always use the magic button to restore the factory-default configuration, but then I'm right back where I started.) Once I'm controlling the router firmly through its Ethernet interface, I should be able to reconfigure the wlan interface without losing control.

Hi mccreigh. Sorry for the long wait, but I have finally completed the config and have it ready to share. Feel free to use and modify as-needed. Comments are written in the config that most should be able to understand with basic RouterOS and networking experience.

https://docs.google.com/document/d/1gdy ... YnDcLFv6aU

And here's the config for posterity's sake (but the Google Doc above allows Commenting and revisions, so check that if you would like to see if I've ever made any updates):

# RouterOS Hotel Setup
# Created 2016-04-10 by Jacob McDonald
# Revised n/a

# This config was built using a model RouterBOARD 962UiGS-5HacT2HnT (“hAP ac”).
# This router has 1x 2.4 GHz radio and 1x 5 GHz radio, but this configuration does not depend on two radios.
# This config uses the 2.4 GHz radio base interface in Station-Pseudobridge mode to connect to another Wi-Fi AP,
# and creates a Virtual AP virtual interface on top to serve 2.4 GHz stations. A 5 GHz AP is also configured, and
# the 5 GHz AP would provide better performance since the 2.4 GHz radio wouldn’t have to share air-time serving
# stations in AP mode and forwarding the traffic to the other AP in station mode.

# The split-mode radio configuration only works with RouterOS 6.35 (rc and higher), using the testing radio
# package “wireless-rep”. This package is not included in the main software package, but can be extracted from
# the extras package and installed a la carte.
# RotuerOS Software: http://www.mikrotik.com/download

# 1. Install the base package from System -> Packages, or by uploading the .npk to the root filesystem and reboot.
# 2. Extract the wireless-rep.npk package from the extras .zip archive, upload to the root filesystem, and reboot.
# 3. Third, upgrade the RouterBOARD firmware: System -> RouterBOARD -> Upgrade, and reboot.

# Change the wireless security profiles in “/interface wireless security-profiles” below:
#   default: set for your desired AP password (LAN)
#   wlan-WAN: set to the AP password for the Wi-Fi network you wish to use as WAN
#   none: this is a profile for using a Wi-Fi network as WAN with no authentication, typical in hotels

# Change between “wlan-WAN” and “none” security-profile as-needed by changing the setting in the
# “/interface wireless wlan1-WAN” config.

# Using the WebUI, Winbox, or CLI, perform Scan on the wlan-WAN interface, and select Connect to the AP you wish
# to use as WAN. This will adopt the frequency, bandwidth, and protocol settings automatically.

# This config will use the DHCP-supplied DNS servers from the WAN interface, which will be necessary to pass
# through the captive portal.

# apr/10/2016 20:31:47 by RouterOS 6.35rc48
# software id = XZFF-04CI
#
/interface bridge
add name=bridge1
/interface ethernet
set [ find default-name=ether1 ] name=ether1-WAN
/interface wireless
set [ find default-name=wlan2 ] band=5ghz-a/n/ac disabled=no mode=ap-bridge name=wlan2-5G-LAN ssid="Magrathea 5G" wireless-protocol=802.11
/ip neighbor discovery
set ether1-WAN discover=no
/interface wireless security-profiles
set [ find default=yes ] authentication-types=wpa2-psk eap-methods="" mode=dynamic-keys supplicant-identity=MikroTik wpa2-pre-shared-key=h2g2h2g2
add authentication-types=wpa2-psk eap-methods="" mode=dynamic-keys name=wlan-WAN supplicant-identity="" wpa-pre-shared-key=hdyfrc4la1 wpa2-pre-shared-key=hdyfrc4la1
add name=none
/interface wireless
set [ find default-name=wlan1 ] band=2ghz-b/g/n disabled=no distance=indoors frequency=2442 mode=station-pseudobridge name=wlan1-2G-WAN security-profile=wlan-WAN \
    ssid=skyconway_com-2231 wireless-protocol=802.11
add disabled=no keepalive-frames=disabled mac-address=E6:8D:8C:49:23:FA master-interface=wlan1-2G-WAN mode=ap-bridge multicast-buffering=disabled name=wlan3-2G-LAN ssid=Magrathea \
    wds-cost-range=0 wds-default-cost=0 wps-mode=disabled
/ip neighbor discovery
set wlan1-2G-WAN discover=no
/ip hotspot profile
set [ find default=yes ] html-directory=flash/hotspot
/ip pool
add name=dhcp ranges=192.168.88.3-192.168.88.254
/ip dhcp-server
add address-pool=dhcp authoritative=yes disabled=no interface=bridge1 name=dhcp1
/interface bridge port
add bridge=bridge1 interface=ether2
add bridge=bridge1 interface=ether3
add bridge=bridge1 interface=ether4
add bridge=bridge1 interface=ether5
add bridge=bridge1 interface=sfp1
add bridge=bridge1 interface=wlan2-5G-LAN
add bridge=bridge1 interface=wlan3-2G-LAN
/ip address
add address=192.168.88.1/24 interface=ether2 network=192.168.88.0
/ip dhcp-client
add default-route-distance=0 dhcp-options=hostname,clientid disabled=no interface=ether1-WAN
add default-route-distance=2 dhcp-options=hostname,clientid disabled=no interface=wlan1-2G-WAN
/ip dhcp-server network
add address=192.168.88.0/24 gateway=192.168.88.1 netmask=24
/ip dns
set allow-remote-requests=yes
/ip firewall filter
add chain=input protocol=icmp
add chain=input connection-state=established
add chain=input connection-state=related
add action=drop chain=input in-interface=ether1-WAN
add action=drop chain=input in-interface=wlan1-2G-WAN
/ip firewall nat
add action=masquerade chain=srcnat out-interface=ether1-WAN
add action=masquerade chain=srcnat out-interface=wlan1-2G-WAN
/ip upnp
set enabled=yes
/ip upnp interfaces
add interface=bridge1 type=internal
add interface=ether1-WAN type=external
add interface=wlan1-2G-WAN type=external
/system clock
set time-zone-name=UTC
/system identity
set name=rbtest
/system leds
set 1 interface=wlan2-5G-LAN
/system ntp client
# These are from us.pool.ntp.org
set enabled=yes primary-ntp=108.61.73.243 secondary-ntp=216.229.4.69
/tool mac-server
set [ find default=yes ] disabled=yes
add interface=ether2
add interface=ether3
add interface=ether4
add interface=ether5
add interface=sfp1
add interface=wlan2-5G-LAN
add interface=wlan3-2G-LAN
/tool mac-server mac-winbox
set [ find default=yes ] disabled=yes
add interface=ether2
add interface=ether3
add interface=ether4
add interface=ether5
add interface=sfp1
add interface=wlan2-5G-LAN
add interface=wlan3-2G-LAN

brwainer · Mon Apr 11, 2016 9:58 am

Requests for CAPsMAN bug fixes and new features, based on my experience with the current RC version:

6. {Annoying} Stop CAPsMAN from creating virtual interfaces on CAPs with name "wlanXXX" where XXX is a number which is incremented every time the interface is disabled and re-enabled.

Although I have not tried any of the RC versions, I have been tracking the release notes and do want to echo this request. I opened a ticket about it on 3/2/15 (#2016030266001122) and was eventually told "We have though about it. We will see if not changing name/id is possible solution and if everything will run smoothly then soon enough we will release changes." on 3/7/15 - I am hoping this makes it into 6.35rc and then current. Specifically my request was to re-use the same wlanID # (and SNMP interface index #) every time the CAP reconnects to the manager.

Zorro · Mon Apr 11, 2016 10:23 pm

had weird issues with UPnP since 6.29 or later ~ in few online games, like BF4, Planetside 2(less frequent) and UT4.
without UPnP its works flawless.
not hard to reproduce, but time of issue after round - are vary/different/unpredictible.
(other customers report other games, especially PunkBuster-aware/supported, but i cannot reproduce their issues in same games. but few ones(like enumerated above) - had Very persistent disconnections in result)

fix:
conntrack issue, reported before - my error. impact of static ARP whitelisting/binding to netflow on mobile assets. resolved.

jondavy · Tue Apr 12, 2016 5:35 am

when I have many address-list enabled, more than 300, and on mangle one mark-routing them to, the router restarts after a few hours
tested on RB2011UiAS

edit:
in fact it does not restart, the traffic to, if I try to ping appears
no buffer space avaliable
I that activated the whatchdog that the address 127.0.0.1 so restarts,
and address-list are all IP blocks's large size /15 /17 /22

scampbell · Tue Apr 12, 2016 6:23 am

Did someone try to this new feature?
>> wireless background scan
I wanted to script a background scan for known Wifi-APs and if found, connect to it automatically.
The Microtik is in a car, and I know several Wifi along the road (while stopping the car!).
The Idea was: Scan for known ssid's (or MAC..) and if found one, set wlan2 to the known credentials.

Why not use the existing wireless "connect list" feature ?

Simply set up a Connect List entry for each known ssid and associated security profile and leave the station SSID blank in the main screen. No scripting needed ?

Mikrotik will then try and connect to any AP that matches a Connect List entry.

notToNew · Tue Apr 12, 2016 10:56 am

Why not use the existing wireless "connect list" feature ?

simply didn't understand this function! Thanks a lot for pointing me there, i will try it!!!

Siona · Tue Apr 12, 2016 11:20 am

RC48 - It seems that RX speed limit doesn't work on VAP rep package. TX limit works fine.

Tue Apr 12, 2016 12:48 pm

Version 6.35rc49 has been released.

Changes since previous version:

*) dhcpv6 client - fix ia expiration and lifetime validation;
*) dhcpv6 server - acquire binding on renew if it does not exist;
*) export - exclude default values from export in "/interface l2tp-server server" menu;
*) export - fixed rare situations when not whole config was exported;
*) leds - fixed AP-CAP led blinking after successful association to CAPsMAN;
*) lte - fixed crash on early initialization;
*) lte - use timer for modem info;
*) ntp - fixed ntp client hangs in reached state;
*) rb3011 - fixed sfp compatibility with CCR when using direct attached cables;
*) tunnels - fixed performance slowdown on any other tunnel disable/enable;
*) winbox - added "pw-type" to "/interface vpls bgp-vpls" menu;
*) winbox - added "use-control-word" and "pw-mtu" to "/interface vpls cisco-bgp-vpls" menu;
*) winbox - added mtu=auto support to eoipv6 tunnel;
*) wireless-rep - use full identity where possible;

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

Neilson · Tue Apr 12, 2016 12:55 pm

Version 6.35rc49 has been released.
...
*) tunnels - fixed performance slowdown on any other tunnel disable/enable;
...

Hi uldis

can you please advise if this specific change is to address the reports that have come in over time with PPP concentrators experiencing packet loss when individual connections were disconnected?

If so this is a great improvement and I will look to people for testing on these larger concentrators (CCR's are particularly good for this).

If not, can you please advise what types of performance slowdown this does target?

Regards
Alexander

Tue Apr 12, 2016 12:57 pm

It is unrelated to ppp.
Problem appeared for example on GRE tunnels. Performance of one tunnel decreased after other gre tunnels were disabled/enabled.

Florian · Tue Apr 12, 2016 2:33 pm

Version 6.35rc49 has been released.

Changes since previous version:

*) dhcpv6 client - fix ia expiration and lifetime validation;
*) dhcpv6 server - acquire binding on renew if it does not exist;

I see a lot of works on dhcpv6 in recents RCs, which is a good thing.

Any timeline about adding options on the dhcpv6 client ? (like asked here : http://forum.mikrotik.com/viewtopic.php ... 81#p517695 ) ?

Thx.

MichaelTrip · Tue Apr 12, 2016 3:41 pm

Hi,

how do i enable Fast Path on my PPPOE-client? I think it will give my RB2011 more throughput.

VagnerBecker · Tue Apr 12, 2016 4:10 pm

HI,

The Dude i can not upload images, .npk files, returns "invalid file"

Best regards,

Vagner Felipe Becker

Tue Apr 12, 2016 5:07 pm

Rc49 should contain correction for the [Ticket#2016031666000222] but nothing similar is mentioned in the release notes. Is it so or not?

ka4opi4a · Tue Apr 12, 2016 10:12 pm

Any news about fixing AC mode and Intel 7260 ?

florentrivoire · Tue Apr 12, 2016 10:33 pm

I see a lot of works on dhcpv6 in recents RCs, which is a good thing.

Any timeline about adding options on the dhcpv6 client ? (like asked here : http://forum.mikrotik.com/viewtopic.php ... 81#p517695 ) ?

Thx.

I'm also interested in this new feature.
Thanks !

xuqianman · Wed Apr 13, 2016 9:13 am

in wireless-rep package,capsman could you add “bridge-mode” config support？

Wed Apr 13, 2016 11:01 am

When installed 6.35rc49 on RB941-2nd (nonTC), got this blue error in the log:

09:52:49 script,warning DefConf: Unable to find wireless interface(s)

There are no scripts at all. What does it mean? Why there should be running any default config script while the default config was long time ago fully wiped and everything was set manually?

Wed Apr 13, 2016 12:16 pm

Each time you upgrade, new defautl configuration file is generated, it doesn't matter if you wipe defconf or not.

Wed Apr 13, 2016 1:48 pm

Any news about fixing AC mode and Intel 7260 ?

This problem is already fixed in the latest rc wireless-rep package.

Are you still seeing some problems with it?

ka4opi4a · Wed Apr 13, 2016 1:51 pm

Can I use latest current release and latest rc wireless rep package ?

Wed Apr 13, 2016 2:22 pm

Can I use latest current release and latest rc wireless rep package ?

No, you need to switch the RouterOS to Release Candidate channel and upgrade to the latest RC which currently is rc49. And then install the wireless-rep package.

Wed Apr 13, 2016 3:07 pm

Each time you upgrade, new defautl configuration file is generated, it doesn't matter if you wipe defconf or not.

So it means there is an error in the script that expects some wlan adapter but it is not present... You should correct the default script then.

Wed Apr 13, 2016 3:30 pm

RB941 has one wireless interface, if during load it cannot find one there will be an error.

Wed Apr 13, 2016 3:54 pm

How it cannot find one when there is such adapter present?

docmarius · Wed Apr 13, 2016 3:58 pm

Do you have the latest ROS update and the latest firmware installed?

Did you do a reset to defaults?

Did you try netinstall

Aren't these the ultimate answers for everything? 42.

Wed Apr 13, 2016 4:06 pm

Yes. This error line appears when latest rc is installed over the 6.34.4. I saw it repetitively on 4 devices. It's either the wrong defconf script or the script runs too early when drivers are not properly loaded yet. It was just to inform that it could signalised some other maybe more important problem. Otherwise I don't see any significant impact in my case so far.

Wed Apr 13, 2016 4:13 pm

Works perfectly fine on out of the box router. Generator has limited time of execution. Unless there is no heavy load on CPU during boot up that could cause drivers not to load in time you will be fine.

xuqianman · Wed Apr 13, 2016 4:49 pm

Hi,
how to open then "bridge-mode" for capsman mode? thanks.

Wed Apr 13, 2016 4:58 pm

Hi,
how to open then "bridge-mode" for capsman mode? thanks.

currently it is not possible and it will not be added in the near future as it isn't just simple settings, there are lot of things needed for supporting that feature. And for the regular indoor APs you don't need this function.

human1982 · Wed Apr 13, 2016 10:32 pm

6.35rc49
NV2 qos works very good, ping in low, ap control capacity of the client well. Could u add a second Wieless Protocol nv2 (ex nv2-ptp, old named nv2-ptmp) for ptp only, with some special features to improove it? Ex lower the ping and more overhead control to stable the links? It could be the option in wireless-rep, we will test it.

regards
Mateusz

WirelessRudy · Thu Apr 14, 2016 2:00 am

6.35rc49
NV2 qos works very good, ping in low, ap control capacity of the client well. Could u add a second Wieless Protocol nv2 (ex nv2-ptp, old named nv2-ptmp) for ptp only, with some special features to improove it? Ex lower the ping and more overhead control to stable the links? It could be the option in wireless-rep, we will test it.

regards
Mateusz

"nv2-ptp", "nv2-ptmp"? I never heard of that. Only "NV2" then parameters are set for different type of link?

How did you measure the NV2 qos? Examples?

human1982 · Thu Apr 14, 2016 2:30 am

6.35rc49
NV2 qos works very good, ping in low, ap control capacity of the client well. Could u add a second Wieless Protocol nv2 (ex nv2-ptp, old named nv2-ptmp) for ptp only, with some special features to improove it? Ex lower the ping and more overhead control to stable the links? It could be the option in wireless-rep, we will test it.

regards
Mateusz
"nv2-ptp", "nv2-ptmp"? I never heard of that. Only "NV2" then parameters are set for different type of link?

How did you measure the NV2 qos? Examples?

Nv2 gives time space, and other things, it is in the code, for ptmp it is working now very well as i wrote (in auto period size one station overhead ap much before, now it isn`t). I think for ptp the code could be rewrite and aded as a second choise in menu. In lte no matter what rate and speed u have, ping is always the same, this is for me good qos. It is work for a coders, i am a customer, they must do the job to beat airmax, not me

For me i rather be pleased to have 90mb and ping 0-1-2 ms on 240/240 802.11N than 130-140mb and ping 2-7-20ms, this is example. When noise apears radio should do the job and lower the speed to do 0-1-2ms, now u understand?

regards
Mateusz

andersonlich · Thu Apr 14, 2016 10:41 am

v6.35rc49,

pppoe-client interface always up-down if it's doesn't get ipv6 dhcp-pd.
can it make not re-dial the pppoe if the ipv6 dhcp-pd not obtained ?

janisk · Thu Apr 14, 2016 11:04 am

regarding options for DHCPv6-client, DHCP-PD client (and also DHCP--PD server) as it currently stands - options will be available only with RouterOS 7.x release due to technical limitations for backporting the feature.

WirelessRudy · Thu Apr 14, 2016 11:55 am

6.35rc49
NV2 qos works very good, ping in low, ap control capacity of the client well. Could u add a second Wieless Protocol nv2 (ex nv2-ptp, old named nv2-ptmp) for ptp only, with some special features to improove it? Ex lower the ping and more overhead control to stable the links? It could be the option in wireless-rep, we will test it.

regards
Mateusz
"nv2-ptp", "nv2-ptmp"? I never heard of that. Only "NV2" then parameters are set for different type of link?

How did you measure the NV2 qos? Examples?
Nv2 gives time space, and other things, it is in the code, for ptmp it is working now very well as i wrote (in auto period size one station overhead ap much before, now it isn`t). I think for ptp the code could be rewrite and aded as a second choise in menu. In lte no matter what rate and speed u have, ping is always the same, this is for me good qos. It is work for a coders, i am a customer, they must do the job to beat airmax, not me For me i rather be pleased to have 90mb and ping 0-1-2 ms on 240/240 802.11N than 130-140mb and ping 2-7-20ms, this is example. When noise apears radio should do the job and lower the speed to do 0-1-2ms, now u understand?

regards
Mateusz

No, not a lot. Your english is a bit hard to understand.
Basically you mention that the 'auto' setting of NV2 time delay should be in two versions? One for PtMP and one for PtP?
I found 'auto' setting not always give best result anyway. We have AP with 30 clients and in changing 'auto' in 6ms we more than doubled the total throughput from AP (30 =>55Mb. Netbox5) while the ping time to client hardly changed.

I think 'auto' setting is always a compromise. If you really need to fine tune a link you have to do it manually.
But I can see your point in having 2 different default 'auto' scenarios. One for PtMP and one for PtP. That would make sense and give a better start for many of us...

To bring down a ping time by QoS is not very senseful. Your ping would be nice stable and fast, since QoS will take care of it, but your end goal is a good service level for your client's traffic. That is not ping but ordinary internet, voip, streaming TV etc. etc. If your ping is good due QoS that doesn't mean your network traffic is as good.

Florian · Thu Apr 14, 2016 1:45 pm

regarding options for DHCPv6-client, DHCP-PD client (and also DHCP--PD server) as it currently stands - options will be available only with RouterOS 7.x release due to technical limitations for backporting the feature.

Thx for the update

The famous RouterOS7.x.... I'll have to wait I guess

notToNew · Thu Apr 14, 2016 4:53 pm

When using the wireless_rep- package and adding the wan1-Device to a bridge called "bridge-wan" *and* using "connect-list",
bridge-wan does not get an ip adress from dhcp. (as station)
Removing it from the bridge it recives the ip immediately.

Connection it to station without using "connect-list" works, even as bridge.

Can this be a configuration error or is this a bug?

anuser · Thu Apr 14, 2016 9:29 pm

Is it possible to add more information about connected user to CAPSMAN view with wireless-rep package?
e.g. user name being used, auto-translation of vendor part of MAC (well it´s a gimmick)

juanvi · Thu Apr 14, 2016 10:29 pm

Where has gone the export compact by default with export command "only" in new terminal?????

jondavy · Thu Apr 14, 2016 11:44 pm

on CapsMan channel width=10mhz not work

jondavy · Fri Apr 15, 2016 1:07 am

mANTBox 15 not work in 10mhz with manual frequency

scampbell · Fri Apr 15, 2016 3:42 am

Is it possible to add more information about connected user to CAPSMAN view with wireless-rep package?
e.g. user name being used, auto-translation of vendor part of MAC (well it´s a gimmick)

If your were to create access lists based on the OUI info in this table http://standards-oui.ieee.org/oui.txt then each registration would have manufacturer listed next to it.

Fri Apr 15, 2016 11:06 am

on CapsMan channel width=10mhz not work

It is not, perhaps, supposed to work. My understanding is CAPsMAN currently mainly targets indoors setups with only the standard 802.11 features supported.

Fri Apr 15, 2016 5:05 pm

We have released 6.35 (current) discussion topic here http://forum.mikrotik.com/viewtopic.php?f=1&t=107307 Thanks to your feedback we have found the issue randomly causing boards to fail on upgrade during the rc testing,m this fix is included in 6.35 (current),

to successfully upgrade to 6.35 from 6.35rc29-rc49, please do a /system reboot, and then on bootup make an upgrade straight away.