v6.37rc [release candidate] is released, only one wireless package!

hedele · Mon Sep 12, 2016 5:43 pm

Wow... greatly reduced CPU load over previous versions on devices with large routing tables! Also a CCR1016 does no longer produce packet loss in general packet forwarding when a single CPU core is stuck at 100%

Tue Sep 13, 2016 1:33 pm

Version 6.37rc34 has been released,

Changes since 6.37rc32:

*) capsman - fixed kernel crash on cap while changing client-to-client forwarding;
*) dhcpv6 - improved interface status tracking;
*) dude - (changes discussed here: viewtopic.php?f=8&t=110424);
*) gps - always check NMEA checksum if available;
*) ipv6 - fixed RA and RS processing on new interfaces after many interfaces have lost link during prolonged operation;
*) mpls - fixed memory leak;
*) packages - fixed situation when it was impossible to disable ipv6 package (introduced in v6.37rc3x);
*) ppp,lte - pin is now converted to string argument;
*) supout - improved crash report generation for tile architecture;

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

Tue Sep 13, 2016 2:09 pm

*) mpls - fixed memory leak;

Hi Sergejs + Team,

Can you please provide more detail on this fix. Specifically what the triggers for the memory leak were, this way we can know exactly what problems it will solve.

Thanks!

Tue Sep 13, 2016 4:02 pm

Hi Sergejs + Team,
Can you please provide more detail on this fix. Specifically what the triggers for the memory leak were, this way we can know exactly what problems it will solve.
Thanks!

Lately changelog is as precise as they are willing/allowed to answer. for example - you wouldn't like them to reveal information that can potentially be used to trigger this on purpose. Especially while the fix is only in RC versions. Questions like this are dangerous.
Question here is simple, have you noticed or not some memory leaks in your mpls setups? If yes - upgrade.

Tue Sep 13, 2016 4:16 pm

nz_monkey,
We had ticket with MPLS configuration, that produced memory leak. This is fixed, however it is actual for very specific configurations. And I do not have to add more that previous poster replied.

amokkatmt · Tue Sep 13, 2016 5:38 pm

I can't disable wireless package on RB750GL since some of rc's.

17:24:09 system,info package wireless@ is scheduled for disable by ***
17:24:18 system,info disabled wireless@-6.37rc34 
17:24:21 system,info router rebooted

And after this reboot:

/system package print terse where disabled=no name=wireless
 0   name=wireless version=6.37rc34 build-time=sep/12/2016 13:06:07 scheduled="" bundle=routeros-mipsbe

Tue Sep 13, 2016 5:47 pm

Using package bundle by default is very bad approach of mikrotik for years. Better to install separate packages instead of bundle. Never mind it should be possible to disable bundled packages too.

Tonda · Tue Sep 13, 2016 6:11 pm

I have the same problem with disabling wireless package at RB750UP. To be honest - I do not understand, why it is even possible to install or enable/disable wireless package on device, which never had and will never have any kind of WiFi device inside? I think more examples can be found among Routerboard devices.

Tue Sep 13, 2016 10:13 pm

because you can use such device as capsman - so you need the wireless package.

Wed Sep 14, 2016 8:10 am

nz_monkey,
We had ticket with MPLS configuration, that produced memory leak. This is fixed, however it is actual for very specific configurations. And I do not have to add more that previous poster replied.

Thanks Sergejs, macgaiver perfectly explained with a context I had not thought about.

JHV · Wed Sep 14, 2016 9:53 pm

Version 6.37rc34 has been released,

Changes since 6.37rc32:

*) dhcpv6 - improved interface status tracking;

DHCPv6 still does not work like before v 6.33.6.

If a disconnect occurs, DHCPv6 stays for 10 minutes in state renewing and for another 10 minutes in state rebinding. It takes exactly 20 minutes until a new prefix could be obtained.
Please see also this thread.

juhos · Sat Sep 17, 2016 3:03 pm

Hi guys!

*) modem - added d-link dwm-222 support;

Can anyone help me with this? I have one dwm-222 modem but it not seems like work. The router only see the "Mobile connect"(cd drive for progs on pc).
Im trying on HAP lite.

wispwest · Sun Sep 18, 2016 10:28 pm

