still hoping to have a small wifi2 package for device that have small space
i use dns redirec, 7.3 is not working ,
version 7.2 ok, long ime 7.1.5 version is ok
add action=redirect chain=dstnat dst-port=53 protocol=udp in-interface-list=LAN
add action=redirect chain=dstnat dst-port=53 protocol=tcp in-interface-list=LAN
Hello.
After upgrading to 7.3 sending emails through google fails. Any advice?
BR.
Might be a Google thing.
I seem too recall an announcement from Google you can not use simple authentication anymore as of end of May.
Needs to be an app password (or something like that, can’t verify right now)
But this morning it worked perfectly, it was when updating all my computers from 7.2.1 to 7.3, sending emails (through google) from different accounts and different routers stopped working.
BR.
Works fine for me, gmail in a web browser, Apple Mail on OSX workstations, and Mail on an iPhone. I use Google Workspace, fwiw. CCR2004 on the edge, 7.3 with 7.3 firmware.
I am referring to sending emails through the routeros application /tool->emails
BR.
That is a feature that has been hanging by a thread for quite some time. Basically it could stop working at any moment.
It would be better to send the mails through the ISP’s smarthost (which trusts the IP addresses within its own allocation) rather than directly to a Google server…
You are right, the problem is with Google.
Since May 30 they have reinforced the security of the accounts and now it is necessary to activate the two-step verification and then create “application passwords” on the Google website with 16 characters.
I have tried it and it has worked.
BR.
Thanks for confirming my memory is still ok 
But still you are not safe. Microsoft has done that before, and now they plan (in october, I think) to end support of those “application passwords” as well.
So, only 2-factor remains. Which of course sucks for applications like this.
Probably Google is going to do that as well… don’t know if it has already been planned and announced.
In both routers
/system routerboard settings set auto-upgrade=yes
>
> was configured and routerboard firmware version was v7.2.3
You have remote routers on auto-upgrade and get them updated at the same day of a new 7.x release?
You seem to be more the YOLO type of admin ¯\_(ツ)_/¯That setting does not actually auto-upgrade RouterOS…
But indeed I have removed it on all my routers some time ago, after reading about mishaps with firmware upgrade. Now I only upgrade it when there are indications that it is required.
Firmware version should always match RouterOS version, too many “admins” run on firmware version 3.1 and ROS v7 and complain about problems.
RB3011 is resolved by disconnecting the fibre from the SFP module and downgrading back to 7.2.1 along with firmware.
For the RB450Gx4 I have a feeling, disconnect some Ethernet cables might help
Yeah, everything related to ”auto-upgrade” and similar scripts should be abandoned immediately until Mikrotik sorts out the release management.
It’s actually pretty hard to understand why MT even try to promote this functionallity due to the current sitation (I was thinking about the YT stuff)
Why? Do you have a change list for all the firmware version so you know what has been updated, and you can see that its needed?
PS to any auto upgrade or upgrade to a new release the first day it comes out on a production router, have not read this forum…
Wait a week or two, read forum, upgrade on a test router, equal to the production router. If all OK, you can upgrade if there are some new function that you need or an important fix that need to be added.
Ask MT, they encourage the version should match as best practice. Either way, does it make sense to have firmware version 3.1 but ROS 7.3?
I do agree in that, but it would be better that firmware and RouterOS was just one thing, if it was to always upgrade both.
@DarkeNate
The 2 parts that make up the solution for Tik gear is:
1… The functional software that drives the capability
2… The Firmware [drivers] that enables the functional software to exploit the capability
So When upgrading it’s MANDATORY to always do both parts sequentially otherwise the capability will fail.
I’m just another customer of MikroTik. This flaw of RouterOS + firmware separation is for MikroTik to fix their xxx. The advice is set auto-upgrade=yes when upgrading ROS and then reboot twice, go figure.