v6.44beta [testing] is released!

emils · Tue Sep 11, 2018 1:47 pm

Version 6.44beta6 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.44beta6 (2018-Sep-11 08:52):

Changes in this release:

!) upgrade - release channels renamed - "bugfix" to "long-term", "current" to "stable" and "release candidate" to "testing";
!) upgrade - "testing" release channel now can contain "beta" together with "release-candidate" versions;
*) chr - assign interface names based on underlying PCI device order on KVM;
*) crs317 - fixed packet forwarding on bonded interfaces without hardware offloading;
*) crs3xx - improved data transmission between 10G and 1G ports;
*) dhcpv4-server - fixed service becoming unresponsive after interface leaves and enters the same bridge;
*) dhcpv6-client - log only failed pool additions;
*) ethernet - fixed IPv6 packet forwarding on IPQ4018 devices;
*) hotspot - properly update dynamic "walled-garden" entries when changing "dst-host";
*) ike2 - added option to specify certificate chain;
*) ike2 - fixed local address lookup when initiating new connection;
*) ike2 - fixed rare authentication and encryption key mismatches after rekey with PFS enabled;
*) lte - fixed DHCP relay packet forwarding when in passthrough mode;
*) lte - fixed Jaton/SQN modems preventing router from booting properly;
*) rb3011 - added IPsec hardware acceleration support;
*) routerboard - fixed memory tester reporting false errors on IPQ4018 devices ("/system routerboard upgrade" required);
*) sniffer - made "connection", "host", "packet" and "protocol" sections read-only;
*) switch - fixed ACL rules on IPQ4018 devices;
*) upnp - improved UPnP service stability when handling HTTP requests;
*) w60g - added "frequency-list" setting;
*) w60g - fixed interface LED status update on connection;
*) winbox - allow setting "network-mode" to "auto" under LTE interface settings;
*) wireless - removed "czech republic 5.8" regulatory domain information as it overlaps with "ETSI 5.7-5.8";

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.

Tue Sep 11, 2018 1:51 pm

O_o "beta"!!!! The hell just froze over!! what happened there?

honzam · Tue Sep 11, 2018 1:54 pm

Now Beta. And Alpha? Alpha V7?

bennyh · Tue Sep 11, 2018 2:14 pm

Now Beta. And Alpha? Alpha V7?

Guys! If there will be ROS 7 stable release, we should celebrate it with a big worldwide party

ontopic:Did someone test the v6.44 on rb3011?

upower3 · Tue Sep 11, 2018 3:34 pm

!) upgrade - release channels renamed - "bugfix" to "long-term", "current" to "stable" and "release candidate" to "testing";

Tell me the truth, who decided that current is stable? It is bugfix that can be considered stable, while current is some bleeding-edge and sometimes even "never to use in prod" version.

Will the naming be backward aware, like cli to accept both bugfix and long-term?

And what to do with old releases (6.29) which are not aware of branches at all and consider itself as stable?

schadom · Tue Sep 11, 2018 5:40 pm

Would be very nice to see some routing (especially BGP, BGP4 SNMP MIBs, etc.) improvements for 6.44!
Also currently peering session re-connects when it's comment is changed in Winbox. This is annoying and could be changed.

Bobstonom · Tue Sep 11, 2018 6:20 pm

Just saw this. Will definitely check it out.

By the way, newbie here. Aside from being a MikroTik novice, I'm also a critter lover. I'm usually found at home, treating my Pomeranian, Jules, to his nylabones and watching TV with my wife. Such a simple, yet, happy life. Cheers, fellas!

z1022 · Tue Sep 11, 2018 6:25 pm

Now Beta. And Alpha? Alpha V7?

Alpha V7 will be launched after v6.99 or v6.999 released

upower3 · Tue Sep 11, 2018 6:55 pm

currently peering session re-connects when it's comment is changed in Winbox.

So to say, MT used to down and up again PPP-interfaces when you change comment on it! It was this way some time ago, not sure for now, but this was some "bright" idea these days (and maybe today).

honzam · Tue Sep 11, 2018 6:57 pm

Would be very nice to see some wireless (especially NV2, AC) improvements for 6.44!
The bandwidth per 20Mhz channel is very small. Compared to competition...

upower3 · Tue Sep 11, 2018 6:58 pm

Now Beta. And Alpha? Alpha V7? :)
Alpha V7 will be launched after v6.99 or v6.999 released :lol: :lol: :lol:

I suspect they will release some absolutely new change in the system somewhere between 6.49 and 6.49.7, so noone will ever be able to predict that. Look at new bridge implementation introduction, some serious change that is there in current (sorry, so called stable) release but not in the bugfix, and you get the idea.

djdrastic · Tue Sep 11, 2018 7:06 pm

!) upgrade - release channels renamed - "bugfix" to "long-term", "current" to "stable" and "release candidate" to "testing";

Hi Mikrotik will this release channel naming be pushed down into other releases at a later time ?
All my ansible scripts at present that upgrade 100's of rb's point to "bugfix" , "current" and "release candidate"

Gonna have to do a bit of retooling if so.

notToNew · Tue Sep 11, 2018 9:13 pm

!) upgrade - release channels renamed - "bugfix" to "long-term", "current" to "stable" and "release candidate" to "testing";

That's good, but we need another channel named oldstable, where 6.42 should go and stay for at least several weeks.

At least do make downgrading more seamless when necessary.

mkx · Tue Sep 11, 2018 9:35 pm

That's good, but we need another channel named oldstable, where 6.42 should go and stay for at least several weeks.

At least do make downgrading more seamless when necessary.

If MT is not going to release new versions in 6.42.x series, then this series does not need its own channel. If you want to downgrade your RB to some particular older version of ROS you can always download it (manually construct download URL if every other option to get DL link fails) and install.
Channels are only useful for semi-automated upgrades and for users that trust in MT decission about which version belongs to which category of stability. If you're not one of us, then you can completely ignore channel naming and install whatever version of ROS you believe is best for yor RBs.

boldsuck · Tue Sep 11, 2018 9:40 pm

!) upgrade - release channels renamed - "bugfix" to "long-term", "current" to "stable" and "release candidate" to "testing";

That's good, but we need another channel named oldstable, where 6.42 should go and stay for at least several weeks.

At least do make downgrading more seamless when necessary.

Upload 'old Firmware' to Router and reboot...
...downgrade ready.

Chupaka · Thu Sep 13, 2018 3:00 pm

You'll need to press Downgrade button, not just reboot

But yes, that's that simple.

bennyh · Thu Sep 13, 2018 4:08 pm

IPSec results appeared on the RB3011 product page as the Mikrotik guys promised, but theese values are lower than IPSec results on the 750Gr3 page. The HW crypt core is weaker in the RB3011 or there will be optimalizations in further ROS releases?

blingblouw · Thu Sep 13, 2018 4:54 pm

seems this release gave us a wireless channel 66000 on w60g interface. Nice!

Thu Sep 13, 2018 4:54 pm

Mikrotik, please explain why you needed to rename the release channels. Also please explain what real change does this mean. Without that the renaming of current to stable is very confusing for those who came recently or do not know that the only well tested bugfix could be considered as stable in reality.

bennyh · Thu Sep 13, 2018 5:35 pm

Mikrotik, please explain why you needed to rename the release channels. Also please explain what real change does this mean. Without that the renaming of current to stable is very confusing for those who came recently or do not know that the only well tested bugfix could be considered as stable in reality.

Maybe they think the new Bridge module is mature enough, to mark as stable. This naming method was earlier too, so they only returned to that.

MonkeyDan · Thu Sep 13, 2018 5:40 pm

seems this release gave us a wireless channel 66000 on w60g interface. Nice!

Be aware this overlaps with 64800: https://en.wikipedia.org/wiki/Wireless_ ... e#Channels
Also, it appears this isn’t in the default frequency list for station mode: https://wiki.mikrotik.com/wiki/Manual:I ... properties

emils · Fri Sep 14, 2018 10:13 am

IPSec results appeared on the RB3011 product page as the Mikrotik guys promised, but theese values are lower than IPSec results on the 750Gr3 page. The HW crypt core is weaker in the RB3011 or there will be optimalizations in further ROS releases?

Currently the RB3011 IPsec performance is comparable with any of the IPQ4018 routers (like 450Gx4, hAP ac2), it actually shares the same driver, however there are 4 total crypto modules on RB3011 and as of now only 1 is enabled, meaning it has the potential to achieve even higher throughput. Anyway, we will continue to develop this driver, but in the mean time, 400Mbps over the 100Mbps which you were able to achieve with software crypto is a valuable gain in my opinion.

bennyh · Fri Sep 14, 2018 10:49 am

IPSec results appeared on the RB3011 product page as the Mikrotik guys promised, but theese values are lower than IPSec results on the 750Gr3 page. The HW crypt core is weaker in the RB3011 or there will be optimalizations in further ROS releases?
Currently the RB3011 IPsec performance is comparable with any of the IPQ4018 routers (like 450Gx4, hAP ac2), it actually shares the same driver, however there are 4 total crypto modules on RB3011 and as of now only 1 is enabled, meaning it has the potential to achieve even higher throughput. Anyway, we will continue to develop this driver, but in the mean time, 400Mbps over the 100Mbps which you were able to achieve with software crypto is a valuable gain in my opinion.

Yes, thats true

Only that was strange, the smaller and cheaper 750Gr3 is stronger in it, but I got a deep explanation from you. Thank you!

Cal5582 · Fri Sep 14, 2018 6:07 pm

RBM11G and R11e-5HacT looses the R11e-5HacT in this software revision and in 6.43 downgrading to 6.42.7 auto-magically makes the wireless card come back so it is a software issue and not a hardware issue. it is also repeatable during testing.

honzam · Fri Sep 14, 2018 6:19 pm

RBM11G and R11e-5HacT looses the R11e-5HacT in this software revision and in 6.43 downgrading to 6.42.7 auto-magically makes the wireless card come back so it is a software issue and not a hardware issue. it is also repeatable during testing.

I reported the same problem to support. After upgrade to 6.43 rbM11 looses card. No answer yet.

Cal5582 · Fri Sep 14, 2018 6:20 pm

good to know its not just me. i sent a supout to them and an email describing the issue but havent heard anything yet.

Cal5582 · Fri Sep 14, 2018 6:28 pm

just out of curiosity are you also using an RBM11g also or something else with MPCIe?

honzam · Fri Sep 14, 2018 7:02 pm

RBM11G and R11e-5HacD

ozone · Sat Sep 15, 2018 6:26 pm

RBM11G and R11e-5HacT looses the R11e-5HacT in this software revision and in 6.43 downgrading to 6.42.7 auto-magically makes the wireless card come back so it is a software issue and not a hardware issue. it is also repeatable during testing.

RBM33g+R11e-5HacT does seem to work. (design closely related to RBM11g)

But my connection issues still remain (viewtopic.php?f=3&t=136950)
Support case is about that is also still open, although I haven't received any feedback from MT about it for weeks now

RBM33 still doesn't seem to be a viable contender for a hap-ac replacement unfortunately.
(is design been given up???)

jondavy · Sat Sep 15, 2018 9:52 pm

is not allowing to create qos scripts with parent queue with hotspot,
with pppoe works normal

schadom · Sun Sep 16, 2018 1:10 am

Please consider some BGP fixes and improvements for 6.44:

- make route matching via /ip route print where=.. with BGP full feeds faster
- do not reset/re-establish a BGP session when it's comment is changed
- improve overall BGP convergence time on CCR/tile

+ introduce BGP4 SNMP MIBs
+ introduce priority/order feature for BGP sessions

Thanks

epkulse · Sun Sep 16, 2018 12:51 pm

