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

Announcements
181

strods and normis,
sorry I made you angry. You have my full respect and I am very gratefull to you for what you are doing.

But this situation is a bit different. You have seen a picture where was clearly visible that BartoszP pressed “download” or “download and install” button in system-packages after checking for update. The response was that there is not enough space for it. Instead of providing him a working solution you stated that update is made in memory. How it is heplful when on my 941s is normally 4-6MB of free ram? His devices run similarly probably.

I would not suggest to him any procedure that I had not tested before. I did not wanted to make such tests at all, but your approach forced me to do so, because I am having the same problems as BartoszP so I have developed a way ho to perform the update even there is not enough space for it… My way works, your statements are for nothing. Yes, finally everyone can make netinstall, but why, if there is a workable workaround?

If you think my suggestions just breaks things, you shoul also explain what things and how will be broken. I have not realised anything like this.

And what is the root cause? I can tell you.

Firstly, it is your decision to make new devices with just 32MB of RAM although I (and others) are telling you that it is too small amount of memory. And besides that, you decided to provide almost any flash memory. OK, I know, 16MB in this case, but not usable to store the packages to be installed, as the running ros is already installed there.

Secondly it is your decision to ship the devices with preinstalled bundled set of packages, many of them disabled, not necessary for “ordinary home users”, but just occupying space on flash. More over that, if automatcially updated, these useless packages have to be downloaded and stored to be updated too. You know I was asking you long time ago not to ship devices with one bundled package but with “individually” preinstalled packages so the user could be able to fully remove the ones he does not need. It would free the flash and also the next updates will be smaller so they probably could fit in ram/flash to be updated automatically. It is still not clear for me why are you doing this.

You surely remember why you had to remove the winbox dll file from smips ros and therefore needed to release winbox v.3. I am very curious how you will ensure update operation within ros7. I am expecting the ros7 will be again a bit bigger to store… Maybe it will force you to admit that I was right by doing the things I have suggested to you long time ago and this time again.

Cha0s,
thank you confirming my statements. Obviously you have the same experience.

182

Looks like you posted before Strods made the post before yours.

So in the end, if you want to use bundle, use bundle. If you want something special, don’t use bundle, but install all packages one by one.

183

Version 6.35rc12 has been released.

Changes since previous version:
*) dude - (changes discussed here: http://forum.mikrotik.com/t/the-dude-work-continues-v6-35rc-test-builds/94981/1);
*) pppoe-client - implemented fastpath support;
*) ssl - optimized certificate update;
*) ospf - fixed crash when getting neighbor router-id in NBMA area;
*) romon-ssh - fixed active addresses for romon user;
*) email - fix send cmd server addr override.

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.

184

jarda - Sorry. this time it was my mistake. Often also we forget that hAP lite does not have flash folder. I guess I can blame Friday :slight_smile:

185

Wait! What??
*) pppoe-client - implemented fastpath support;
MT you need to stop destroying my weekends, now i need to test this… :slight_smile:

I love versions before the big MUM events - all good stuff is coming out.

186

Hey Normis, Is this an Hotspot Bug ???
http://forum.mikrotik.com/t/hotspot-pirates-mikrotik-hotspot-v6-35rc11-isp-nightmare/95558/1 :frowning:

187

A. Restart helped … inmemory upgrade have made my RB741 @ rc11 … why not to put “inmemory upgrade in progress” instead of “too low space” ?
B. What about situation when my address lists, rules lists will be too big in total for downloading package to make inmemory upgrade ?
C. 16MB flash as a disk is … TOO SMALL … what about importing scripts, making backups before upgrade etc. ?
D. “My new preciousssss” … hAP AC has only 16MB too … it is strange for such powerfull device … how to make it main router ?
962.PNG

188

BartoszP - Previously it was my mistake. We have many devices which uses flash memory. They all can be divided in two groups - smips devices and other devices. hAP lite is smips device and performs upgrade within flash memory (this I messed up previously). Other devices which has flash memory but are not smips devices are upgraded by using RAM memory.