We had a few catostrophic wireless failures recently due to upgrading firmwares When it would come back, WLAN is disabled and lost all of its configuration as if ts a brand-new WLAN interface. Some of them didn't even show it, and needed the new wireless package enabled. Granted it wasn't clear enough what to do "prior" to the upgrade to the tech that was upgrading them.

It is understood now, but does still post some risks, would definitely be nice if the upgrade was full-automatic, which I understand is now happening the newest firmware? Aside from if you have multiple packages enabled, just make sure you disable one of them?

mistry7 · Mon Sep 19, 2016 10:06 am

How to solve this?
How to remove the old used Wireless Pack?

notToNew · Mon Sep 19, 2016 11:54 am

Is it possible to use the wireless-connect-list to connect to HIDDEN ssid's? Am I blind, or is there no possibility?

Mon Sep 19, 2016 1:28 pm

Version 6.37rc38 has been released,

Changes since 6.37rc36:

!) ethernet - added new loop-protect feature for ethernet,vlan,eoip,eoipv6 interfaces, http://wiki.mikrotik.com/wiki/Manual:Loop_Protect ;
*) dude - (changes discussed here: viewtopic.php?f=8&t=110424);
*) ipsec - fixed dynamic policy not deleted on disconnect for nat-t peers;

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

w0lt · Mon Sep 19, 2016 4:22 pm

Package list (Check For Updates) doesn't seem to grab the latest RC version.

barracuda · Mon Sep 19, 2016 11:59 pm

Same here!

qiet72 · Tue Sep 20, 2016 12:31 am

Hi,

Currently running 6.37rc38 on a hAP ac. I noticed that my laptop with an Intel 7250 wireless card cannot seem to receive mimo (dual chain) at the higher rates of 802.11ac but works perfectly when connected to my Asus RT-AC68U router. The issue seems to only happen on receive (to laptop), not transmit (from laptop). Transmit works as expected with dual chain mimo. I have used the registration page in winbox and the "iw wlan0 station dump" linux command to get the info.

Have tried 6.34.6, 6.36.3 and this latest rc - all exibit the same issue. The Asus RT-AC68U router seems to use the Broadcom BCM4360 chipset.

Qiet72

Tue Sep 20, 2016 9:13 am

6.37rc36 @ RB433 does not see rc38 for download.

qiet72 · Tue Sep 20, 2016 9:45 am

6.37rc36 @ RB433 does not see rc38 for download.

I stand corrected. Thank you. I will re-check the version and try again with latest.

Sent from my iPhone using Tapatalk

kristaps · Tue Sep 20, 2016 10:44 am

How to solve this?
How to remove the old used Wireless Pack?

Please use the Netinstall utility to reinstall the device:
http://wiki.mikrotik.com/wiki/Manual:Netinstall

andywright · Tue Sep 20, 2016 12:00 pm

6.37rc38 on hAP AC

Trying to use QuickSet from Winbox in Home AP Dual mode - unable to save config as 'Band' always stays red whatever settings for 2GHz and 5GHz are chosen. Works ok from Web config page though.

Tue Sep 20, 2016 2:59 pm

6.37rc38 on hAP AC

Trying to use QuickSet from Winbox in Home AP Dual mode - unable to save config as 'Band' always stays red whatever settings for 2GHz and 5GHz are chosen. Works ok from Web config page though.

what winbox loader version are you using?

andywright · Tue Sep 20, 2016 3:03 pm

Winbox 3.5

Tue Sep 20, 2016 3:34 pm

Version 6.37rc40 has been released,

Changes since 6.37rc38:

*) dhcpv6 - reworked DHCP-PD server interface and route management;
*) tunnel - fixed communication via tunnel to router itself if fastpath was active;
*) wireless - fixed interface disappearance on upgrade to 6.37 (introduced in v6.37rc);

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

Tue Sep 20, 2016 3:35 pm

andywright - This is an Winbox issue and will be fixed in next Winbox release.

andywright · Tue Sep 20, 2016 3:39 pm

strods - many thanks

John39 · Tue Sep 20, 2016 4:42 pm

After upgrading to 6.37 RC 40 on the router where the wireless interface disappeared , he returned , although in support of said preparing to replace the router as the problem in the router .

rajo · Tue Sep 20, 2016 5:16 pm

Is there any reason why NTP client still does not support DNS? It would be great if I could finally get rid of my script for this.

Tue Sep 20, 2016 5:24 pm