Upgraded now, and I am not able to login anymore. Password appears to be changed. Same problem in Webfig as SSH. Known issue? Any idea how to restore?

grusu · Sun Sep 16, 2018 12:52 pm

Upgraded now, and I am not able to login anymore. Password appears to be changed. Same problem in Webfig as SSH. Known issue? Any idea how to restore?

viewtopic.php?f=21&t=139189

epkulse · Sun Sep 16, 2018 12:59 pm

Well, I guess it should still be possible to login with Webfig or SSH?

grusu · Sun Sep 16, 2018 1:11 pm

Well, I guess it should still be possible to login with Webfig or SSH?

Hi,

Try to update winbox to 3.18 version.
From which version you upgraded RouterOS to v6.44beta?

Geo

Rico40 · Sun Sep 16, 2018 1:57 pm

Update the certificate in the browser. I had this problem too and it helped me.

epkulse · Sun Sep 16, 2018 3:33 pm

I used Webfig on a MAC... Have winbox4mac on 3.17 - but that should not make any difference... As SSH does not work, it is not browser dependent, I guess...

epkulse · Sun Sep 16, 2018 3:45 pm

ssh says "permission denied" all the time...
admin@192.168.88.6's password:
Permission denied, please try again.

Does not work to login with blank password - so it seems something is corrupted...

The device is a RB751G-2HnD running as AP - I use it as a test device för new releases. So, no panic - but maybe alarming to others...

epkulse · Sun Sep 16, 2018 3:56 pm

Winbox 3.18 - not working... When running it on a PC...

grusu · Sun Sep 16, 2018 6:02 pm

Winbox 3.18 - not working... When running it on a PC...

Try to clear cache:

Tools > Clear Cache

epkulse · Sun Sep 16, 2018 6:52 pm

That does not help.

Somehow my Password has been corrupted when I upgraded. So, likely something wrong with this upgrade which I assume needs to taken care of as it would affect a lot of users otherwise...

I have tried Webfig, Winbox, SSH - none of these access methods allow me to use the Password I have defined. Nor can i login by omitting the password - so it is not restored to default or something. Appears to be working, I can connect to wifi (run by Capsman) - but I am unable to access it as admin anymore Seems I have to make a HW-reset or something... Not nice, should you have lots of these devices.

As I have said before, this is not a critical production device for me - but still quite confusing how this could happen...

emils · Tue Sep 18, 2018 10:26 am

Version 6.44beta9 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.44beta9 (2018-Sep-17 07:20):

MAJOR CHANGES IN v6.44:
----------------------
!) upgrade - release channels renamed - "bugfix" to "long-term", "current" to "stable" and "release candidate" to "testing";
!) upgrade - "testing" release channel now can contain "beta" together with "release-candidate" versions;
----------------------

Changes in this release:

!) cloud - added command "/system backup cloud" for backup storing on cloud (CLI only);
*) bridge - improved packet handling when hardware offloading is being disabled;
*) cloud - ignore "force-update" command if DDNS is disabled;
*) crs3xx - fixed possible memory leak when disabling bridge interface;
*) defconf - properly clear global variables when generating default configuration after RouterOS upgrade;
*) discovery - properly use Sytem ID for "software-id" value on CHR;
*) e-mail - added info log message when e-mail is sent successfully;
*) lte - fixed LTE interface not working properly after reboot on RBSXTLTE3-7;
*) proxy - removed port list size limit;
*) romon - improved reliability when processing RoMON packets on CHR;
*) routerboard - show "boot-os" option only on devices that have such feature;
*) switch - fixed port mirroring on devices that do not support CPU Flow Control;
*) webfig - allow to change user name when creating a new system user;
*) webfig - fixed time interval settings not applied properly under "IP/Kid Control/Kids" menu;
*) winbox - added 4th chain selection for "HT TX chains" and "HT RX chains" under "CAPsMAN/CAP Interface/Wireless" tab;
*) winbox - added "allow-dual-stack-queue" setting to "IP/DHCP Server/Leases" menu;
*) winbox - added "allow-dual-stack-queue" setting to "IPv6/DHCPv6 Server/Bindings" menu;
*) winbox - added "radio-name" setting to "CAPsMAN/CAP Interface/General" tab;
*) winbox - added "secondary-channel" setting to "CAPsMAN/CAP Interface/Channel" tab;
*) winbox - fixed corrupt user database after specifying allowed address range (introduced in v6.43);
*) winbox - make bridge port "untrusted" by default when creating new port;
*) winbox - show "IP/Cloud" menu on CHR;
*) winbox - show "System/RouterBOARD/Mode Button" on devices that have such feature;

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.

mducharme · Tue Sep 18, 2018 10:36 am

Backup stored on cloud? Great idea, but how is this accessed, if you need to restore? Even more importantly, how is it secured? The idea of a backup with confidential passwords and other information floating in the aether for a hacker to conveniently steal is a bit concerning. I use online backup all the time, but that comes with details as to how the data is protected, etc.

Tue Sep 18, 2018 10:39 am

!) cloud - added command "/system backup cloud" for backup storing on cloud (CLI only);

Two questions:

Can this cloud backup be encrypted?
Since Mikrotik cloud services are bound to the device's serial number, is there any way to retrieve a backup when the original device is lost?

Tue Sep 18, 2018 10:40 am

Remember that in MikroTik RouterOS, backup file is for restoring past configuration on the same device, not a safeguard against a lost or damaged device, for restoring on other devices, you should be using "export" config files.

mducharme · Tue Sep 18, 2018 10:49 am

Remember that in MikroTik RouterOS, backup file is for restoring past configuration on the same device, not a safeguard against a lost or damaged device, for restoring on other devices, you should be using "export" config files.

Officially, yes, but if the device is being replaced with one of the same model and the MAC addresses are reset after the restore, if you are in a pinch and have nothing else, the .backup does work, even though it is not the best choice. I imagine that is why andriys is asking and I would echo it - even though it is bad practice, it can be better to have the .backup than to have to recreate a complicated config from scratch, if whoever was managing the router was not careful enough to keep good .rsc backups.

What about integrating the cloud into the "My Account" on MikroTik, so that you could view a list of previous backups from the MikroTik account and download them from there? Just an idea.

nescafe2002 · Tue Sep 18, 2018 10:55 am

Or a backup explorer so you can fetch the configuration export from a binary backup file. Like the supout.rif viewer.

janisk · Tue Sep 18, 2018 11:02 am

viewtopic.php?f=1&t=135603&p=687001#p687001

*) It is a requirement for the file to be encrypted - see update to backup file encryption, only the new kind is accepted by IP Cloud Backup
*) if you save secure-download-key you can retrieve the file from another router
*) integration in the account is planned and it is coming sometime later

schadom · Tue Sep 18, 2018 11:34 am

Remember that in MikroTik RouterOS, backup file is for restoring past configuration on the same device, not a safeguard against a lost or damaged device, for restoring on other devices, you should be using "export" config files.

Why can't device-specific stuff like MAC-addresses simply be removed from the backup files?

mrz · Tue Sep 18, 2018 12:25 pm

Because it is whole system backup.

msatter · Tue Sep 18, 2018 12:48 pm

Remember that in MikroTik RouterOS, backup file is for restoring past configuration on the same device, not a safeguard against a lost or damaged device, for restoring on other devices, you should be using "export" config files.

Export config files is death for me. Tried everything what is mentioned in the wiki and forum but never succeeded to import a config file for years.

Restoring backup files on other devices with same or similar hardware goes fine and after restore also restore the MAC's of the new device.

Tue Sep 18, 2018 1:49 pm

Without an example we can not comment why you are not being able to import .rsc file.

We recommend that you import file step-by-step if it is failing. Then you will see at which point configuration is not accepted and you can fix it or report a problem to support@mikrotik.com if there is one.

Export/import must work without any problems on the same model RouterBOARD if the same RouterOS version is installed on both devices and the same software packages are enabled.

und3ath · Tue Sep 18, 2018 4:56 pm

lhg 60 + 6.44 beta9 - interface wlan60-1 window in winbox, Status tab: only frequency is shown, anything else is empty. SNMP also stopped working for these values.

2nd problem - I see only 4 frequencies - there is no 66000 MHz option

doneware · Tue Sep 18, 2018 5:57 pm

Why can't device-specific stuff like MAC-addresses simply be removed from the backup files?

i'd like to have something like '/sys backup load name="filename.backup" password="dragon" keep-mac-addresses=yes

or an ability to auto-run commands upon successful restore (like a cli command to restore original mac addresses)

doneware · Tue Sep 18, 2018 6:05 pm

Without an example we can not comment why you are not being able to import .rsc file.

in case of big export files you can run into situations, when the next command is just not accepted. like you add an object as nameA, then try to set something on the same object by its name, and CLI responds as "not found". carefully tuned delay statements help with these issues.

but in general my biggest PITA is
- not having the users
- not having the ssh keys
- not having the certificates
in the export file. this renders the stuff unusable in many cases.

right now we have the user passwords as hashes, so i see no point why this "hash" could not be rendered as base64 or anything printable. the same goes for the keys and certificates. esp certificates are kind of hard to come by: the export file contains references at some services (like sstp client) to a certificate by its name, and the certificate is just not there. if you manually export the certs and re-import them, they lose their original names, so the references are broken.

with /system reset-config you can have the user accounts remain intact, so an 'import' of a previously exported rsc 'can' work. but i can't say the same for the certs and keys.
but in general, i'd like to have the same 'in-line' exports for users (along with their hashes) as well.

Sob · Tue Sep 18, 2018 8:02 pm

I agree with @doneware, an export that exports everything would be dream come true. I don't even care if it can be imported at once.

Backup is just impractical binary mess for me. I don't break my configs in a way that I'd need to restore them. But I do need to know what was there, in case the router dies and I need to replace it. In most cases I won't have the same model available, at least initially, so restoring backup meant for same device is not exactly ideal.

Plus you can't see what's in backup, unless you restore it somewhere. I have set up automated exports and the output is saved in version control system, so I know what exactly changed and when. And it's perfect for me, but sadly incomplete. Luckily not every router has certificates and recreating users is bearable. But it would be better if export had everything.

amokkatmt · Tue Sep 18, 2018 10:03 pm

After updating to 6.44beta9 I can not get output of command execution over SSH, using putty's plink. What I mean:

plink.exe -v -ssh username@hostname -i .\mikrotik-priv.key.ppk -sshlog .\lkjlkj.log ":put 'hello';/quit"

What I got:

...........
Event Log: Opened main channel
Outgoing packet #0x9, type 98 / 0x62 (SSH2_MSG_CHANNEL_REQUEST)
  00000000  00 00 00 00 00 00 00 22 73 69 6d 70 6c 65 40 70  ......."simple@p
  00000010  75 74 74 79 2e 70 72 6f 6a 65 63 74 73 2e 74 61  utty.projects.ta
  00000020  72 74 61 72 75 73 2e 6f 72 67 00                 rtarus.org.
Outgoing packet #0xa, type 98 / 0x62 (SSH2_MSG_CHANNEL_REQUEST)
  00000000  00 00 00 00 00 00 00 04 65 78 65 63 01 00 00 00  ........exec....
  00000010  12 3a 70 75 74 20 27 68 65 6c 6c 6f 27 3b 2f 71  .:put 'hello';/q
  00000020  75 69 74                                         uit
Incoming packet #0x9, type 99 / 0x63 (SSH2_MSG_CHANNEL_SUCCESS)
  00000000  00 00 01 00                                      ....