smips platform is called like that for a reason, It is most simple platform which we have and should be used for simple home configurations. In such cases memory should be used basically only for export files.

As it goes for hAP ac and other devices which are not smips devices but has flash memory - they still are simple home routers. There is plenty space for backup, some other things and, if you need something more, then there is a USB port on which you can attach any USB drive and use as a storage device.

If you have other questions, then please turn to support. This is still 6.35rc topic and problems related to this particular version should be discussed here :slight_smile:

189

Yeah, pppoe-client fastpath support!!! :smiley: :smiley:

Now I can reach 306Mbps download speed (http://www.speedtest.net), and CPU is 34%-40% (on 6.34.2 was 85%), tested on RB951G / Movistar / Spain.

Thanks MikroTik, great job!!

190

What does it mean - latest router? And why do you need it? Without any information I cannot suggest to you other version than 6.32.3. Even though the 6.32.4 is out already for some time I have not tested it enough yet and I have no need to change the production version so far.

191

It means one point for spammer and zero for jarda, better luck next time. :wink:

I don’t know if the signature was there before you replied or if it was added later, but it’s quite obvious with it. User’s first post, does not make much sense, but they made sure they added the signature with link to some commercial activity.

192

Yes, nice feature indeed. :slight_smile:

193

There is no signature displayed in tapatalk. I am not aware about it.

194

Hello Normis! Can You Help me Here?
http://forum.mikrotik.com/t/hotspot-2-0-wireless-802-11u-interface-wireless-interworking-profiles-a-very-interesting-theme/95426/1

195

Tested the repeater-mode on hap-ac lite: it works with win10-laptop, with android-phones,but not with winXP-Wifi.
This simply doesn’t get an IP.

11:20:31 wireless,info 00:0E:35:D6:11:EF@wlan1_ap2: connected
11:20:31 wireless,info 00:0E:35:D6:11:EF@wlan1_ap2: reassociating
11:20:31 wireless,info 00:0E:35:D6:11:EF@wlan1_ap2: disconnected, ok
11:20:31 wireless,info 00:0E:35:D6:11:EF@wlan1_ap2: connected
11:20:31 wireless,info 00:0E:35:D6:11:EF@wlan1_ap2: reassociating
11:20:31 wireless,info 00:0E:35:D6:11:EF@wlan1_ap2: disconnected, ok
11:20:31 wireless,info 00:0E:35:D6:11:EF@wlan1_ap2: connected
11:20:32 wireless,info 00:0E:35:D6:11:EF@wlan1_ap2: reassociating
11:20:32 wireless,info 00:0E:35:D6:11:EF@wlan1_ap2: disconnected, ok
11:20:32 wireless,info 00:0E:35:D6:11:EF@wlan1_ap2: connected
11:20:32 wireless,info 00:0E:35:D6:11:EF@wlan1_ap2: reassociating
11:20:32 wireless,info 00:0E:35:D6:11:EF@wlan1_ap2: disconnected, ok
11:20:32 wireless,info 00:0E:35:D6:11:EF@wlan1_ap2: connected
11:20:32 wireless,info 00:0E:35:D6:11:EF@wlan1_ap2: reassociating
11:20:32 wireless,info 00:0E:35:D6:11:EF@wlan1_ap2: disconnected, ok
11:20:32 wireless,info 00:0E:35:D6:11:EF@wlan1_ap2: connected
11:20:32 wireless,info 00:0E:35:D6:11:EF@wlan1_ap2: disconnected, received deauth: unspecified (1)

When configuring an non-virtual AP in Mikrotik, the XP-Laptop (with Intel-Hardware) can connect as expected.

Do i miss anything?

→ I love the new feature, it helps me a lot

196

notToNew

Please execute this command on your device:
“/system logging add topics=wireless,debug”

After that try to connect again. If logs do not show you error right away, then generate supout file and send it to support@mikrotik.com for checking.

Here you can see how to generate supout file:
http://wiki.mikrotik.com/wiki/Manual:Support_Output_File

197

About this nice feature “*) pppoe-client - implemented fastpath support;”