Is there any reason why NTP client still does not support DNS? It would be great if I could finally get rid of my script for this.

It is supported for a while already or you are looking some other setting:

/system ntp client set server-dns-names=NTP_SERVER_NAME

rajo · Tue Sep 20, 2016 5:51 pm

It is supported for a while already or you are looking some other setting:
Code: Select all
/system ntp client set server-dns-names=NTP_SERVER_NAME

I don't have server-dns-names as a configuration parameter. These are the options I have on MikroTik hardware:

[admin@MikroTik] > system ntp client set
enabled  mode  primary-ntp  secondary-ntp

Both primary-ntp and secondary-ntp require an IP address.

npero · Tue Sep 20, 2016 6:52 pm

Both primary-ntp and secondary-ntp require an IP address.

Do you maybe using ntp package ?

With ntp package

system ntp client set
enabled mode primary-ntp secondary-ntp

without

system ntp client set
enabled primary-ntp secondary-ntp server-dns-names

if you don't need ntp server don't have any reason to use ntp package.

rajo · Tue Sep 20, 2016 7:17 pm

if you don't need ntp server don't have any reason to use ntp package.

Thanks! That was the issue.

@MikroTik, please fix the inconsistency. It doesn't make sense to me that the server-dns-names option should not be available with the NTP package installed.

pe1chl · Tue Sep 20, 2016 7:37 pm

It doesn't make sense to me that the server-dns-names option should not be available with the NTP package installed.

It does make sense. The NTP package provides an NTP server and it works with fixed server addresses. Sure it would be
nice if there was the possibility to use DNS names there, but you should understand that in that case the DNS names would
be resolved only one time after router reboot. And there may even be dependency problems in that the router wants to set
the clock correctly before it has started the DNS resolver.

When running the router without NTP package, an SNTP implementation is used that can (when server-dns-names is used)
do an NTP lookup every time it requests the time, and the DNS name can return a different IP address every time. When that
is what you want (e.g. because you want to use the NTP pool), please use the SNTP implementation. Unfortunately, in that
case you cannot serve the time from the router.

I don't know which NTP server sourcecode MikroTik uses for the NTP server, and when it is the ntpd reference implementation,
if they will update to the latest version in RouterOS version 7. When they do, it would be possible to add a "pool-dns-name"
option to have both DNS resolution and server functionality.

rajo · Tue Sep 20, 2016 8:16 pm

It does make sense. The NTP package provides an NTP server and it works with fixed server addresses. Sure it would be
nice if there was the possibility to use DNS names there, but you should understand that in that case the DNS names would
be resolved only one time after router reboot. And there may even be dependency problems in that the router wants to set
the clock correctly before it has started the DNS resolver.

I really don't buy this argument. What you describe is really an implementation rather than technical (or even best-practices) issue.

rzirzi · Tue Sep 20, 2016 8:18 pm

Package list (Check For Updates) doesn't seem to grab the latest RC version.

Still the same problems... now the same with RC40...

pe1chl · Tue Sep 20, 2016 9:57 pm

I really don't buy this argument. What you describe is really an implementation rather than technical (or even best-practices) issue.

It is the same in all NTP server implementations. NTP servers lock onto reference servers, and would not work OK when the actual
server changes for subsequent polls. So NTP server implementations lookup the DNS name only when started. SNTP is different.

qiet72 · Tue Sep 20, 2016 10:55 pm

6.37rc36 @ RB433 does not see rc38 for download.

OK, I have now updated to the latest rc (6.37rc40) by downloading from mikrotik.com/download and updating routeros manually.
I did the same test: Do a download via the 5Ghz 802.11ac. My hardware is an Intel 7260 a/b/g/n/ac adapter. When I download via my Asus RT-AC68U router which uses a Broadcom BCM4360 chipset, I get full mimo transfers at up to 866 Mb/s (actual transfer speed is about 320Mb/s). Unfortunately, when the Intel card is connected to the 5 Ghz hAP ac MikroTik router, then I only get a bitrate of 433Mb/s max (1 chain) on receiving or around 210Mb/s and 866 Mb/s (2 chains) on transmitting. Again, this issue happens also on 6.36.3 and 6.34.6 versions. Interestingly, the bug only happens when the receive signal is negotiate above 195 Mb/s.

Qiet72

Sob · Wed Sep 21, 2016 1:14 am