Event Log: Started a shell/command
Incoming packet #0xa, type 98 / 0x62 (SSH2_MSG_CHANNEL_REQUEST)
  00000000  00 00 01 00 00 00 00 0b 65 78 69 74 2d 73 74 61  ........exit-sta
  00000010  74 75 73 00 00 00 00 00                          tus.....
Event Log: Server sent command exit status 0
Incoming packet #0xb, type 97 / 0x61 (SSH2_MSG_CHANNEL_CLOSE)
  00000000  00 00 01 00                                      ....
Outgoing packet #0xb, type 96 / 0x60 (SSH2_MSG_CHANNEL_EOF)
  00000000  00 00 00 00                                      ....
Outgoing packet #0xc, type 97 / 0x61 (SSH2_MSG_CHANNEL_CLOSE)
  00000000  00 00 00 00                                      ....
Event Log: Disconnected: All channels closed

But I expected command output. This was test command. What I run in my project is

:while (true) do={delay 300; :put "999 BEG";/ip firewall address-list print terse without-paging where list="china"; :put "999 END"}

Here I am exporting address-list "china" every 5 minutes via SSH for parsing etc. This command should run forever, thus keeping SSH connection forever too. But after updating from beta6 to beta9, ssh connection is closing immediately without giving me any output on plink's stdout.
Simple commands are executed actually, tried "/system ntp server set manycast=yes" and it worked.

raffav · Tue Sep 18, 2018 10:11 pm

Without an example we can not comment why you are not being able to import .rsc file.

We recommend that you import file step-by-step if it is failing. Then you will see at which point configuration is not accepted and you can fix it or report a problem to support@mikrotik.com if there is one.

Export/import must work without any problems on the same model RouterBOARD if the same RouterOS version is installed on both devices and the same software packages are enabled.

Also can use that third tool that someone biuld that can read rsc file and remove unnecessary lines like mac address

Sent from my XT1580 using Tapatalk

Bobstonom · Wed Sep 19, 2018 9:50 am

"Because it is whole system backup."

Oh, that's why. Thanks for clearing it up.

pe1chl · Wed Sep 19, 2018 10:12 am

*) chr - assign interface names based on underlying PCI device order on KVM;

Is this specificially for Linux KVM or is it also for other virtual environments?
I have an interface name issue under VMware ESXi 6.7 would that be fixed by this?
(I want the ether interfaces named in icreasing PCI bus number)

pe1chl · Wed Sep 19, 2018 10:24 am

I have set up automated exports and the output is saved in version control system, so I know what exactly changed and when. And it's perfect for me, but sadly incomplete. Luckily not every router has certificates and recreating users is bearable. But it would be better if export had everything.

I am in the same boat, and for me the fact that certificates are not in /export is a showstopping reason not to use certificates, even when the router is putting "insecure configuration, suggest to use certificates" comments in some config items.
When it is really not wanted to put certificates in a normal export, there should be a certificate-only backup that you can restore on another device (even another type) without issue!
For example, we have 2 CCR1009-8G-1S-1S+ in the network. Should they fail, they are unobtanium so I should get something like CCR1009-7G-1C-1S+ instead, or maybe I would then choose a RB1100AHx4 or RB4011iGS+RM. It should then be possible to transfer the configuration, and while I understand that it is not so easy to make a backup file format that would simply restore on another type of router (although some other manufacturers sort of have that!) it should at least be possible to backup and restore those certificates, keys and users. The remainder of the config can then be transferred using a /export and some editing.

BTW, there are still issues in the /export. I tried the above yesterday to make a cold standby backup for a CCR1009-8G-1S-1S+ as a CHR under VMware ESXi and I encountered two /export issues (apart from the fact I was using 6.42.7 /export in a 6.43.1 CHR so the /ipsec peer config failed, but I understand that):

- /ipv6 dhcp-server is exported before /ipv6 pool but server refers to pool names
- /ip neighbor discovery-settings set discover-interface-list=!somelistname forgets to export the ! (not)

Cha0s · Wed Sep 19, 2018 10:29 am

I have set up automated exports and the output is saved in version control system, so I know what exactly changed and when.

Can you give more info on your setup/workflow?
I am interested in implementing something similar.

Thanks.

mducharme · Wed Sep 19, 2018 8:05 pm

I have experienced occasional problems doing import of an rsc due to race conditions. If RSC is imported on boot, there needs to be a delay programmed in for the ethernet interfaces to initialize before the config begins to apply. If the RSC is imported at any other time (ex. booted router with "no default configuration"), I have seen it happen where some settings do not take effect the moment that the command is run, but instead are delayed a few seconds later. The import then fails partway through because it hits some other setting that depends on a previous one that hasn't applied yet, and again the solution is to add a delay of one or two seconds into the import rsc file to give enough time for the previous setting to activate before reaching the dependent setting. It would be really nice if this would happen automatically without needing to worry about this.

Sob · Thu Sep 20, 2018 12:24 am

@Cha0s: What I currently use is a little old and messy (php + svn). Long-term plan is to write something nicer and share it here in the forum too, but it might take a while. But bare bones version can be:

for /F "tokens=*" %%A in (hosts.txt) do plink -ssh -i backup.ppk backup@%%A /export | grep "^[^#]" > %%A.rsc
git add *.rsc
git commit -m "automated backup"

File backup.ppk is PuTTY's private key and hosts.txt is text file with list of addresses or hostnames. Grep strips comments, to only record real changes. On router there's backup user (with ssh key):

/user group
add name=backup policy=ssh,read,sensitive,!local,!telnet,!ftp,!reboot,!write,!policy,!test,!winbox,!password,!web,!sniff,!api
/user
add group=backup name=backup

And that's it, just run it as often as needed, from scheduler or manually. There's a lot of room for improvements (logging, notifications on failure, ...), but even this is usable as quick'n'dirty solution. Or it could be done in reverse, with routers uploading their config to some central server and a script there could handle the rest. Now if only the export exported everything...

Cha0s · Thu Sep 20, 2018 12:40 am

Thanks!

pe1chl · Thu Sep 20, 2018 1:04 am

It can be a good idea to use "/export terse" as this tends to result in easier to identify changes e.g. when using gitweb or other colored-diff tools or when you want to grep your config collection for the occurrence of certain constructs (with meaningful output).
This was added in 6.40 and before that I used a simple perl script that converts a classic export to terse form.

jkarras · Thu Sep 20, 2018 5:06 am

I have set up automated exports and the output is saved in version control system, so I know what exactly changed and when.
Can you give more info on your setup/workflow?
I am interested in implementing something similar.

Thanks.

RANCID works for this. There are runners for a lot of different NOS.

http://www.shrubbery.net/rancid/

Oxidized is a more modern replacement that also supports ROS.

https://github.com/ytti/oxidized/blob/m ... S-Types.md

server8 · Thu Sep 20, 2018 1:29 pm

2nd problem - I see only 4 frequencies - there is no 66000 MHz option

Mikrotik 60 GHZ@66000 MHz ???

blingblouw · Thu Sep 20, 2018 1:59 pm

2nd problem - I see only 4 frequencies - there is no 66000 MHz option
Mikrotik 60 GHZ@66000 MHz ???

CLI only. You will also need to add it to frequency-list of remote end.

server8 · Thu Sep 20, 2018 5:27 pm

CLI only. You will also need to add it to frequency-list of remote end.

I miss it thank you for the info

Ivoshiee · Mon Sep 24, 2018 10:31 pm

The 6.44beta9 has no more information about wlan60 link status except "connected" and "link downs" count. Signal info and the rest of stuff is nowhere to be found.

Tue Sep 25, 2018 12:08 am

Id like to find out about helping with the Beta test on this...Ive used the big program for many years now, and have been on the Beta list for quite some time.

I just started using PE, as Ive changed employers, and my new job wont allow me to install anything on my computer there, but I can use USB U3 programs. Im already really liking this, and would be glad to assist with your testing

Thanks
-Chris

What are you talking about? What are USB U3 programs? Please stop posting such posts.

Sob · Tue Sep 25, 2018 12:35 am

@BartoszP: It's probably someone preparing the ground for later, establish the presence and then add spammy link in signature or something. Has three posts so far and none of them makes any sense.

bigal488 · Wed Sep 26, 2018 6:51 pm

After updating to 6.44beta9 I can not get output of command execution over SSH, using putty's plink. What I mean:
Code: Select all
plink.exe -v -ssh username@hostname -i .\mikrotik-priv.key.ppk -sshlog .\lkjlkj.log ":put 'hello';/quit"

I'm seeing the same with beta9 - no output from commands run via ssh e.g.

ssh -i "mikrotik.key" admin@192.168.0.254 ":put \"hello\""

produces nothing...

tigro11 · Thu Sep 27, 2018 12:56 am

if I recover a backup, it gives me error 6.
the backup is NOT encrypted and not even the password.

nescafe2002 · Sun Sep 30, 2018 11:47 am

amokkatmt, bigal488, did you report the ssh output issue to support?

emils · Mon Oct 01, 2018 8:51 am

Thank you everyone, single line SSH command execution will be fixed in the next beta version.

bennyh · Tue Oct 02, 2018 12:10 pm

New beta out:
rb3011 - implemented multiple engine IPsec hardware acceleration support;
Cool

mikruser · Tue Oct 02, 2018 12:42 pm

what is "multiple engine"??

nescafe2002 · Tue Oct 02, 2018 1:28 pm

Search for "ipsec" in this topic.

viewtopic.php?f=21&t=139057&p=686156#p686156

Currently the RB3011 IPsec performance is comparable with any of the IPQ4018 routers (like 450Gx4, hAP ac2), it actually shares the same driver, however there are 4 total crypto modules on RB3011 and as of now only 1 is enabled, meaning it has the potential to achieve even higher throughput. Anyway, we will continue to develop this driver, but in the mean time, 400Mbps over the 100Mbps which you were able to achieve with software crypto is a valuable gain in my opinion.

emils · Tue Oct 02, 2018 1:38 pm

Version 6.44beta14 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.44beta14 (2018-Oct-01 12:01):

MAJOR CHANGES IN v6.44:
----------------------
!) cloud - added command "/system backup cloud" for backup storing on cloud (CLI only);
!) upgrade - release channels renamed - "bugfix" to "long-term", "current" to "stable" and "release candidate" to "testing";
!) upgrade - "testing" release channel now can contain "beta" together with "release-candidate" versions;
----------------------

Changes in this release:

*) bridge - do not learn untagged frames when filtering only tagged packets;
*) bridge - fixed packet forwarding when changing MSTI VLAN mappings;
*) bridge - fixed possible memory leak when using MSTP;
*) bridge - improved packet processing when bridge port changes states;
*) bridge - properly forward unicast DHCP messages when using DHCP Snooping with hardware offloading;
*) cloud - improved DDNS service disabling;
*) dhcp - properly load DHCP configuration if options are configured;
*) dhcpv6-server - recreate DHCPv6 server binding if it is no longer within prefix pool when rebinding/renewing;
*) ethernet - fixed IPv6 packet forwarding on IPQ4018 devices;
*) ike2 - improved subsequent phase 2 initialization when no childs exist;
*) ipsec - added account log message when user is successfully authenticated;
*) ipsec - allow multiple peers to the same address with different local-address (introduced in v6.43);
*) ipsec - fixed stability issues after changing peer configuration (introduced in v6.43);
*) ipsec - improved invalid policy handling when a valid policy is uninstalled;
*) kidcontrol - added "reset-counters" command for "device" menu (CLI only);
*) kidcontrol - added "tur-fri", "tur-mon", "tur-sat", "tur-sun", "tur-thu", "tur-tue", "tur-wed" parameters (CLI only);
*) kidcontrol - dynamically discover devices from DNS activity;
*) kidcontrol - fixed validation checks for time intervals;
*) led - added "dark-mode" functionality for wsAP ac lite, RB951Ui-2nD, hAP and hAP ac lite devices;
*) lte - added additional ID support for Novatel USB730L modem;
*) lte - added "cell-monitor" command for R11e-LTE international modem (CLI only);
*) lte - added support for JioFi JMR1040 modem;
*) ntp - fixed possible NTP server stuck in "started" state;
*) rb3011 - implemented multiple engine IPsec hardware acceleration support;
*) romon - improved packet processing when MTU in path is lower than 1500;
*) snmp - fixed w60g station table;
*) snmp - report bridge ifSpeed as "0";
*) ssh - fixed single command execution (introduced in v6.44beta9);
*) traffic-flow - fixed post NAT port reporting;
*) w60g - added interface stats;
*) w60g - renamed "mcs" to "tx-mcs" and "phy-rate" to "tx-phy-rate";
*) wireless - improved stability for 802.11ac;

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.

