The official Mikrotik router thread

Cactus said:
I flashed all my sonoff devices with tasmota.

Tasmota Documentation - Tasmota

Open source firmware for ESP devices with easy configuration using webUI, OTA updates, automation using timers or rules, expandability and entirely local control over MQTT, HTTP, serial or KNX.
tasmota.github.io tasmota.github.io

It works well with Home assistant if you ever go that route
Click to expand...
I was looking at that the other day, will have to wait. Rebuilding OMV & docker containers this week.
 
PhireSide said:
What do you need for that? I seem to recall reading/hearing that you need an Arduino to connect with it, with perhaps some light soldering as well?
Click to expand...
I flashed mine with a Raspberry pi if I remember correctly. Was a long time ago. Just remember there's no going back
 
PhireSide said:
Very recently there has been some sorcery going on with my Sonoff devices on our network.

We have a handful of Eachen/Sonoff light switches that are linked up with Google Home, and we have always had an issue with one of them (10.0.0.194 in this list) that kept on losing and requesting a DHCP lease. As of a few nights ago, all of the Sonoff/Eachen devices are now doing it! You can see the Google-Home-Mini has a lease that still has 8h17 before it expires, but everything below that is the smart home devices and they are constantly renewing their leases:

View attachment 1227476

Has anyone else had something similar happen recently? They connect to a dedicated IoT SSID via an Unifi AP that runs 2.4GHz only. I can connect to this SSID with my phone or a laptop and it works just fine. It might be worth noting that i run static IP's for all the devices on the main 5GHz network, which is why the range for the switches are all from 188 and up.

At the moment I am suspecting foul play on the Unifi side of things, but I thought I'd post up here for good measure.
Click to expand...
Same issue here, my lights also turned on randomly 1 AM at night and then all devices were offline for nearly 2 hours and since then constantly requesting leases.
 
Thor said:
Same issue here, my lights also turned on randomly 1 AM at night and then all devices were offline for nearly 2 hours and since then constantly requesting leases.
Click to expand...
Is it fixed now? All mine are working OK again (touch wood).

If yours are still off then it could be something else.
 
PhireSide said:
Is it fixed now? All mine are working OK again (touch wood).

If yours are still off then it could be something else.
Click to expand...
I had to reboot my homebridge about 2 hours ago, homekit reported all my sonoff lights as offline

Also rebooted last night during the outage
 
Leno said:
I had to reboot my homebridge about 2 hours ago, homekit reported all my sonoff lights as offline

Also rebooted last night during the outage
Click to expand...
I, too, did the reboot dance. My first suspicion was my Unifi setup as my router has been untouched for 30+ days.

The Unifi runs in docker that auto updates at 3:00AM but this happened at around 11 or 12 so it was strange, but I didn't immediately make the link in my head at the time.
 
Morning Mikrotik experts, I need some help.

It seems I've been used as part of a DNS attack :(
I have these rules in my Mikrotik, but it seems to not work properly.

Code: 
add action=drop chain=input connection-state=new dst-port=53 in-interface=\
    pppoe-afrihost protocol=udp
add action=drop chain=input connection-state=new dst-port=53 in-interface=\
    pppoe-cool-ideas protocol=udp
add action=drop chain=input connection-state=new dst-port=53 in-interface=\
    pppoe-afrihost protocol=tcp
add action=drop chain=input connection-state=new dst-port=53 in-interface=\
    pppoe-cool-ideas protocol=tcp

1642404368675.png

1642403967381.png


1642403914117.png


For now, to stop this what I did was added this firewall rule to my pi and removed all other rules. Theoretically, only internal 192.x.x.x ips should be able to access the pi now, but ideally want to set up the Mikrotik properly.
Code: 
ufw allow all 192.168.0.0/16
 
Never mind, found the issue. It was a pebcac error.
I had a dst-nat rule to force all traffic on 53 to the pi (not from the pi bridge), and well dst-nat opened it up to the world as well :confused:
 
Has anyone updated their Mikrotik RouterOS version to 7.1? I've got a RB750Gr3 which is currently on 6.49.2. Would love to upgrade to 7.1 but scared that it's going to mess up my config on that router.
 
deweyzeph said:
Has anyone updated their Mikrotik RouterOS version to 7.1? I've got a RB750Gr3 which is currently on 6.49.2. Would love to upgrade to 7.1 but scared that it's going to mess up my config on that router.
Click to expand...
I went to v7 and it did screw up my config pretty badly. I had to basically redo it but still had trouble with some of my Mangle rules, so I rolled back to 6.49.2 again and haven't tried again since.
 
PhireSide said:
I went to v7 and it did screw up my config pretty badly. I had to basically redo it but still had trouble with some of my Mangle rules, so I rolled back to 6.49.2 again and haven't tried again since.
Click to expand...

That's exactly what I'm afraid of. I've seen mixed reviews about 7.1. There are some cool new features that it introduces, but also lots of reports of certain things missing that were in 6.49.2.
 
deweyzeph said:
That's exactly what I'm afraid of. I've seen mixed reviews about 7.1. There are some cool new features that it introduces, but also lots of reports of certain things missing that were in 6.49.2.
Click to expand...
In all honesty I can't recommend it as your main router. Maybe if you have a fallback router that you could play with and keep your current one as a hot spare, but I've also seen a lot of bugs crop up with the new rOS
 
PhireSide said:
In all honesty I can't recommend it as your main router. Maybe if you have a fallback router that you could play with and keep your current one as a hot spare, but I've also seen a lot of bugs crop up with the new rOS
Click to expand...

I actually have my RB750Gr3 sitting in front of my UDM Pro for WAN failover between my Openserve fibre line and LTE backup. I also use it for IPv6 prefix assignment. The UDM Pro unfortunately is poor at both of those functions, so I'm essentially using my UDM Pro as a very expensive Unifi controller with the Mikrotik taking over all routing and gateway functions.
 
I have been on 7.1 for a while

I had to redo my policy routing (route tables) but apart from that its working fine

IPv6 dies if you have any form of queue active though - even v4
 
deweyzeph said:
Has anyone updated their Mikrotik RouterOS version to 7.1? I've got a RB750Gr3 which is currently on 6.49.2. Would love to upgrade to 7.1 but scared that it's going to mess up my config on that router.
Click to expand...
Did my RB2011 with no issue, but I do not have the most complex of setups - VLAN on the WAN interface is all
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X