NTP servers lock onto reference servers, and would not work OK when the actual
server changes for subsequent polls. So NTP server implementations lookup the DNS name only when started.

Let it work the same way as other ntp servers do, that's fine. No one asks for hostname being resolved again and again for each poll.

Current problem is that you have to put in numeric address instead of proper hostname, and if server moves somewhere else, RouterOS is stuck with old address. So you have to update config of all RouterOS clients, instead of updating only server's hostname. It's not right, since dns was invented to solve exactly this kind of problems.

pe1chl · Wed Sep 21, 2016 11:44 am

I understand what you mean, but note that MikroTik routers do not usually have a hardware real time clock, so they need
to get their system time from an external source as soon as possible during startup. It might be that the NTP server is
started before the DNS resolver, I don't know details about that.

The problem is worsened by the fact that MikroTik allow only 2 NTP servers to be configured. This should IMHO be
extended to at least 4, better an "arbitrary" number as seen in other places (where you can just expand the value list).
Maybe the issue could be solved by adding the capability for at least 2 DNS names in addition to the existing 2 fixed
addresses, and the NTP server could delay the resolving of DNS names until it has DNS available.

Having some method of updating certain settings of a large number of MikroTik routers is a topic I am going to investigate
anyway, as I get more and more routers and require this as well. Probably some solutions exist using either the API
or an automated login to the ssh/telnet service.

RyperX · Wed Sep 21, 2016 1:44 pm

I updated to latest rc40 and i lost my complete interface configuration. (As i know i came from rc38)
All interfaces was resettet and every setting that had an interface applied was set to unknown.

Any idea what happen? Device rb2011

qiet72 · Wed Sep 21, 2016 1:50 pm

6.37rc36 @ RB433 does not see rc38 for download.
OK, I have now updated to the latest rc (6.37rc40) by downloading from mikrotik.com/download and updating routeros manually.
I did the same test: Do a download via the 5Ghz 802.11ac. My hardware is an Intel 7260 a/b/g/n/ac adapter. When I download via my Asus RT-AC68U router which uses a Broadcom BCM4360 chipset, I get full mimo transfers at up to 866 Mb/s (actual transfer speed is about 320Mb/s). Unfortunately, when the Intel card is connected to the 5 Ghz hAP ac MikroTik router, then I only get a bitrate of 433Mb/s max (1 chain) on receiving or around 210Mb/s and 866 Mb/s (2 chains) on transmitting. Again, this issue happens also on 6.36.3 and 6.34.6 versions. Interestingly, the bug only happens when the receive signal is negotiate above 195 Mb/s.

Qiet72

I am considering adding screenshots to give a better idea of what I mean in case someone does not understand the problem. Unfortunately, I haven't figured out how to upload screenshots. If I try to insert an image, then it looks like it expects the image to exist already on the internet, but I would like upload the image from my computer - how do I do that on this forum?

Qiet72

qiet72 · Wed Sep 21, 2016 2:12 pm

Is it possible to use the wireless-connect-list to connect to HIDDEN ssid's? Am I blind, or is there no possibility?

I seem to remember that you have to use the mac address of the ap you want to connect to instead of the ssid when you want to connect to a hidden access point.

Qiet72

notToNew · Wed Sep 21, 2016 6:05 pm

I seem to remember that you have to use the mac address of the ap you want to connect to instead of the ssid when you want to connect to a hidden access point.

Qiet72

Thanks for your answer, I tried it without success. My Ap has several hidden wifi with the same mac, so how can the microtik connection-list determine which
wifi to choose, when it has no information about the ssid? Maybe that's the reason why it didn't work in my test?

pe1chl · Wed Sep 21, 2016 7:14 pm

My Ap has several hidden wifi with the same mac

Ohh boy... that is not good! Did the AP allow you to configure it that way? Did you have to force it somehow?

Sob · Wed Sep 21, 2016 7:53 pm

Maybe the issue could be solved by adding the capability for at least 2 DNS names in addition to the existing 2 fixed
addresses, and the NTP server could delay the resolving of DNS names until it has DNS available.

You may be overthinking it. DNS resolver in RouterOS is simple service, it must start up in no time. Making it a dependency for NTP client should not be a problem. And even if not, and NTP client was not able to resolve hostname, it would succeed a second later. No big deal to most users.