Tue Oct 02, 2018 4:33 pm

*) rb3011 - implemented multiple engine IPsec hardware acceleration support;

Thank you for finally getting the RB3011 IPSEC engine working, and for getting all crypto blocks operating. This breathes new life into this product for me.

anuser · Tue Oct 02, 2018 11:05 pm

Version 6.44beta14 has been released.
*) wireless - improved stability for 802.11ac;

Hello, semester is starting, soon. So I´m asking myself what problems will our users will face without this patch? What stability problems exist? It would be great to have this in 6.43.3 aswell.
(Talking about wireless, could we please get a simple "reboot" button within capsman, so after a reboot a cap will connect to its master capsman controller(as it is saved on the cap itself)? I know wrong thread)

honzam · Wed Oct 03, 2018 8:49 pm

*) wireless - improved stability for 802.11ac;

Any description of improve? Thanks

server8 · Thu Oct 04, 2018 10:34 am

*) wireless - improved stability for 802.11ac;
Any description of improve? Thanks

+1

mistry7 · Thu Oct 04, 2018 11:53 am

Still no Support for QCA9984/9994 and QCA9888 hopefully we see support not only for ARM (RB4011)
It would be an option to use this Wave2 Modules on M11G (MMips)

emils · Fri Oct 05, 2018 2:51 pm

Version 6.44beta17 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.44beta17 (2018-Oct-04 09:42):

MAJOR CHANGES IN v6.44:
----------------------
!) cloud - added command "/system backup cloud" for backup storing on cloud (CLI only);
!) upgrade - release channels renamed - "bugfix" to "long-term", "current" to "stable" and "release candidate" to "testing";
!) upgrade - "testing" release channel now can contain "beta" together with "release-candidate" versions;
----------------------

Changes in this release:

*) bridge - fixed possible memory leak when VLAN filtering is used;
*) dhcpv4-server - use client MAC address for dual stack queue when "client-id" is not received;
*) ethernet - fixed IPv6 packet forwarding on IPQ4018 devices;
*) health - improved fan control stability on CRS328-24P-4S+RM;
*) led - fixed default LED configuration for SXT LTE kit devices;
*) led - fixed power LED turning on after reboot when "dark-mode" is used;
*) lte - added "firmware-upgrade" command for R11e-LTE international modems (CLI only);
*) wireless - improved signal strength at low TX power on LHG 5 ac, LHG 5 ac XL and LDF 5 ac ("/system routerboard upgrade" required);

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.

emils · Fri Oct 05, 2018 3:01 pm

A bug in v6.44beta17 prevents SFP+ interfaces from linking properly on CRS328-24P-4S+RM. We will resolve the issue in the next beta version. Please upgrade with caution.

Fri Oct 05, 2018 4:05 pm

*) wireless - improved stability for 802.11ac;
Any description of improve? Thanks

This fix should provide better rate selection at higher rates and at higher load.

rogerkri · Fri Oct 05, 2018 5:12 pm

*) wireless - improved signal strength at low TX power on LHG 5 ac, LHG 5 ac XL and LDF 5 ac ("/system routerboard upgrade" required);

Will this be fixed for the RB922UAGS-5HPacD as well?

soomanyquestions · Sat Oct 06, 2018 1:38 am

Hi,

I'm getting the following on my devices after upgrading to beta17.

This eventually leads to the routers management interfaces to be unresponsive. For example you can run /ip route print via ssh and it will just hang forever and wont output anything. Same with winbox if you open interfaces menu or ppp menu the lists are just empty. Also it seems that you can not connect to the wireless network of the device when this happens.
I do have a snmp server that periodically queries the routers. I have tested this on a mAp, hAP ac lite and a rb2011.

emils · Wed Oct 10, 2018 3:44 pm

Version 6.44beta20 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.44beta20 (2018-Oct-09 09:29):

MAJOR CHANGES IN v6.44:
----------------------
!) cloud - added command "/system backup cloud" for backup storing on cloud (CLI only);
!) upgrade - release channels renamed - "bugfix" to "long-term", "current" to "stable" and "release candidate" to "testing";
!) upgrade - "testing" release channel now can contain "beta" together with "release-candidate" versions;
----------------------

Changes in this release:

*) crs328 - fixed SFP+ interface linking on CRS328-24P-4S+RM (introduced in v6.44beta17);
*) crs328 - improved link status update on disabled SFP+ interface when using DAC;
*) crs3xx - properly read "eeprom" data after different module inserted in disabled interface;
*) dhcp - added "allow-dual-stack-queue" setting for IPv4/IPv6 DHCP servers to control dynamic lease/binding behaviour (CLI only);
*) dhcpv6-server - improved DHCPv6 server stability when using "print" command;
*) led - added "dark-mode" functionality for LHG and LDF series devices;
*) lte - added "firmware-upgrade" command for R11e-LTE international modems (CLI only);
*) lte - fixed connection issue when LTE modem was de-registered from network for more than 1 minute;
*) w60g - general stability and performance improvements;
*) w60g - improved stability for short distance links;

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.

eworm · Wed Oct 10, 2018 4:13 pm

The fetch command behaves wired...

