v6.46beta [testing] is released!

Holy sh*t, I really hope that 5Ghz WiFi is stable now and we get this fix backported to long-term asap.

When will we see 6.46.0 release? I really want to See:
“*) ccr - improved general system stability” plus mentioned IPQ4019 fixes in a stable release.

When it’s ready. As that particular change was introduced recently, don’t expect quick release to ‘stable’ channel.

Probably the change was too late for 6.45.7… But if 6.46 will take some more time (I think so…) we could still hope for 6.45.8.

I am still waiting for the bitwise operator support for “ip6” data type. Let’s hope that will be available soon.

I wonder if this is the start of something to provide synchronisation for NV2/3? based access points without needing GPS modules. You only need relative synchronisation not something synchronised to absolute time to make it work.

Can you elaborate regarding *) ccr - improved general system stability ?
Thanks

Hi, I saw a strange error in a hAP ac^2 with beta59:

[admin@Mikrotik] > /system routerboard print 
       routerboard: yes
        board-name: hAP ac^2
             model: RBD52G-5HacD2HnD
     serial-number: B4A00A072300
     firmware-type: ipq4000L
  factory-firmware: 6.42.3
  current-firmware: 6.46beta59
  upgrade-firmware: 6.46beta59
[admin@Mikrotik] > /ping 1.1.1.1
action timed out - try again, if error continues contact MikroTik support and send a supout file (13)
[admin@Mikrotik] > :ping 1.1.1.1
action timed out - try again, if error continues contact MikroTik support and send a supout file (13)
[admin@Mikrotik] > /ping [:resolve ipv6.google.com]
action timed out - try again, if error continues contact MikroTik support and send a supout file (13)
[admin@Mikrotik] > :tool traceroute 192.168.88.252
action timed out - try again, if error continues contact MikroTik support and send a supout file (13)

It was consistently reproducible, and both ping ipv6 addresses and traceroute failed the same, as can be seen.

After rebooting the behaviour returned to normal. The machine had slightly less than one week uptime.

Hi Mikrotik Team,

Please add the following features in upcomming release:

1. Walled garden or some filtering service to limit the invalid PPPOE request hits.–> To filter Unnecessary Hits or Request from unauthenticated PPPOE Clients.
2. IPv6 Accounting for radius. → Most important and expected by almost all ISP’s

3. Hotspot Service for Ipv6
4. NATv6 Service.
5. DHCPv6 IP server → for giving IPv6 Address to direct clients or PPPOEv6 Service.

Looking forward to your valuable reply…

IMO, they are likely to only introduce things like that in v7, not in 6.x.

Hello!
looks like there is BUG in RoMON - can`t connect …

Please use the English language.

Hope Mikrotik ROS v7.x will be a biggest change with all lots of features… :slight_smile: :smiley:

Version 6.46beta68 has been released.

Before an upgrade:

  1. Remember to make backup/export files before an upgrade and save them on another storage device;
  2. Make sure the device will not lose power during upgrade process;
  3. Device has enough free storage space for all RouterOS packages to be downloaded.

What's new in 6.46beta68 (2019-Nov-21 09:13):

**MAJOR CHANGES IN v6.46:

!) lora - added support for LoRaWAN low-power wide-area network technology for MIPSBE, MMIPS and ARM;
!) package - accept only packages with original filenames (CVE-2019-3976);
!) package - improved package signature verification (CVE-2019-3977);
!) security - fixed improper handling of DNS responses (CVE-2019-3978, CVE-2019-3979);
----------------------**

Changes in this release:

!) lora - added support for LoRaWAN low-power wide-area network technology for MIPSBE, MMIPS and ARM;
*) backup - store automatically created backup file in "flash" directory;
*) capsman - improved radar detection algorithm;
*) certificate - added progress bar when creating certificate request (CLI only);
*) certificate - added support for certificate request signing with EC keys;
*) certificate - allow specifying "file-name" parameter for export (CLI only);
*) certificate - allow specifying "name" parameter for import (CLI only);
*) certificate - removed "key-size" parameter for "create-certificate-request" command;
*) defconf - fixed default configuration generation on SXT R (introduced in v6.46beta28);
*) dhcpv4-client - allow empty "dhcp-options" parameter when adding new client;
*) dhcpv4-server - improved stability when RADIUS Interim update is sent;
*) ike2 - improved stability when retransmitting first packet as responder;
*) ipsec - fixed policy "sa-src-address" detection from "local-address" (introduced in v6.45);
*) led - fixed default LED configuration for RBLHG-2nD and RBLHG-5HPnD;
*) lte - added support for D402 modem;
*) ptp - added support for IEEE 1588 Precision Clock Synchronization Protocol on CRS317-1G-16S+ (CLI only);
*) route - fixed area range summary route installation in VRF;
*) snmp - added option to monitor "link-downs" parameter using MIKROTIK-MIB;
*) snmp - fixed "dot1dBasePort" index offset for BRIDGE-MIB;
*) snmp - fixed "ifLastChange" OID reporting for IF-MIB;
*) snmp - improved interface status reporting for IfOperStatus OID;
*) ssh - fixed output printing when "command" parameter used;
*) supout - include information from all LTE interfaces;
*) switch - ignore "default-vlan-id" property after switch reset on RTL8367 switch chip;
*) telnet - fixed successful connection establishment output in console (introduced in v6.46beta28);
*) timezone - updated time zone database to version 2019c;
*) ups - improved compatibility with APC UPS's;
*) winbox - fixed "CAPs Scanner" stopping;
*) wireless - added "indonesia4" regulatory domain information;
*) wireless - added "push-button-5s" value for "wps-mode" parameter;
*) wireless - added U-NII-2 support forRBSXTsqG-5acD, RBLHGG-5acD-XL, RBLHGG-5acD, RBLDFG-5acD, RBDiscG-5acD;

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 expected or after crash.

Bug still present: I’ve written here also: http://forum.mikrotik.com/t/bug-winbox-webfig-wireless-acl-signal-strength-range-input-validation/134895/1
Post could be moved or deleted, I didn’t know it was beta related at the time. Done the tests today :slight_smile:

Yep still no basic wireless function in this beta :smiley:

Signal Strength setting using Winbox will be fixed in the next beta version.

Hi,

After upgrading to version 6.46beta68, no IPSEC connection works anymore.

grusu what router are you using?

RB4011 l2tp+ipsec not work

RouterBOARD 1100Dx4 Dude Edition.
I have multiple l2tp/ipsec connections to my clients. After update from 6.46beta59 to 6.46beta68 no connection has ever worked.
And it seemed to me that certain sites were not loading properly. I don’t know if it has anything to do with it.
I returned to the 6.45.7 version.