You can come up with some setup where hostnames wouldn't work. E.g. if your upstream DNS resolver would be only accessible using IPSec tunnel, which would have trouble starting with wrong system time. But it would be a special case and user/admin's responsibility to use the right configuration (i.e. in this case NTP client with numeric addresses only).

Mikhail73 · Wed Sep 21, 2016 8:43 pm

Does anyone have problems with recursive routing? I used this manual (Multiple host checking per Uplink), and everything works fine on first router. But exactly the same configuration (except gateways, of course) doesn't work on another two routers. When i add default route via virtual host 10.1.1.1, this route becomes active for several seconds, then becomes inactive. When i checked 10.1.1.1 (terminal-ip route check 10.1.1.1) - everything is ok. It seems to me, it's a bug. Tested on 6.36.2/6.36.3/6.47rc40.

qiet72 · Wed Sep 21, 2016 8:59 pm

I seem to remember that you have to use the mac address of the ap you want to connect to instead of the ssid when you want to connect to a hidden access point.

Qiet72
Thanks for your answer, I tried it without success. My Ap has several hidden wifi with the same mac, so how can the microtik connection-list determine which
wifi to choose, when it has no information about the ssid? Maybe that's the reason why it didn't work in my test?

You say: "My Ap has several hidden wifi with the same mac" - do you mean you have multiple Virtual AP's with the same mac address beside the one physical AP?

Qiet72

notToNew · Thu Sep 22, 2016 9:56 am

You say: "My Ap has several hidden wifi with the same mac" - do you mean you have multiple Virtual AP's with the same mac address beside the one physical AP?
Qiet72

No, I have ONE AP(not mikrotik) with several hidden SSIDs. each of this ssids have a name, like private-net and guestnet.
Every hidden ssid has the same mac-adresss.
So when i want to connect to the "private-net", how can i be shure that i'm connected to this net when i use ssid=MAC instead of ssid=private-net?

MartijnVdS · Thu Sep 22, 2016 10:08 am

You say: "My Ap has several hidden wifi with the same mac" - do you mean you have multiple Virtual AP's with the same mac address beside the one physical AP?
Qiet72
No, I have ONE AP(not mikrotik) with several hidden SSIDs. each of this ssids have a name, like private-net and guestnet.
Every hidden ssid has the same mac-adresss.
So when i want to connect to the "private-net", how can i be shure that i'm connected to this net when i use ssid=MAC instead of ssid=private-net?

Every virtual AP should, by default, get its own unique mac address. Otherwise, clients will get confused even when the network is visible.

pe1chl · Thu Sep 22, 2016 10:36 am

No, I have ONE AP(not mikrotik) with several hidden SSIDs. each of this ssids have a name, like private-net and guestnet.
Every hidden ssid has the same mac-adresss.

Please verify that again. I don't think it is true, and if it is true I don't think it can work.

Thu Sep 22, 2016 11:10 am

if you don't need ntp server don't have any reason to use ntp package.
Thanks! That was the issue.

@MikroTik, please fix the inconsistency. It doesn't make sense to me that the server-dns-names option should not be available with the NTP package installed.

This will be fixed/added in the RouterOS v7 only as current implementation doesn't allow that to add in v6 for the NTP package.

paoloaga · Thu Sep 22, 2016 1:13 pm

This will be fixed/added in the RouterOS v7 only as current implementation doesn't allow that to add in v6 for the NTP package.

There are so many things that will be available in v7 only, the most important (for me) are IPv6 routing enhancements (like the recursive lookup of BGP routes), I hope that we will be able to see it soon enough!

patrick7 · Thu Sep 22, 2016 1:49 pm

If it ever will be available...

Thu Sep 22, 2016 3:15 pm

Version 6.37rc42 has been released,

Changes since 6.37rc40:

!) dude - (changes discussed here: viewtopic.php?f=8&t=110424);
*) certificate - do not allow to remove certificate template while signing certificate;
*) dhcpv6 - fixed interface status update on client add (introduced in v6.37rc);
*) firewall - fixed time based rules on time/timezone changes (again);
*) ipsec - fixed crash with enabled fragmentation;
*) ipsec - fixed fragmentation use negotiation;
*) lte - added hauwei me909s variant;
*) lte - fixed setting correct lte band for sxt lte;
*) traffic-flow - fixed IPFIX packet timestamp;
*) traffic-flow - fixed IPFIX wrong flow sequence;

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