[admin@MikroTik] > :put ([ /tool fetch https://www.eworm.de/ip/index.shtml output=user as-value ]->"data")
91.16.17.160
[admin@MikroTik] > /file print where name="index.shtml"
 # NAME                     TYPE                    SIZE CREATION-TIME
 0 index.shtml              .shtml file                0 oct/10/2018 15:07:50

It does put empty files in storage where it should not. Fetching from urls ending with a slash is not possible at all, unless you give "dst-path=".

TerminalAddict · Thu Oct 11, 2018 2:51 am

@Cha0s: What I currently use is a little old and messy (php + svn). Long-term plan is to write something nicer and share it here in the forum too, but it might take a while. But bare bones version can be:
Code: Select all
for /F "tokens=*" %%A in (hosts.txt) do plink -ssh -i backup.ppk backup@%%A /export | grep "^[^#]" > %%A.rsc
git add *.rsc
git commit -m "automated backup"
File backup.ppk is PuTTY's private key and hosts.txt is text file with list of addresses or hostnames. Grep strips comments, to only record real changes. On router there's backup user (with ssh key):
Code: Select all
/user group
add name=backup policy=ssh,read,sensitive,!local,!telnet,!ftp,!reboot,!write,!policy,!test,!winbox,!password,!web,!sniff,!api
/user
add group=backup name=backup
And that's it, just run it as often as needed, from scheduler or manually. There's a lot of room for improvements (logging, notifications on failure, ...), but even this is usable as quick'n'dirty solution. Or it could be done in reverse, with routers uploading their config to some central server and a script there could handle the rest. Now if only the export exported everything...

I've just finished writing something to automate git commit backups
https://www.paulwillard.nz/snippet.php? ... ackup.html

I don't trim the comments as they might be there for a reason

emils · Thu Oct 11, 2018 2:20 pm

Thanks, eworm, both issues will be fixed in the next beta version.

soomanyquestions · Thu Oct 11, 2018 3:11 pm

Hi,

I'm getting the following on my devices after upgrading to beta17.

This eventually leads to the routers management interfaces to be unresponsive. For example you can run /ip route print via ssh and it will just hang forever and wont output anything. Same with winbox if you open interfaces menu or ppp menu the lists are just empty. Also it seems that you can not connect to the wireless network of the device when this happens.
I do have a snmp server that periodically queries the routers. I have tested this on a mAp, hAP ac lite and a rb2011.

I updated to 6.44beta20 and this is still happening.

nescafe2002 · Thu Oct 11, 2018 3:22 pm

I updated to 6.44beta20 and this is still happening.

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.

schrotn · Fri Oct 12, 2018 6:32 am

I think I'm running into a config bug in 6.44 Beta 20

I've upgraded my testing router and saw the L2TP/IPSec unsafe config notice. So I was playing around with configs to fix that.

Once the L2TP peer is initially added, any attempt to edit the peer config errors out with "Couldn't change IPSec Peer <::/0> - certificate chain is supported only in IKEv2 (6)"
This seems to affect both manually and dynamically added peers.

Any truly valid peer config commits successfully when initially configured, but any attempt to change them results in the same error.

Also, since Mikrotik is warning against L2TP/IPSec PSK, is there any plans to expand the L2TP setup in PPP to be more secure?

docmarius · Fri Oct 12, 2018 9:16 am

What are you talking about? What are USB U3 programs? Please stop posting such posts.

U3 is a portable execution medium developed some years ago, and pushed by Sandisk.
It allows the installation of a PE (Portable executable) on an USB stick which creates an automatic launch environment in Windows, so that those specific installed programs can be transferred completely, including their run environment to another machine, just by inserting the USB device in the other machine, without the need to install them on each machine.

https://en.wikipedia.org/wiki/U3_%28software%29

So Chris is really talking about a real thing, which actually works. The fact that not everybody has heard about it doesn't makes it idiotic by default.
Putty is one of the applications which has a PE variant available for download. So maybe you should refrain from characterizing posts without doing a basic google search first.

BTW, Winbox could also be such a candidate, if it would drop the saving of the login data in the users home folder in favor of a local folder access...

Fri Oct 12, 2018 10:26 am

Docmarius .. thank you for explanation but what USB U3 has common with ROS? What does he want to beta test with U3?

docmarius · Fri Oct 12, 2018 6:08 pm

Yes, you are right. It has nothing to do with ROS. As Sob said, it's probably a preparation for later actions. Sorry for the bump in.
But an actual PE release for Winbox could be a nice step

pakud · Sat Oct 13, 2018 10:07 pm

the recent betas [ eg 6.44beta20 ] allow for upgrade of the lte card's firmware in RBwAPR-2nD&R11e-LTE, yet it's not possible in the RBwAPR-2nD&R11e-LTE-US

do you plan for allowing lte firmware upgrade on the US version?

thanks!

raffav · Sat Oct 13, 2018 11:22 pm

Test on the current/stable channel
I was also trying to do that without success.

I think I'm running into a config bug in 6.44 Beta 20

I've upgraded my testing router and saw the L2TP/IPSec unsafe config notice. So I was playing around with configs to fix that.

Once the L2TP peer is initially added, any attempt to edit the peer config errors out with "Couldn't change IPSec Peer <::/0> - certificate chain is supported only in IKEv2 (6)"
This seems to affect both manually and dynamically added peers.

Any truly valid peer config commits successfully when initially configured, but any attempt to change them results in the same error.

Also, since Mikrotik is warning against L2TP/IPSec PSK, is there any plans to expand the L2TP setup in PPP to be more secure?

Sent from my XT1580 using Tapatalk

notToNew · Sun Oct 14, 2018 4:03 am

the recent betas [ eg 6.44beta20 ] allow for upgrade of the lte card's firmware in RBwAPR-2nD&R11e-LTE,

Is 008 still the current firmware?

pakud · Sun Oct 14, 2018 9:05 am

the recent betas [ eg 6.44beta20 ] allow for upgrade of the lte card's firmware in RBwAPR-2nD&R11e-LTE,
Is 008 still the current firmware?

after an upgrade on RBwAPR-2nD&R11e-LTE /interface lte info lte1 shows "MikroTik_CP_2.160.000_v008", while RBwAPR-2nD&R11e-LTE-US - MPSS: R11eL_v12.09.171931 APSS: R11eL_v02.14.173531 CUSTAPP

running /interface lte firmware-upgrade upgrade=y lte1 on the US device gives: failure: Device does not support this feature!

mkx · Sun Oct 14, 2018 10:42 am

Change log for this beta clearly states that R11e firmware upgrade is available only for international version of devices .... can't you read?

pakud · Sun Oct 14, 2018 7:06 pm

Change log for this beta clearly states that R11e firmware upgrade is available only for international version of devices .... can't you read?

actually i can - that's why i stated my question: do you plan for allowing lte firmware upgrade on the US version?

mkx · Sun Oct 14, 2018 10:16 pm

Change log for this beta clearly states that R11e firmware upgrade is available only for international version of devices .... can't you read?
actually i can - that's why i stated my question: do you plan for allowing lte firmware upgrade on the US version?

Sorry, didn't see the question in your previous post.

schrotn · Mon Oct 15, 2018 6:52 am

I previously had 6.44 b(~6 or 8, can't recall) and it didn't warn about either l2tp/ipsec psk nor ipsec certificates.
I'm fairly certain it's a recent addition to the testing channel only.

Test on the current/stable channel
I was also trying to do that without success.

Sent from my XT1580 using Tapatalk

fredcom · Mon Oct 15, 2018 10:53 am

Hey guys,

I have a sort of offtopic question, but since we have the ability to upgrade the firmware now - where does one get the new firmware for R11e-LTE?

juliokato · Mon Oct 15, 2018 2:46 pm

Use the new board:
https://mikrotik.com/product/r11e_4g

raffav · Mon Oct 15, 2018 3:44 pm

I previously had 6.44 b(~6 or 8, can't recall) and it didn't warn about either l2tp/ipsec psk nor ipsec certificates.
I'm fairly certain it's a recent addition to the testing channel only.

Test on the current/stable channel
I was also trying to do that without success.

Sent from my XT1580 using Tapatalk

On the 43rc was also get the sames errors
I sent a email to support they told me that I had to use the cli for that. maybe they still doesn't have fixed yet.

Sent from my XT1580 using Tapatalk

fredcom · Mon Oct 15, 2018 10:09 pm

Use the new board:
https://mikrotik.com/product/r11e_4g

Thanks for heads up. I think I will eventually end up with this new board, as it seems I've became addicted to Mikrotik tech

But anyway, no one has knowledge on where to get new firmware?

netispguy · Tue Oct 16, 2018 12:12 am

I really hope that the new iPhone Xs/XsMax 5GHz AC problem is resolved before the 6.44 production release.

viewtopic.php?f=7&t=139608&sid=c8121250 ... cae5c96b71

Tue Oct 16, 2018 11:00 am

I really hope that the new iPhone Xs/XsMax 5GHz AC problem is resolved before the 6.44 production release.

viewtopic.php?f=7&t=139608&sid=c8121250 ... cae5c96b71

Reading through the topic you've linked to makes me think it is an iPhone's problem, not Mikrotik's one.

netispguy · Tue Oct 16, 2018 2:14 pm

I really hope that the new iPhone Xs/XsMax 5GHz AC problem is resolved before the 6.44 production release.

viewtopic.php?f=7&t=139608&sid=c8121250 ... cae5c96b71

Reading through the topic you've linked to makes me think it is an iPhone's problem, not Mikrotik's one.

Hmm... I respectfully disagree that reading the topic leads to your assumption; however, I am also willing to believe this is an Apple problem.

The problem is that we (and other reports) have confirmed that the new Apple Xs devices appear to be working without any problem across a broad spectrum of Wi-Fi ecosystems. This includes commercial environments (such as Ubiquiti and Cisco), consumer environments (such as NetGear, Linksys, Google, ASUS etc.) and whatever Comcast and Xfinity are using for their deployments. Maybe these platforms are having issues (although unnoticeable), but the problem we are seeing on the Mikrotik framework is extremely severe.

I personally went out and purchased an iPhone XsMax to see for myself. I travel a lot and move through a large number of wifi environments and can confirm that I saw the problem at our office in Silicon Valley (as reported by my users) and at my home (which is fully Mikrotik). I did NOT see any issue whatsoever last week connecting to wifi at SFO, for 6 hours connected to Gogo on a United flight to Boston, at a Marriott hotel or at a coffee shop. Once I walked into my Boston office (Mikrotik), I immediately saw the problem return...

If this is an Apple problem, it appears to be impacting our Mikrotik frameworks more than others...

kalamaja · Tue Oct 16, 2018 2:20 pm

I really hope that the new iPhone Xs/XsMax 5GHz AC problem is resolved before the 6.44 production release.

viewtopic.php?f=7&t=139608&sid=c8121250 ... cae5c96b71
Reading through the topic you've linked to makes me think it is an iPhone's problem, not Mikrotik's one.

From iOS 12.0.1 release notes:
Resolves an issue that could cause iPhone XS devices to rejoin a Wi-Fi network at 2.4GHz instead of 5GHz

netispguy · Tue Oct 16, 2018 2:48 pm

I really hope that the new iPhone Xs/XsMax 5GHz AC problem is resolved before the 6.44 production release.

viewtopic.php?f=7&t=139608&sid=c8121250 ... cae5c96b71
Reading through the topic you've linked to makes me think it is an iPhone's problem, not Mikrotik's one.
From iOS 12.0.1 release notes:
Resolves an issue that could cause iPhone XS devices to rejoin a Wi-Fi network at 2.4GHz instead of 5GHz

12.0.1 does not resolve what we are seeing. I can confirm it did fix the issue you mentioned above when both 2.4GHz and 5GHz radios are broadcasting the same SSID, and was impacting all environments. The issue I am discussing makes these new iPhones almost totally dysfunctional within the Mikrotik framework using any 5GHz AC 80MHz XXXX channel width. If you configure your radio to 5GHz A/N 40MHz XX, the problem goes away. It's an "AC" issue...different problem than what was fixed in 12.0.1

kramer · Wed Oct 17, 2018 6:57 pm

Hi,

In the beginning just to say I'm not IT pro when comes to Mikrotik. However on beta soft I did create ipv6 tunnel from HE - it working fine on my CCR 1009. I can ping outside ipv6 addr without problem.
But what I cannot ping Miktrotik ipv6 addres from LAN, same subnet, same VLAN. Maybe someone have similar issue ?

Brgds
D

pe1chl · Wed Oct 17, 2018 8:37 pm

But what I cannot ping Miktrotik ipv6 addres from LAN, same subnet, same VLAN. Maybe someone have similar issue ?

Please do not use the release topic for other things than reporting issues with the release.
Make a new topic in the General or Beginners section describing your issue and include a /export of your configuration (no screenshots!).

kramer · Wed Oct 17, 2018 10:25 pm

But what I cannot ping Miktrotik ipv6 addres from LAN, same subnet, same VLAN. Maybe someone have similar issue ?
Please do not use the release topic for other things than reporting issues with the release.
Make a new topic in the General or Beginners section describing your issue and include a /export of your configuration (no screenshots!).

sorry... I fixed this by using Router/48: from HE instead /64:

emils · Mon Oct 29, 2018 11:31 am

Version 6.44beta28 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.44beta28 (2018-Oct-29 07:58):

MAJOR CHANGES IN v6.44:
----------------------
!) cloud - added command "/system backup cloud" for backup storing on cloud (CLI only);
!) upgrade - release channels renamed - "bugfix" to "long-term", "current" to "stable" and "release candidate" to "testing";
!) upgrade - "testing" release channel now can contain "beta" together with "release-candidate" versions;
----------------------

Changes in this release:

!) radius - initial implementation of RadSec (Radius communication over TLS);
*) bridge - added option to monitor fast-forward status;
*) bridge - disable fast-forward when using SlowPath features;
*) bridge - fixed DHCP Option 82 parsing when using DHCP Snooping;
*) certificate - fixed time zone adjustment for SCEP requests;
*) crs328 - fixed SFP+ interface linking on CRS328-24P-4S+RM (introduced in v6.44beta17);
*) crs328 - fixed SFP ports not reporting auto-negotiation status;
*) crs328 - improved link status update on disabled SFP and SFP+ interfaces;
*) defconf - automatically accept default configuration if reset done by holding button;
*) defconf - fixed configuration not generating properly on upgrade;
*) ethernet - fixed linking issues on wAP ac, RB750Gr2 and Metal 52 ac (introduced in v6.43rc52);
*) fetch - fixed fetching with "as-value" creating an empty file (introduced in v6.44beta20);
*) fetch - fixed "without-paging" option;
*) health - fixed bad voltage readings on RB493G;
*) ike2 - added option to specify certificate chain;
*) ike2 - send split networks over DHCP (option 249) to Windows initiators if DHCP Inform is received;
*) ike2 - show weak pre-shared-key warning;
*) ipsec - added basic pre-shared-key strength checks;
*) ipsec - fixed hw-aead (H) flag presence under Installed SAs on startup;
*) ipsec - improved stability when uninstalling multiple SAs at once;
*) ipsec - made peers autosort themselves based on reachability status;
*) ipsec - properly update warnings under peer menu;
*) lte - added support for JioFi JMR1040 modem;
*) lte - fixed IPv6 activation for R11e-LTE-US modems;
*) lte - fixed LTE interface not working properly after reboot on RBSXTLTE3-7;
*) lte - fixed missing running (R) flag for Jaton LTE modems;
*) ospf - improved stability while handling type-5 LSAs;
*) port - improved "remote-serial" TCP performance in RAW mode;
*) rb3011 - implemented multiple engine IPsec hardware acceleration support;
*) rbm33g - improved stability when used with some USB devices;
*) routerboard - require at least 10 second interval between "reformat-hold-button" and "max-reformat-hold-button";
*) routerboard - show "boot-os" and "force-backup-booter" option only on devices that have such feature;
*) snmp - added "dot1qPortVlanTable" and "dot1dBasePortTable" OIDs;
*) ssh - added error log message when key exchange fails;
*) ssh - fixed non-interactive shell not returning all output (introduced in v6.44);
*) tr069-client - fixed HTTP cookie getting duplicated with the same key;
*) tunnel - made "ipsec-secret" parameter sensitive;
*) upgrade - made security package depend on DHCP package;
*) wireless - removed G/N support for 2484MHz in "japan" regulatory domain;
*) w60g - fixed scan in bridge mode;
*) w60g - improved PtMP performance;
*) w60g - renamed "frequency-list" to "scan-list";
*) w60g - renamed disconnection message when license level did not allow more connected clients;
*) w60g - added align mode "/interface w60g align" (CLI only);

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.

eworm · Mon Oct 29, 2018 1:30 pm

Starting with 6.44beta28 the security package requires the dhcp package to be installed? I think that is something to be noted in changelog. What's the reason?

emils · Mon Oct 29, 2018 2:11 pm

Nice catch. It is because of the new IKEv2 feature which works with DHCP. I will update the changelog.

huntah · Mon Oct 29, 2018 4:33 pm

ike2 - send split networks over DHCP (option 249) to Windows initiators if DHCP Inform is received;

Any Examples?