Is the RB3011 RouterOS specific version really supporting fastpath ?
Why this question:

  • It not appears listed as supported in the WIKI page on fatspath.
  • My testing after applying the firewall rules and having the counter growing…does not seem to provide any CPU saving on RB3011.

Please, Mikrotik, may you clarify this: today, an RB3011 dowloading one TCP stream at 300 Mbits over PPP and having NAT and a basic configuration of firewall rules needs 80% of one CPU to handle this trafic with spikes up to 90% at 1400 mhz frequency…

This device is starting to remember me the buggy RB850x2: lower performance than anticipated, strange problems (software bridge problems,…), features not working (partition not working,…), hardware revisions (I hope this not again, please)…

It would be “funny” to have to go back to an RB2011: starting to become tired to be patient with MIkrotik…RB3011 is not a 100$ device.

198

And when you plan to fix this “dirty” SNTP behaviour in RB3011 ?

605 Feb/23/2016 15:45:19 memory system, info sntp change time Feb/23/2016 15:45:16 => Feb/23/2016 15:45:19
606 Feb/23/2016 15:47:30 memory system, info sntp change time Feb/23/2016 15:47:27 => Feb/23/2016 15:47:30
607 Feb/23/2016 15:48:19 memory system, info sntp change time Feb/23/2016 15:48:18 => Feb/23/2016 15:48:19
608 Feb/23/2016 15:49:25 memory system, info sntp change time Feb/23/2016 15:49:23 => Feb/23/2016 15:49:25
609 Feb/23/2016 15:56:14 memory system, info sntp change time Feb/23/2016 15:56:05 => Feb/23/2016 15:56:14
610 Feb/23/2016 15:57:20 memory system, info sntp change time Feb/23/2016 15:57:18 => Feb/23/2016 15:57:20
611 Feb/23/2016 15:58:25 memory system, info sntp change time Feb/23/2016 15:58:24 => Feb/23/2016 15:58:25
612 Feb/23/2016 16:00:36 memory system, info sntp change time Feb/23/2016 16:00:33 => Feb/23/2016 16:00:36
613 Feb/23/2016 16:01:42 memory system, info sntp change time Feb/23/2016 16:01:40 => Feb/23/2016 16:01:42
614 Feb/23/2016 16:04:26 memory system, info sntp change time Feb/23/2016 16:04:22 => Feb/23/2016 16:04:26
615 Feb/23/2016 16:05:15 memory system, info sntp change time Feb/23/2016 16:05:14 => Feb/23/2016 16:05:15
616 Feb/23/2016 16:06:20 memory system, info sntp change time Feb/23/2016 16:06:19 => Feb/23/2016 16:06:20
617 Feb/23/2016 16:08:31 memory system, info sntp change time Feb/23/2016 16:08:28 => Feb/23/2016 16:08:31
618 Feb/23/2016 16:12:53 memory system, info sntp change time Feb/23/2016 16:12:47 => Feb/23/2016 16:12:53
619 Feb/23/2016 16:37:15 memory system, info sntp change time Feb/23/2016 16:36:41 => Feb/23/2016 16:37:15
620 Feb/23/2016 16:38:20 memory system, info sntp change time Feb/23/2016 16:38:19 => Feb/23/2016 16:38:20
621 Feb/23/2016 16:40:31 memory system, info sntp change time Feb/23/2016 16:40:28 => Feb/23/2016 16:40:31
622 Feb/23/2016 16:42:42 memory system, info sntp change time Feb/23/2016 16:42:39 => Feb/23/2016 16:42:42
623 Feb/23/2016 16:44:53 memory system, info sntp change time Feb/23/2016 16:44:50 => Feb/23/2016 16:44:53
624 Feb/23/2016 16:45:43 memory system, info sntp change time Feb/23/2016 16:45:41 => Feb/23/2016 16:45:43
625 Feb/23/2016 16:49:15 memory system, info sntp change time Feb/23/2016 16:49:11 => Feb/23/2016 16:49:15
626 Feb/23/2016 16:50:21 memory system, info sntp change time Feb/23/2016 16:50:19 => Feb/23/2016 16:50:21
627 Feb/23/2016 16:53:37 memory system, info sntp change time Feb/23/2016 16:53:33 => Feb/23/2016 16:53:37
628 Feb/23/2016 16:54:27 memory system, info sntp change time Feb/23/2016 16:54:25 => Feb/23/2016 16:54:27
629 Feb/23/2016 16:55:32 memory system, info sntp change time Feb/23/2016 16:55:31 => Feb/23/2016 16:55:32
630 Feb/23/2016 16:57:43 memory system, info sntp change time Feb/23/2016 16:57:40 => Feb/23/2016 16:57:43
631 Feb/23/2016 17:11:06 memory system, info sntp change time Feb/23/2016 17:10:47 => Feb/23/2016 17:11:06
632 Feb/23/2016 17:11:55 memory system, info sntp change time Feb/23/2016 17:11:54 => Feb/23/2016 17:11:55
633 Feb/23/2016 17:13:00 memory system, info sntp change time Feb/23/2016 17:12:59 => Feb/23/2016 17:13:00
634 Feb/23/2016 17:15:11 memory system, info sntp change time Feb/23/2016 17:15:08 => Feb/23/2016 17:15:11
635 Feb/23/2016 17:19:21 memory dhcp, info dhcpNoSecure assigned 192.168.60.247 to XXXXXX
636 Feb/23/2016 17:19:33 memory system, info sntp change time Feb/23/2016 17:19:27 => Feb/23/2016 17:19:33
637 Feb/23/2016 17:43:55 memory system, info sntp change time Feb/23/2016 17:43:21 => Feb/23/2016 17:43:55
638 Feb/23/2016 17:45:00 memory system, info sntp change time Feb/23/2016 17:44:59 => Feb/23/2016 17:45:00
639 Feb/23/2016 17:45:50 memory system, info sntp change time Feb/23/2016 17:45:48 => Feb/23/2016 17:45:50
640 Feb/23/2016 17:49:55 memory system, info sntp change time Feb/23/2016 17:49:50 => Feb/23/2016 17:49:55
641 Feb/23/2016 17:51:01 memory system, info sntp change time Feb/23/2016 17:50:59 => Feb/23/2016 17:51:01
642 Feb/23/2016 17:51:50 memory system, info sntp change time Feb/23/2016 17:51:49 => Feb/23/2016 17:51:50
643 Feb/23/2016 17:55:23 memory system, info sntp change time Feb/23/2016 17:55:18 => Feb/23/2016 17:55:23
644 Feb/23/2016 17:58:07 memory system, info sntp change time Feb/23/2016 17:58:03 => Feb/23/2016 17:58:07
645 Feb/23/2016 18:01:23 memory system, info sntp change time Feb/23/2016 18:01:19 => Feb/23/2016 18:01:23
646 Feb/23/2016 18:04:40 memory system, info sntp change time Feb/23/2016 18:04:35 => Feb/23/2016 18:04:40
647 Feb/23/2016 18:05:29 memory system, info sntp change time Feb/23/2016 18:05:28 => Feb/23/2016 18:05:29
648 Feb/23/2016 18:06:34 memory system, info sntp change time Feb/23/2016 18:06:33 => Feb/23/2016 18:06:34
649 Feb/23/2016 18:08:45 memory system, info sntp change time Feb/23/2016 18:08:42 => Feb/23/2016 18:08:45
650 Feb/23/2016 18:22:40 memory system, info sntp change time Feb/23/2016 18:22:21 => Feb/23/2016 18:22:40
651 Feb/23/2016 18:24:51 memory system, info sntp change time Feb/23/2016 18:24:48 => Feb/23/2016 18:24:51
652 Feb/23/2016 18:25:57 memory system, info sntp change time Feb/23/2016 18:25:55 => Feb/23/2016 18:25:57
653 Feb/23/2016 18:30:19 memory system, info sntp change time Feb/23/2016 18:30:13 => Feb/23/2016 18:30:19
654 Feb/23/2016 18:31:08 memory system, info sntp change time Feb/23/2016 18:31:07 => Feb/23/2016 18:31:08
655 Feb/23/2016 18:35:14 memory system, info sntp change time Feb/23/2016 18:35:08 => Feb/23/2016 18:35:14
656 Feb/23/2016 18:36:03 memory system, info sntp change time Feb/23/2016 18:36:02 => Feb/23/2016 18:36:03
657 Feb/23/2016 18:37:08 memory system, info sntp change time Feb/23/2016 18:37:07 => Feb/23/2016 18:37:08
658 Feb/23/2016 18:43:58 memory system, info sntp change time Feb/23/2016 18:43:48 => Feb/23/2016 18:43:58
659 Feb/23/2016 18:44:47 memory system, info sntp change time Feb/23/2016 18:44:46 => Feb/23/2016 18:44:47
660 Feb/23/2016 18:45:52 memory system, info sntp change time Feb/23/2016 18:45:51 => Feb/23/2016 18:45:52
661 Feb/23/2016 18:48:03 memory system, info sntp change time Feb/23/2016 18:48:00 => Feb/23/2016 18:48:03
662 Feb/23/2016 18:52:25 memory system, info sntp change time Feb/23/2016 18:52:19 => Feb/23/2016 18:52:25
663 Feb/23/2016 19:01:09 memory system, info sntp change time Feb/23/2016 19:00:57 => Feb/23/2016 19:01:09
664 Feb/23/2016 19:16:31 memory system, info sntp change time Feb/23/2016 19:16:09 => Feb/23/2016 19:16:31
665 Feb/23/2016 19:31:52 memory system, info sntp change time Feb/23/2016 19:31:31 => Feb/23/2016 19:31:52
666 Feb/23/2016 19:47:13 memory system, info sntp change time Feb/23/2016 19:46:52 => Feb/23/2016 19:47:13
667 Feb/23/2016 20:02:00 memory dhcp, info dhcpNoSecure assigned 192.168.60.240 to uuuuuuuuuuu
668 Feb/23/2016 20:19:17 memory system, info sntp change time Feb/23/2016 20:18:33 => Feb/23/2016 20:19:17
669 Feb/23/2016 20:20:07 memory system, info sntp change time Feb/23/2016 20:20:05 => Feb/23/2016 20:20:07
670 Feb/23/2016 20:21:12 memory system, info sntp change time Feb/23/2016 20:21:11 => Feb/23/2016 20:21:12
671 Feb/23/2016 20:25:43 memory dhcp, info dhcpNoSecure assigned 192.168.60.252 to HHHHHHHH
672 Feb/23/2016 20:28:02 memory system, info sntp change time Feb/23/2016 20:27:52 => Feb/23/2016 20:28:02
673 Feb/23/2016 20:28:51 memory system, info sntp change time Feb/23/2016 20:28:50 => Feb/23/2016 20:28:51
674 Feb/23/2016 20:29:56 memory system, info sntp change time Feb/23/2016 20:29:55 => Feb/23/2016 20:29:56
675 Feb/23/2016 20:36:46 memory system, info sntp change time Feb/23/2016 20:36:36 => Feb/23/2016 20:36:46
676 Feb/23/2016 20:39:29 memory system, info sntp change time Feb/23/2016 20:39:26 => Feb/23/2016 20:39:29
677 Feb/23/2016 20:40:18 memory system, info sntp change time Feb/23/2016 20:40:17 => Feb/23/2016 20:40:18
678 Feb/23/2016 20:41:24 memory system, info sntp change time Feb/23/2016 20:41:22 => Feb/23/2016 20:41:24

199

strods,

is there any hope for a minor change to LCD, adding a screen that only displays a logo from branding package or some custom png and nothing else?
More details and some discussion here, http://forum.mikrotik.com/t/lcd-displaying-a-bitmap-or-some-other-custom-message/95373/1

I’d be grateful and happy. :wink:

200

Are you really expecting fastpath when firewall rules are implemented?

Try fasttrack in this case.