notToNew · Thu Sep 22, 2016 4:26 pm

2 year old sony-tv does not work with wireless-rep package. wireless-cm2 works as expected.

Thu Sep 22, 2016 9:45 pm

RB741TC @ RC36 or RC40
Cannot set it as CAP as "Certicate" field is in error state and there is no way to resolve this problem from GUI.
This RB741 have been removed from CAPSMAN some RC's back and I want to connect it again to CAPSMAN.

RB741TCRC40.PNG

FezzFest · Thu Sep 22, 2016 11:42 pm

Upgraded OmniTIK U-5HnD from 6.34.6 (bugfix) to 6.37rc40 and I'm stuck without wireless. It is in the package list two times, once with version 6.37rc40, once with version 6.27 (I have no idea where this comes from), both disabled. Uninstalling wireless package does not work, neither does enabling any of the packages.

Edit: downgraded to 6.36.3 and upgraded to 6.37rc42 again, issue persists. Device is in a remote location, so netinstall is not a possibility.

mistry7 · Fri Sep 23, 2016 6:43 am

@fezzfest

Known Unfixed issue......
Downgrade to 6.35.4
This bring you back with Wireless, After This you can Upgrade to 6.36 and the old Wireless-FP will be removed!

Mistry7

Mikhail73 · Fri Sep 23, 2016 6:47 pm

Does anyone have problems with recursive routing? I used this manual (Multiple host checking per Uplink), and everything works fine on first router. But exactly the same configuration (except gateways, of course) doesn't work on another two routers. When i add default route via virtual host 10.1.1.1, this route becomes active for several seconds, then becomes inactive. When i checked 10.1.1.1 (terminal-ip route check 10.1.1.1) - everything is ok. It seems to me, it's a bug. Tested on 6.36.2/6.36.3/6.36rc40/6.37

Excuse my persistence, but can anyone answer me, why double recursive route is inactive while it's gateway is active?..

samsung172 · Sat Sep 24, 2016 1:23 am

with "radar-detect" enabled will end in endless frequency search loop, even when there is realy no radar
That is not true. All countries in the EU, and the USA should have already been using this setting for a long time, and there are no problems like you describe.

I hope taht there will be country "other"
RouterOS already has a superchannel mode that does exactly this.

this is not true.

If you have to much power, noise and gain - you WILL have DFS to detect radar at all freq. DFS is NOT working as expected in ros. You should also implement TPC.

Chupaka · Sat Sep 24, 2016 3:35 am

Does anyone have problems with recursive routing? I used this manual (Multiple host checking per Uplink), and everything works fine on first router. But exactly the same configuration (except gateways, of course) doesn't work on another two routers. When i add default route via virtual host 10.1.1.1, this route becomes active for several seconds, then becomes inactive. When i checked 10.1.1.1 (terminal-ip route check 10.1.1.1) - everything is ok. It seems to me, it's a bug. Tested on 6.36.2/6.36.3/6.36rc40/6.37
Excuse my persistence, but can anyone answer me, why double recursive route is inactive while it's gateway is active?..

please make a new topic and post some details of actual config and state ("/ip route print detail", etc). as you can see, your question is not about 6.37rc exactly

vlatko · Sat Sep 24, 2016 12:47 pm

I'm not sure where mikrotik going, concerning wireless and radio side
I am aware of the limitations imposed by regulatory agencies in terms of DFS and other
now is the fact that with the current DFS mode, wireless becomes completely unusable in dense areas
DFS just constantly shifting frequency even if there is no radar in the vicinity and that's a fact
ITS TOTALY UNUSABLE
as far as I can see, there are two possible solutions
or they will be left some backdoor possibillity to go without DFS
or they will have to do something drastic to change
I think we need the following
spectrum scan should be carried out continuously in the background, independently of the work of operating clients radio
selection of free channels should be carried in background also, without disrupting client connections
probably would have to be a separate radio for it, like at ubiquiti
also, on mandatory, should be introduced synchronous switching customers to new frequency from ap radio side
after DFS establishing new free frequencies, ap should task a control signal for simultaneously switching to a new frequency to all clients from reg table
This could probably be introduced on proprietary protocols
without this i dont see how to use DFS

notToNew · Mon Sep 26, 2016 10:48 am