If I am not mistanken this means that split tunneling will now work!

emils · Mon Oct 29, 2018 4:48 pm

There is no special configuration needed. RouterOS will automatically convert split-network parameter to use with DHCP option.

huntah · Mon Oct 29, 2018 8:25 pm

I just installed beta28 on brand new HapLite (default Settings).
added Certificates and ipsec ike2 RSA setup:

/certificate
add common-name=TESTCA name=TESTCA days-valid=3650
sign TESTCA ca-crl-host=192.168.3.124
add common-name=192.168.3.124 subject-alt-name=DNS:192.168.3.124 key-usage=tls-server name=TestVPN days-valid=3600
sign TestVPN ca=TESTCA
add common-name=hunter key-usage=tls-client name=hunter days-valid=3600
sign hunter ca=TESTCA

/ip pool
add name=VPN-Pool ranges=192.168.222.100-192.168.222.150

/ip ipsec mode-config
add address-pool=VPN-Pool address-prefix-length=32 name=RW-cfg split-include=192.168.88.0/24
/ip ipsec peer profile
set [ find default=yes ] enc-algorithm=aes-128
/ip ipsec policy group
add name=RoadWarrior
/ip ipsec proposal
set [ find default=yes ] enc-algorithms=aes-256-cbc,aes-128-cbc
add auth-algorithms=sha256,sha1 enc-algorithms=aes-256-cbc,aes-128-cbc name=proposal1 pfs-group=none
/ip ipsec peer
add auth-method=rsa-signature certificate=TestVPN exchange-mode=ike2 generate-policy=port-strict mode-config=RW-cfg passive=yes policy-template-group=RoadWarrior
/ip ipsec policy
add comment=IKEv2 dst-address=192.168.222.0/24 group=RoadWarrior proposal=proposal1 src-address=0.0.0.0/0 template=yes

Win10 client connects OK but split-include does not work. The Win10 1803 client does not get routes..
Also tried address-prefix-length=24.. still noting.

In log I can see mikrotik detect Windows Machine but split-include is not pushed to the client..
I have attached the ipsec debug log. Connect and disconnect from win10 test machine

@emils: Am I doing something wrong? Please advise.. thx

sindy · Mon Oct 29, 2018 9:32 pm

I'm not Emils, however can you try to run packet sniffer before clicking "connect" on the Windows machine with the following settings (assuming that etherX is the name of the interface through which it connects)?

/tool sniffer set only-headers=no memory-limit=100 memory-scroll=yes file-name="" file-limit=8000 streaming-enabled=no filter-stream=no filter-interface=etherX filter-mac-address="" filter-mac-protocol="" filter-ip-address="" filter-ipv6-address="" filter-ip-protocol=udp filter-port=53 filter-cpu="" filter-direction=any filter-operator-between-entries=and

Then, do the following:

/tool sniffer start
/tool sniffer packet print interval=1s

And then start the client on Windows.

If you see a packet in the list, chances are high that it is the DHCPINFORM which is needed for the feature to work; however, another necessary condition may be to have more than one split-subnet, as one destination subnet is normally a mandatory part of the mode-config so there is no point in sending it using DHCP.

huntah · Mon Oct 29, 2018 11:03 pm

I tried with ether1 (my wan on test router)
but nothing is catcing in the sniffer when I connect or disconnect.
I dont really understand what DNS (udp/53) has to do with DHCP (udp/67-68)
If I change it to correct ports I get:

0   14.46 ether1                         192.168.222.146:68 (bootpc)                                 255.255.255.255:67 (bootps)                                 udp           342   0 no 
 1  19.212 ether1                         192.168.222.146:68 (bootpc)                                 255.255.255.255:67 (bootps)                                 udp           342   0 no 
 2   24.21 ether1                         192.168.222.146:68 (bootpc)                                 255.255.255.255:67 (bootps)                                 udp           342   0 no

I have also tried multiple subnets in split-include.. With no luck.

If I set user remote gateway on Win10 Client VPN connecton works.. But for all networks (split-include set 0.0.0.0/0, havent tried with includes...).

sindy · Mon Oct 29, 2018 11:16 pm

I dont really understand what DNS (udp/53) has to do with DHCP (udp/67-68)

I'm a bit sleepy so I've mixed them up, that's all. Good you've found out yourself.

Now if 192.168.222.146 is the address from the /ip pool assigned to /ip ipsec mode-config, so it is the one assigned to the Win PC using mode-config, you can double-check that it is a DHCPINFORM packet by sniffing into file and opening the file using Wireshark (update: just checked it myself on a W2012 system connected to 6.43.2, so yes, it is a DHCPINFORM)

So until Emils comes tomorrow, I'd try to attach a DHCP server to ether1, and that's my last idea given that he's already stated that the ipsec plant itself takes care about converting the split-include data into Option 249.

huntah · Mon Oct 29, 2018 11:51 pm

I dont get any DHCPInform..
Attached is the wireshark and then connect to VPN..
I cant put DHCP Server on WAN port ...

guess we will wait for Mktik guys to wake up

Night all and thnx for tips and help sindy!

sindy · Tue Oct 30, 2018 12:02 am

You most likely do get the DHCPINFORM

But to see it, you cannot capture on the PC as you did, you have to use /tool sniffer on Mikrotik and set file-name=something.pcap. When you capture on the PC, the DHCPINFORM is only seen there encrypted in the ESP so you cannot recognize it. The Mikrotik sniffer shows you both the IPsec transport packets (ESP in this case) and the plaintext packets extracted from them. This is not true in the opposite direction, i.e. you cannot see plaintext packets before they got encrypted on the same interface through which they are sent out encrypted.

huntah · Tue Oct 30, 2018 12:45 am

OK my bad

Here is the Wireshark capture from Mikrotik..
There are DHCP Inform messages but I am not able to interpret them :/

emils · Tue Oct 30, 2018 9:04 am

That is interesting. Are there really no other logs in ipsec topic after the IPsec-SA has been established? From what I can tell, DHCP inform is received on the router, but IPsec does not see the packet. What other configuration do you have on the router? Is there a DHCP server or client configured? Do you see any logs in dhcp topic when establishing the tunnel?

huntah · Tue Oct 30, 2018 9:46 am

I have default configuration (eth1 -> DHCLient to my private network)
All drop rules disabled
DHCPServer on Bridge (Default with IP pool 192.168.88.0)
VPN Pool is 192.168.222.0/24
I have attached the full config export compact

emils · Tue Oct 30, 2018 10:39 am

Weird, it works for me with exact your configuration and 1803 (Pro). Did you change any of the advanced ipv4 configuration on Windows side except for disabling EAP authentication? Note that it might take a few seconds for routes to be installed. How are you checking the route presence? Can you do 'route print -4' in cmd.exe? If that does not yield any results, please enable IPsec debug logs (topics=ipsec) and generate a supout.rif file after a few seconds when connection is established and send it to support@mikrotik.com.

huntah · Tue Oct 30, 2018 11:24 am

I check exactly like that..
but there arent any routes from split-include..

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.3.1    192.168.3.122     55
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    331
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    331
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    331
      192.168.3.0    255.255.255.0         On-link     192.168.3.122    311
    192.168.3.122  255.255.255.255         On-link     192.168.3.122    311
    192.168.3.124  255.255.255.255         On-link     192.168.3.122     56
    192.168.3.255  255.255.255.255         On-link     192.168.3.122    311
    192.168.222.0    255.255.255.0         On-link   192.168.222.148     46
  192.168.222.148  255.255.255.255         On-link   192.168.222.148    301
  192.168.222.255  255.255.255.255         On-link   192.168.222.148    301
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    331
        224.0.0.0        240.0.0.0         On-link     192.168.3.122    311
        224.0.0.0        240.0.0.0         On-link   192.168.222.148    301
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    331
  255.255.255.255  255.255.255.255         On-link     192.168.3.122    311
  255.255.255.255  255.255.255.255         On-link   192.168.222.148    301
===========================================================================

Suppout.rif sent to support..
If anyone else can try it would be super..
Maybe just my Win10 machine wont work as it should

I will test in the eventing with another..

msatter · Tue Oct 30, 2018 1:16 pm

Why can't device-specific stuff like MAC-addresses simply be removed from the backup files?

Because it is whole system backup.

Proposal: choice, to omit not on backup but on restore. So you will have allways a full backup and can select on restore if certain values should not be restored.

Workings could be, enter the password if needed, that you can selected direct restore or making a selection containing options, which by omitting them not lead to bricking the device.

After deselecting data not to be restored a new backup file is written (with a different name), not containing the omitted data. This file is used for the restore and deleted after restoring, so one time usage.

The original full backup file will be untouched.

Chupaka · Tue Oct 30, 2018 1:48 pm

Proposal: choice, to omit not on backup but on restore. So you will have allways a full backup and can select on restore if certain values should not be restored.

Let's imagine the internals of this restoration process. There's a database table with the list of interfaces, their parameters, their MAC addresses, etc. Now you restore it from backup leaving MAC address fields empty (?). So there's no connection between entries in the table and real interfaces. Configuration is in inconsistent state.

Don't think about backup like about an /export file. It's a bit different and more low-level thing.

5nik · Tue Oct 30, 2018 1:49 pm

*) ike2 - send split networks over DHCP (option 249) to Windows initiators if DHCP Inform is received;

It will be greate to add this feature for PPP tunels too (SSTP, L2TP). Now I'm using forwarding DHCP Info packets to external DHCP server for DHCP option 249 (and another DHCP options for Windows clients).

msatter · Tue Oct 30, 2018 5:36 pm

Proposal: choice, to omit not on backup but on restore. So you will have allways a full backup and can select on restore if certain values should not be restored.
Let's imagine the internals of this restoration process. There's a database table with the list of interfaces, their parameters, their MAC addresses, etc. Now you restore it from backup leaving MAC address fields empty (?). So there's no connection between entries in the table and real interfaces. Configuration is in inconsistent state.

Don't think about backup like about an /export file. It's a bit different and more low-level thing.

Then maybe a RSC script that does manual work after a restore. I can Reset MAC on a interface so I get the MAC of the restored to device and not the MAC from the backup.

Changing the tables that use MAC is something you always have to do when use the hard MAC's of a different device.

huntah · Tue Oct 30, 2018 7:19 pm

HI,

ike2 - send split networks over DHCP (option 249) to Windows initiators if DHCP Inform is received;

just got word back from support. They have found the problem with split-include and it will be fixes in next beta..
Will test then again and post back the results!

ksteink · Tue Oct 30, 2018 7:22 pm

I want to see HW Off-load enabled in all bridge interfaces, not just one. Specially knowing that you need 1 Bridge per VLAN having this limitation is a killer as I will limit the traffic throughput without unable to get wired speed only in just 1 VLAN. Really?? Seriously??

xvo · Tue Oct 30, 2018 7:36 pm

I want to see HW Off-load enabled in all bridge interfaces, not just one. Specially knowing that you need 1 Bridge per VLAN having this limitation is a killer as I will limit the traffic throughput without unable to get wired speed only in just 1 VLAN. Really?? Seriously??

After implementing vlan-aware bridges with hw-offload you no longer need 1 bridge per vlan.

pe1chl · Tue Oct 30, 2018 8:15 pm

After implementing vlan-aware bridges with hw-offload you no longer need 1 bridge per vlan.

But with VLAN-aware bridges you have no hw-offload at all!

xvo · Tue Oct 30, 2018 8:51 pm

After implementing vlan-aware bridges with hw-offload you no longer need 1 bridge per vlan.
But with VLAN-aware bridges you have no hw-offload at all!

The config mentioned above - with multiple bridges - was always purely software, and it was the only way for devices without switch chip.
No point to think of it in any other way.

But now, devices without switch chip can do it in much easier way.
Some switches can even do it both easy and in hardware.
And all others - still can do it in the switch menu, just like before.

Anyway, all this is completely unrelated to this ROS version.

dgrififth · Wed Oct 31, 2018 1:08 am

*) ethernet - fixed linking issues on wAP ac, RB750Gr2 and Metal 52 ac (introduced in v6.43rc52);

So what was the bug here? I have a bunch of RB750Gr2 units on 6.43.2 that sometimes lose traffic on ethernet ports until the port is cycled on/off. Link remains up, and it *appears* that data is sent out the port (although maybe it is just presented to the port hardware by ROS and the hardware fails to send it), just nothing comes back in.

Disable/enable the link, all works again for 5-15 minutes. Turning on "Proxy-arp" for that ethernet interface appears to fix it or at least make it work for hours instead of minutes, although there is no reason to have proxy-arp.

pe1chl · Wed Oct 31, 2018 11:20 am

Turning on "Proxy-arp" for that ethernet interface appears to fix it or at least make it work for hours instead of minutes, although there is no reason to have proxy-arp.

That depends. It can be a bug in your client device too. E.g. Ubiquiti access points sometimes lose the default route (or it becomes ineffective) and then you need tricks
like proxy-arp or SNAT to still access the management interface of the device from the network (while it continues to bridge traffic between the routers).
Reboot of the Ubiquiti fixes that, for a few weeks or months. Then it randomly returns.

dgrififth · Wed Oct 31, 2018 11:58 am

It can be a bug in your client device too.

Yeah I was hoping that proxy arp would have a slightly different processing path, and it appears to work. It's a WinCE end device (that is, no routing, just a single IP address) that appeared to work ok with 6.39 across 15 or so units, so I'll probably revert to that and see if it makes a difference. But I've been trawling the changelogs looking for recent ROS ethernet changes, and this is the first one I've come across.

pe1chl · Wed Oct 31, 2018 2:12 pm

You could check the ARP table of the client to see if it has any strange entries (other IP addresses than the router, with the router's MAC address).
If so you need to debug the client.
I would not know a legitimate reason why proxy-arp would work and normal arp would not, when the client is correctly configured.
(correct subnet on the LAN interface and a default route via the router's IP address)

dgrififth · Thu Nov 01, 2018 3:49 am

I would not know a legitimate reason why proxy-arp would work and normal arp would not, when the client is correctly configured.

Hence why I suspect it's a bug in ROS.

They're remote clients running a full screen app on winCE, so it's difficult to debug. Disturbing the port in any way (eg unplug/re-plug, disable/enable in ROS) fixes the issue temporarily, other brands of switches don't present this problem to the device, etc, etc. It's the combo of Mikrotik Hex switch + this device that has the issue. Anyway, I've left a few units on proxy-arp and a few units running 6.42.9, so will observe for a while.

pe1chl · Thu Nov 01, 2018 10:30 am

While the device cannot communicate (I presume to an outside network, not internal to the LAN subnet), is it still possible to ping the device from the router (i.e. from within the same subnet)?
And is it possible to ping the device from outside and wake-up the stalled connection?

eworm · Fri Nov 02, 2018 10:20 am

Nice catch. It is because of the new IKEv2 feature which works with DHCP. I will update the changelog.

Will devices be able to handle that on its own? Or more important... Will CAPsMAN handle this for connected devices?

emils · Fri Nov 02, 2018 12:21 pm

Will devices be able to handle that on its own? Or more important... Will CAPsMAN handle this for connected devices?

We will see if we can remove the dependency, but most likely users with standalone packages will have to handle the upgrade process by themselves.

hknet · Fri Nov 02, 2018 9:29 pm

Hi
regarding the issue:

bridge - fixed packet forwarding when changing MSTI VLAN mappings

could someone from MT please elaborate?
we have been quite unsuccessfull integrating crs317 devices in our network using MSTP
the RSTP from other devices arriving on vlans is simply not being replicated to other memberports of the same VLAN (untagged/tagged).

please advise
hk

dgrififth · Sat Nov 03, 2018 11:13 pm

While the device cannot communicate (I presume to an outside network, not internal to the LAN subnet), is it still possible to ping the device from the router (i.e. from within the same subnet)?
And is it possible to ping the device from outside and wake-up the stalled connection?

Nope. Link to the device from the switch is reported as being up by both the device and the switch, but it's completely unpingable. Device can't connect to a server on the same subnet, server or any other IP on the subnet can't ping the device. ARP pings fail as well. Packet sniffing shows ping packets making it to the port that the device is connected to (according to ROS when I packet sniff on the port, anyway), but nothing from the device, not even normal idle packets (arps, windows networking packets,etc). Zero bytes / packets come from the port when the fault is present.

It's very mysterious.

pe1chl · Sat Nov 03, 2018 11:32 pm

It is a bit contradictory. When you say you see outgoing pings to the device, that is only possible when the device has answered ARP requests (so the router knows the device MAC address, if not you would see ARP requests to the device), but then you say that ARP pings fail.
When turning on proxy-arp fixes it it suggests that ARP is involved and maybe the device does not get answers on its ARP requests (to the router), but when changing something in the router fixes that, you would think that ARP requests *are* in fact sent by the device, but not answered by the router when not in proxy-arp mode.
That could happen e.g. when the requested address in the ARP does not match the address of the router, and this the ARP request is ignored, while it is answered in proxy-arp mode.
But in this case you still should see incoming ARP requests from the device whenever it does not answer pings.
(sometimes devices do not send them "in response to" the incoming packet that requires a reply, but send them at some fixed rate when the first one had not been answered)

I think you need to trace a bit longer to know for sure that really nothing comes in from the device, and especially look for malformed ARP requests.

DezsiIstvan · Sun Nov 04, 2018 9:26 pm

I test radsec (RFC 6614) radius connection.
It's works (connecting over SSL encrypted tcp connection to radius server)

I got the following request on our freeradius server
(1) Received Access-Request Id 23 from y.y.y.y:40627 to 0.0.0.0:2083 length 146
(1) Service-Type = Login-User
(1) User-Name = "username"
(1) MS-CHAP-Challenge = 0x...3e
(1) MS-CHAP2-Response = 0x...bc
(1) Calling-Station-Id = "x.x.x.x"
(1) NAS-Identifier = "AP-name"
(1) NAS-IP-Address = y.y.y.y

I have some problems,questions and future requests:

- for all authentication services (SSH/Winbox/HTTPS/API-SSL/...) we need Clear-Text password not MS-CHAP / MS-CHAP2 because on radius server passwords are hashed
THIS IS VERY IMPORTANT
radsec with mschap is useless

- for us be useful if we differentiate mikrotik auth service in "Service-Type" for example
for ssh put in Service-Type = ssh (like linux machines)
with this we can decide on radius server which user have access via which service
for example "john have access only via winbox, bob via ssh,winbox,https

- mikrotik radsec client how authenticate the server ?

Future requests I need to email to support ?

artz · Mon Nov 05, 2018 10:07 am

Hi
regarding the issue:

bridge - fixed packet forwarding when changing MSTI VLAN mappings

could someone from MT please elaborate?
we have been quite unsuccessfull integrating crs317 devices in our network using MSTP
the RSTP from other devices arriving on vlans is simply not being replicated to other memberports of the same VLAN (untagged/tagged).

please advise
hk

The bug affected all devices. Traffic stopped forwarding when you started to change MSTI VLAN mappings, but you could easily fix it by disabling it and re-enabling it.
MSTP is compatible with RSTP, this means that BPDUs should not be replicated anywhere, each device sends out its own BPDU.
It sounds a lot more like you have misconfigured device:
https://wiki.mikrotik.com/wiki/Manual:L ... _interface

mducharme · Tue Nov 06, 2018 6:04 pm

I see some complaining about MS-CHAPv2 support in Winbox. We like the MS-CHAPv2 support for Winbox because it allows us to no longer have to store the passwords unencrypted on the authentication server, so I hope it is retained in some way. We do not wish to go back to regular CHAP in our case.

Wed Nov 07, 2018 1:00 am

I see some complaining about MS-CHAPv2 support in Winbox. We like the MS-CHAPv2 support for Winbox because it allows us to no longer have to store the passwords unencrypted on the authentication server, so I hope it is retained in some way. We do not wish to go back to regular CHAP in our case.

Agreed

Security first!

mozerd · Wed Nov 07, 2018 1:45 pm

I see some complaining about MS-CHAPv2 support in Winbox. We like the MS-CHAPv2 support for Winbox because it allows us to no longer have to store the passwords unencrypted on the authentication server, so I hope it is retained in some way. We do not wish to go back to regular CHAP in our case.
Agreed

Security first!

ABSOLUTELY, security first.

DezsiIstvan · Wed Nov 07, 2018 2:39 pm

I see some complaining about MS-CHAPv2 support in Winbox. We like the MS-CHAPv2 support for Winbox because it allows us to no longer have to store the passwords unencrypted on the authentication server, so I hope it is retained in some way. We do not wish to go back to regular CHAP in our case.

MS-CHAPv2 need clear-text / decryptable password or MD4 hash of password on radius server side
this mean that in radius server we need to store clear text or decryptable password in database (very insecure, MD4 is also very insecure)
Storing clear-text or reversible password is not allowed. We store only a SHA512 hash of salt+password.
To authenticate a password we need it in clear-text to compute the hash and compare with stored hash

Using MS-CHAP(v2) in a TLS tunnel (radsec) is a nonsense because TLS is a safe encrypted transfer protocol and can be used to transfer password in clear-text like every webpage (https).
So:
1) radsec uses TLS like HTTPS and safe for clear-text password transfer.
2) clear-text password transfer is needed to authenticate against hashed password, stored on radius server

radsec + mschap mean double encrypt the password in tranzit with a secure (radsec) and an unsecure (ms chap v2) algorithm with the price of insecure password store on radius server
radsec + clear-text password mean encrypt the password in tranzit with a secure (radsec) algorithm and on password server passwords can be stored with any algorithm for example with the seucre SHA512

because security is first, is important to send the password in clear-text format to radius server over a secure TLS encrypted (radsec) way

this method is used by every https webpage (clear-text password over TLS)

Chupaka · Wed Nov 07, 2018 4:32 pm

Clear-text password over any channel is a source of MitM. In MS-CHAPv2 client has to prove he knows the password and also the server has to prove he knows the same password (two-way authentication)

JimmyNyholm · Thu Nov 08, 2018 4:17 am

All hash options is useless, Static passwords is insecure. I use OTP (One time Password) can't hash anything because there is nothing to hash on. Please reimplement PAP so I may once again be secure.

anuser · Wed Nov 14, 2018 10:24 am

Version 6.44beta9 has been released.
*) winbox - added 4th chain selection for "HT TX chains" and "HT RX chains" under "CAPsMAN/CAP Interface/Wireless" tab;

I cannot find that setting...

Chupaka · Wed Nov 14, 2018 11:30 am

I cannot find that setting...

honzam · Fri Nov 16, 2018 12:53 pm

No new beta?

Chupaka · Fri Nov 16, 2018 1:25 pm

No new beta?

Bettar beta? =)

Jotne · Fri Nov 16, 2018 4:23 pm

They are working with the new 7.xx, so be patient.

Chupaka · Fri Nov 16, 2018 4:48 pm

This topic is not the place where we're joking about v7

paulct · Fri Nov 16, 2018 4:59 pm

https://download.mikrotik.com/routeros/ ... beta01.npk

psannz · Fri Nov 16, 2018 5:09 pm

https://download.mikrotik.com/routeros/ ... beta01.npk