2 year old sony-tv does not work with wireless-rep package. wireless-cm2 works as expected.

thanks BartoszP for answering, i know that 6.37 only has one wireless-package.
Anyway, the problem still exists:

Connecting with 3.36.3 and wireless-cm2 works,
3.36.3 wireless-rep and 3.37.42 wireless does not work.

Another device which does not work: "Samsung UE22H5670"

pe1chl · Mon Sep 26, 2016 11:49 am

It could depend on some settings, e.g. aes/tkip for group ciphers.

notToNew · Mon Sep 26, 2016 12:07 pm

It could depend on some settings, e.g. aes/tkip for group ciphers.

Thanks for answering.
I posted a more in-dept message in the new 6.37 thread and think we should continoue there...?

My settings are the same on every MT-AP-device: WPA2-PSK and aes-ccm, no tkip.
I have different OS'ses on the client side (linux, windows, BSD, ...)

The MT support already contacted me some weeks ago, without any prograss until today. I offered them so donate
such a device for testing, but they bought one on theire own.

As wireless-cm2 is discontinued in the current branch, I'm somehow worried about the future...

My settings are the same on every device: WPA2-PSK and aes-ccm, no tkip.

The MT support already contacted me some weeks ago, without any prograss until today. I offered them so donate
such a device for testing, but they bought one on theire own.

As wireless-cm2 is discontinued in the current branch, I'm somehow worried about the future...

pe1chl · Mon Sep 26, 2016 12:09 pm

It could depend on some settings, e.g. aes/tkip for group ciphers.
Thanks for answering.
I posted a more in-dept message in the new 6.37 thread and think we should continoue there...?

My settings are the same on every MT-AP-device: WPA2-PSK and aes-ccm, no tkip.

Try to enable tkip for group cipher.

notToNew · Mon Sep 26, 2016 2:33 pm

Try to enable tkip for group cipher.

No difference. Here is the Debuglog from 3.26.3 with enables TKIP

02:02:31 wireless,debug wlan1: 00:12:F0:6E:DD:XX attempts to associate 
02:02:31 wireless,debug wlan1: reject 00:12:F0:6E:DD:XX, banned (last failure - extensive data loss) 
02:02:34 wireless,debug wlan1: 00:12:F0:6E:DD:XX attempts to associate 
02:02:34 wireless,debug wlan1: reject 00:12:F0:6E:DD:XX, banned (last failure - extensive data loss) 
02:02:37 wireless,debug wlan1: 00:12:F0:6E:DD:XX attempts to associate 
02:02:37 wireless,debug wlan1: reject 00:12:F0:6E:DD:XX, banned (last failure - extensive data loss) 
02:02:40 wireless,debug wlan1: 00:12:F0:6E:DD:XX attempts to associate 
02:02:40 wireless,debug wlan1: 00:12:F0:6E:DD:XX not in local ACL, by default accept 
02:02:40 wireless,info 00:12:F0:6E:DD:XX@wlan1: connected 
02:02:43 wireless,debug wlan1: 00:12:F0:6E:DD:XX attempts to associate 
02:02:43 wireless,info 00:12:F0:6E:DD:XX@wlan1: reassociating 
02:02:43 wireless,info 00:12:F0:6E:DD:XX@wlan1: disconnected, ok 
02:02:43 wireless,debug wlan1: 00:12:F0:6E:DD:XX not in local ACL, by default accept 
02:02:43 wireless,info 00:12:F0:6E:DD:XX@wlan1: connected 
02:02:46 wireless,debug wlan1: 00:12:F0:6E:DD:XX attempts to associate 
02:02:46 wireless,info 00:12:F0:6E:DD:XX@wlan1: reassociating

Log wir 6.36.3 wireless-cm2

02:07:15 wireless,debug wlan1: 00:12:F0:6E:DD:XX attempts to associate 
02:07:15 wireless,debug wlan1: 00:12:F0:6E:DD:XX not in local ACL, by default accept 
02:07:15 wireless,info 00:12:F0:6E:DD:XX@wlan1: connected

Edit: Added log for wireless-cm2

pe1chl · Mon Sep 26, 2016 4:05 pm

Ok it helped for me for another ancient device...

Mon Sep 26, 2016 4:15 pm

6.37 is out. Please start separate topics about specific issues or questions

Who is online