That was evil... well played!

Chupaka · Fri Nov 16, 2018 6:48 pm

Try again

server8 · Sat Nov 17, 2018 6:38 pm

4 chains without mu-mimo it's a joke?

I cannot find that setting...

mistry7 · Sun Nov 18, 2018 2:29 pm

4 chains without mu-mimo it's a joke?

I cannot find that setting...

No, that is a feature!

mkx · Sun Nov 18, 2018 2:45 pm

4 chains without mu-mimo it's a joke?

I cannot find that setting...

No, that is a feature!

mimo 4x4 using 2 TX and 2 RX chains works much better than mimo 2x2 using same hardware.

Paternot · Sun Nov 18, 2018 3:27 pm

https://download.mikrotik.com/routeros/ ... beta01.npk

I hate You so much...

mistry7 · Sun Nov 18, 2018 9:50 pm

4 chains without mu-mimo it's a joke?

I cannot find that setting...

No, that is a feature!
mimo 4x4 using 2 TX and 2 RX chains works much better than mimo 2x2 using same hardware.

You Are not really benefiting without mumimo, and Status today ROS doesn’t support MU-Mimo or Wave2 or something else new..
Mikrotik Wireless is outdated!

Mon Nov 19, 2018 5:40 am

https://download.mikrotik.com/routeros/ ... beta01.npk

hahahaha

https://download.mikrotik.com/routeros/ ... beta01.npk

would have built even more excitement for you to destroy

Punkley · Mon Nov 19, 2018 9:27 am

using a w60G and beta28 im not getting any information on the interface page eg

Frequency 64800
Remote MAC
Signal
MCS
PHY Rate
RSSI
TX Sector
TX Sector Info
RX Sector
Distance

All blank, and the quickset page is showing 0 for signal and MCS

Kingsley

tiftok · Sat Nov 24, 2018 12:55 pm

GREET MY PROBLEM SOLVE

l2tp server ISAKMP-SA deleted problem if dhcp enable solve in 6.44beta28

Stril · Sun Nov 25, 2018 1:07 am

using a w60G and beta28 im not getting any information on the interface page eg

Frequency 64800
Remote MAC
Signal
MCS
PHY Rate
RSSI
TX Sector
TX Sector Info
RX Sector
Distance

All blank, and the quickset page is showing 0 for signal and MCS

Kingsley

I can confirm this on LHG60

rzirzi · Mon Nov 26, 2018 10:54 pm

Have MikroTik stopped working at new version of RouterOS ?

raffav · Mon Nov 26, 2018 11:07 pm

Have MikroTik stopped working at new version of RouterOS ?

I think maybe but just maybe they are ready for the 7v beta

would be a very nice Christmas present

server8 · Tue Nov 27, 2018 9:39 am

We are bad boys so no new ROS from Santa Claus this year

emils · Tue Nov 27, 2018 9:57 am

New beta build will be released later today. Had to polish some new features before releasing the version.

honzam · Tue Nov 27, 2018 1:37 pm

New beta build will be released later today. Had to polish some new features before releasing the version.

Please no new 6.44beta...
We wait for V7

msatter · Tue Nov 27, 2018 1:40 pm

We are now all sitting on the edge of our seats.

emils · Tue Nov 27, 2018 3:23 pm

Version 6.44beta39 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.44beta39 (2018-Nov-27 12:14):

Important note!!! Backup before upgrade!
Due to major IPsec configuration changes in RouterOS v6.44beta39+ (see changelog below), it is advised to make a backup before upgrading. Regular downgrade will still be possible as long as no changes in IPsec peer menu are done.

MAJOR CHANGES IN v6.44:
----------------------
!) cloud - added command "/system backup cloud" for backup storing on cloud (CLI only);
!) radius - initial implementation of RadSec (Radius communication over TLS);
!) upgrade - release channels renamed - "bugfix" to "long-term", "current" to "stable" and "release candidate" to "testing";
!) upgrade - "testing" release channel now can contain "beta" together with "release-candidate" versions;
----------------------

Changes in this release:

!) ipsec - added new "identity" menu with common peer distinguishers;
!) ipsec - removed "main-l2tp" exchange-mode, it is the same as "main" exchange-mode;
!) ipsec - removed "users" menu, XAuth user configuration is now handled by "identity" menu;
!) speedtest - added "/tool speed-test" for ping latency, jitter, loss and TCP and UDP download, upload speed measurements (CLI only);
*) btest - added multithreading support for both UDP and TCP tests;
*) bridge - properly disable dynamic CAP interfaces;
*) btest - added warning message when CPU load exceeds 90% (CLI only);
*) certificate - fixed "expires-after" parameter calculation;
*) certificate - properly flush old CRLs when changing store location;
*) certificate - added support for multiple "Subject Alt. Names" (CLI only);
*) chr - correctly initialize grant table version 1;
*) cloud - added "ddns-update-interval" parameter (CLI only);
*) cloud - do not reuse old UDP socket if routing changes are detected;
*) cloud - made address updating faster when new public address detected;
*) conntrack - added new "loose-tcp-tracking" parameter (equivalent to "nf_conntrack_tcp_loose" in netfilter) (CLI only);
*) console - renamed IP protocol 41 to "ipv6-encap";
*) dhcpv4-server - added "User-Name" attribute to RADIUS accounting messages;
*) ethernet - fixed IPv4 and IPv6 packet forwarding on IPQ4018 devices;
*) ethernet - improved per core ethernet traffic classificator on mmips devices;
*) gps - added "coordinate-format" parameter (CLI only);
*) ike2 - added peer identity validation for RSA auth (disabled after upgrade);
*) ike2 - allow to match responder peer by "my-id=fqdn" field;
*) ike2 - properly handle certificates with empty "Subject";
*) ike2 - send split networks over DHCP (option 249) to Windows initiators if DHCP Inform is received;
*) interface - improved system stability when including/excluding a list to itself;
*) ipsec - added new "remote-id" peer matcher (CLI only);
*) ipsec - allow to specify single address instead of IP pool under "mode-config";
*) ipsec - hide empty prefixes on "peer" menu;
*) ipsec - made dynamic "src-nat" rule more specific;
*) ipsec - made peers autosort themselves based on reachability status;
*) ipsec - properly detect AES-NI extension as hardware AEAD;
*) ipsec - properly handle peer profiles on downgrade;
*) ipsec - removed limitation that allowed only single "auth-method" with the same "exchange-mode" as responder;
*) kidcontrol - added statistics web interface for kids (http://router.lan/kid-control);
*) kidcontrol - do not allow users with "read" policy to pause and resume kids;
*) kidcontrol - properly detect time zone changes;
*) log - properly handle long echo messages;
*) led - fixed default LED configuration for wAP 60G AP devices;
*) lte - added "ecno" field for "info" command;
*) lte - added "firmware-upgrade" command for R11e-LTE international modems (CLI only);
*) lte - added support for more ZTE MF90 modems;
*) lte - improved compatibility for Alt38xx modems;
*) lte - increased reported "rsrq" precision (CLI only);
*) profiler - classify kernel crypto processing as "encrypting";
*) routerboard - renamed SIM slots to "a" and "b" on SXT LTE kit;
*) sniffer - save packet capture in "802.11" type when sniffing on w60g interface in "sniff" mode;
*) snmp - do not initialise interface traps on bootup if they are not enabled;
*) ssh - added "allow-none-crypto" parameter to disable "none" encryption usage (CLI only);
*) timezone - updated timezone information from tzdata2018g release;
*) traffic-flow - fixed "src-mac-address" and added "post-src-mac-address" fields;
*) traffic-flow - reduced minimal value of "active-flow-timeout" parameter to 1s;
*) tunnel - properly clear dynamic IPsec configuration when removing/disabling EoIP with DNS as "remote-address";
*) upgrade - made security package depend on DHCP package;
*) usb - fixed power-reset for hAP ac^2 devices;
*) user - speed up first time login process after upgrade from version older than v6.43;
*) userman - show redirect location in error messages;
*) w60g - added "10s-average-rssi" parameter to align mode (CLI only);
*) w60g - improved reconnection detection;
*) w60g - improved "tx-packet-error-rate" reading;
*) winbox - allow to specify SIM slot on LtAP mini;
*) winbox - enabled "fast-forward" by default when adding new bridge;
*) winbox - show "Switch" menu on RB4011iGS+5HacQ2HnD;
*) winbox - show "System/Health" only on boards that have health monitoring;
*) winbox - show "W60G" wireless tab on wAP 60G AP;
*) wireless - improved system stability for all ARM devices with wireless;
*) wireless - report last seen IP address in RADIUS accounting messages;

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.

muetzekoeln · Tue Nov 27, 2018 3:51 pm

"/tool speed-test"

No iperf??

Tue Nov 27, 2018 4:11 pm

Average Joe will not know how to use iperf. I think target audience for this feature is defferent from iperf users

But it is fun anyway:

[admin@1072_bonding_test_1] > /tool speed-test 192.168.1.2 test-duration=60
                  ;;; results can be limited by cpu, note that traffic generation/termination performance might not be 
                      representative of forwarding performance
              status: done
      time-remaining: 0s
    ping-min-avg-max: 111us / 123us / 2.14ms
  jitter-min-avg-max: 0s / 10us / 2.01ms
                loss: 0% (0/1200)
        tcp-download: 11.6Gbps local-cpu-load:83%
          tcp-upload: 12.1Gbps local-cpu-load:89% remote-cpu-load:84%
        udp-download: 24.3Gbps local-cpu-load:5% remote-cpu-load:79%
          udp-upload: 23.1Gbps local-cpu-load:87% remote-cpu-load:20%

Why there are no tcp-download "remote-cpu-load"?

msatter · Tue Nov 27, 2018 4:12 pm

I have my DNS cache being flooded with I think IP coming from the Addresslists.

Screen content of DNS Cache
N IP:xxx.xxx.xxx.xxx type: unknown Data: 0.0.0.0 TTL: 24H

Update: After a reboot it worked again as expected. I think the firmware had to be updated too and that update was already standing ready for the next reboot...which was executed during that reboot.

Thanks for the update of IPSEC and MMIPS and the throughput on my L2TP/IPSEC are really great!

emils · Tue Nov 27, 2018 4:17 pm

Why there are no tcp-download "remote-cpu-load"?

Current implementation allow only include this data into test connection, but waiting for it impacts results, we need to implement data collection as separate connection to get this working, it is in our to-do list.

anuser · Tue Nov 27, 2018 4:20 pm

*) wireless - improved system stability for all ARM devices with wireless;

I ask myself what issues my cAP ac devices have? Can you please give some more information about it?

emils · Tue Nov 27, 2018 4:31 pm

I ask myself what issues my cAP ac devices have? Can you please give some more information about it?

The router could have rebooted due to kernel failure in some rare occasions.

msatter · Tue Nov 27, 2018 4:49 pm

I have L2PT/IPSEC connections that are "dail on demand" and those are displayed in IPSEC-Peers as entries that are unreachable. This is true, however after the connection is up they are still seen as unreachable (colour red).

Chupaka · Tue Nov 27, 2018 4:55 pm

*) chr - correctly initialize grant table version 1;

Huh?.. (O_o)

emils · Tue Nov 27, 2018 4:59 pm

I have L2PT/IPSEC connections that are "dail on demand" and those are displayed in IPSEC-Peers as entries that are unreachable. This is true, however after the connection is up they are still seen as unreachable (colour red).

Can you post some screenshots of your peer menu?

flyfinlander · Tue Nov 27, 2018 5:01 pm

Hi,

What is the idea of that I can't use IKE2 with "pre shared key xauth" ?
When I try to set it up I get the message in attached picture.