The official Mikrotik router thread

You never mentioned what the AVR needs internet for, so this could help. My phone for example streams spotify on port 443 so I could block that TCP port. This is a terrible idea for a phone, but maybe your AVR doesnt care.

Also maybe your AVR doesnt stream encrypted, but that again you would have to torch to see what port its going to.
 
Put the drop above the accept rule if you have one like this:

Code:
add action=drop chain=forward dst-address=196.25.1.1 src-address=172.16.8.208
add action=accept chain=forward comment="Accept Established, Related" connection-state=established,related

That example is one you can test to see the drop works. Just replace the src-address with your device and do a ping to 196.25.1.1. Once you see the rule works you can maybe find the problem. If it still doesnt work then your range of IP's is not complete. You can torch traffic from that IP to see where its going and get the IP

Ok, with this setup, I see a 'could not make socket' in Winbox, using the AVR as the Source Adress. But I can ping it from my PC.

You never mentioned what the AVR needs internet for, so this could help. My phone for example streams spotify on port 443 so I could block that TCP port. This is a terrible idea for a phone, but maybe your AVR doesnt care.
Also maybe your AVR doesnt stream encrypted, but that again you would have to torch to see what port its going to.

No, I need 443 to stream other things, looking at Torch, it uses port 443 to stream from TuneIn/Qobuz.
 
Is there a solution to have MikroTik’s centrally managed?

Preferably a solution for an ISP that gives a high-level overview where I can assign devices into groups and grant clients access to view items only with-in that group.

As well as providing bulk config changes, etc.

I’ve played with TR069, but I haven’t come across a product that achieves the above simply enough.
 
Is there a solution to have MikroTik’s centrally managed?

Preferably a solution for an ISP that gives a high-level overview where I can assign devices into groups and grant clients access to view items only with-in that group.

As well as providing bulk config changes, etc.

I’ve played with TR069, but I haven’t come across a product that achieves the above simply enough.
They used to have "The Dude", which looked promising like a decade or so ago. Dunno what happened to that practically

 
Is there a solution to have MikroTik’s centrally managed?

Preferably a solution for an ISP that gives a high-level overview where I can assign devices into groups and grant clients access to view items only with-in that group.

As well as providing bulk config changes, etc.

I’ve played with TR069, but I haven’t come across a product that achieves the above simply enough.
For my personal devices I use terraform. Although I am unsure if it will be good enough for an isp. The problem is, the limited amount of things that can be configured from terraform. Some things I' use terraform to deploy scripts that manage the things terraform can't do.
 
This little project has matured nicely and I regret selling all my tiks during the pandemic.
If you have a tik or look after a fleet then this free software tier is the biscuit: https://www.mikrocloud.com/

Is there a solution to have MikroTik’s centrally managed?

Preferably a solution for an ISP that gives a high-level overview where I can assign devices into groups and grant clients access to view items only with-in that group.

As well as providing bulk config changes, etc.

I’ve played with TR069, but I haven’t come across a product that achieves the above simply enough.
 
Is there a solution to have MikroTik’s centrally managed?

Preferably a solution for an ISP that gives a high-level overview where I can assign devices into groups and grant clients access to view items only with-in that group.

As well as providing bulk config changes, etc.

I’ve played with TR069, but I haven’t come across a product that achieves the above simply enough.
Give https://www.mikrocloud.com/ a go as previously recommended. You can contact the dev via https://www.linkedin.com/in/hannes-kruger/

Its the biscuit for Mikrotiks.
 
For my personal devices I use terraform. Although I am unsure if it will be good enough for an isp. The problem is, the limited amount of things that can be configured from terraform. Some things I' use terraform to deploy scripts that manage the things terraform can't do.

Thank you, will give it a go.
 
RouterOS 7.13.3 [Stable]
Jan 25th 2024, 09:13


7.13.3 changelog:​

1. When upgrading by using "check-for-updates", all versions earlier than 7.12 will display 7.12 as the latest available version. Upgrade from v7.12 to v7.13 or later versions must be done through 7.12 in order to convert wireless packages automatically. Fresh installation with Netinstall or manual package installation works in the same manner as always.

2. Drivers for older wireless and 60GHz interfaces, as well as the wireless management system CAPsMAN, are now part of a separate "wireless" package instead of being a part of the bundle package. This package can be uninstalled if not needed.

3. The existing "wifiwave2" package has been divided into distinct packages: "wifi-qcom" and "wifi-qcom-ac", and the necessary utilities for WiFi management are now included in the RouterOS bundle. RouterOS and "wifi-qcom-ac" packages alongside each other now fit into 16MB flash memory.

What's new in 7.13.3 (2024-Jan-24 15:16):

*) dns - fixed DNS service crash when DoH used (introduced in v7.13.1);
*) fetch - fixed fetch when using "src-path" with SFTP mode (introduced in v7.13);
*) fetch - less verbose logging (introduced in v7.13);
*) health - show voltage when powering KNOT R through Micro-USB;
*) lte - fixed Simcom modem support in 0x9001 USB composition;
*) lte - improved SIM PIN unlock event handling for MBIM FG621-EA;
*) poe-out - fixed "power-cycle" for CRS354-48P-4S+2Q+ device (introduced in v7.13);
*) poe-out - improved PoE out reliability on routers with a single PoE out interface;
*) sms - fixed SMS inbox for FG621-EA modem (introduced in v7.13);
*) sms - fixed SMS sending from WinBox and WebFig (introduced in v7.13);
*) sms - improved system stability when working with SMS (introduced in v7.13);
*) system - properly close HTTP/S connections initiated by the router;
*) tftp - improved invalid request processing;
*) wifi-qcom - improved system stability when using FastPath (introduced in v7.13);
 
Hi guys,
Wondering if anyone can assist me...

I updated the OS on my HAP AC3 to the latest version (6.49.13) but once I did this, the wheels regarding my connectivity dropped off completely.

High latency yet able to still DL at 50Mbps but the upload was beyond useless... sometimes 0.01Mbps.
Using the absolute default settings - just added in the PPPoE deets for Telskum. I thought that there was a fault with my line but this was not the case.

I tried to fix this using an older HEX RB750gr3 (after unknowingly updating the OS) and the exact issue appeared.

Plugged in a basic TP Link router and got 50/50Mbps no issues.

Does anyone have any ideas what could be causing this?

Thanks in advance :)
 
Last edited:
Hi guys,
Wondering if anyone can assist me...

I updated the OS on my HAP AC3 to the latest version (6.49.13) but once I did this, the wheels regarding my connectivity dropped off completely.

High latency yet able to still DL at 50Mbps but the upload was beyond useless... sometimes 0.01Mbps.
Using the absolute default settings - just added in the PPPoE deets for Telskum. I thought that there was a fault with my line but this was not the case.

I tried to fix this using an older HEX RB750gr3 (after unknowingly updating the OS) and the exact issue appeared.

Plugged in a basic TP Link router and got 50/50Mbps no issues.

Does anyone have any ideas what could be causing this?

Thanks in advance :)
I think you should maybe try rolling back to an older version and see if the problem persists.

You can also reach out to MT support; they are quite on the ball with support in most instances/
 
I think you should maybe try rolling back to an older version and see if the problem persists.

You can also reach out to MT support; they are quite on the ball with support in most instances/
Thanks - tried downgrading (successfully to 6.49.10) yet problem still persists:
1707251765972.png

The guys from Cool Ideas suggested that I try clamping MTU/MSS but I have no idea how I would do that..
Any help once again would greatly be appreciated
 
RouterOS 7.13.4 [Stable]
Feb 7th 2024, 15:28


7.13.4 changelog:​

1. When upgrading by using "check-for-updates", all versions earlier than 7.12 will display 7.12 as the latest available version. Upgrade from v7.12 to v7.13 or later versions must be done through 7.12 in order to convert wireless packages automatically. Fresh installation with Netinstall or manual package installation works in the same manner as always.

2. Drivers for older wireless and 60GHz interfaces, as well as the wireless management system CAPsMAN, are now part of a separate "wireless" package instead of being a part of the bundle package. This package can be uninstalled if not needed.

3. The existing "wifiwave2" package has been divided into distinct packages: "wifi-qcom" and "wifi-qcom-ac", and the necessary utilities for WiFi management are now included in the RouterOS bundle. RouterOS and "wifi-qcom-ac" packages alongside each other now fit into 16MB flash memory.

What's new in 7.13.4 (2024-Feb-07 11:59):

*) bridge - avoid per-VLAN host flushing on HW offloaded bridge (introduced in v7.13);
*) defconf - fixed firewall rule for IPv6 UDP traceroute;
*) leds - fixed modem LED indication for SXT LTE 3-7 (introduced in v7.13);
*) lte - fixed Simcom modem support in 0x9000; 0x9002, 0x9002; 0x901a and 0x901b USB compositions (introduced in v7.13);
*) ovpn - improved system stability when using HW encryption on ARM64 devices (introduced in v7.13);
*) route-filter - fixed AS path matchers when input and output chains are used;
 
Thanks - tried downgrading (successfully to 6.49.10) yet problem still persists:
View attachment 1657582

The guys from Cool Ideas suggested that I try clamping MTU/MSS but I have no idea how I would do that..
Any help once again would greatly be appreciated
MTU clamping can be done using a mangle rule. Something like this:

Code:
/ip firewall mangle
add out-interface=pppoe-out protocol=tcp tcp-flags=syn action=change-mss new-mss=1300 chain=forward tcp-mss=1301-65535
 
MTU clamping can be done using a mangle rule. Something like this:

Code:
/ip firewall mangle
add out-interface=pppoe-out protocol=tcp tcp-flags=syn action=change-mss new-mss=1300 chain=forward tcp-mss=1301-65535
Thanks so much!

I think I tried something similar which I found on the internet but will try your suggestion :)
 
Thanks so much!

I think I tried something similar which I found on the internet but will try your suggestion :)
You mentioned Telkom and Cool ideas so not sure what service you have, however telkom on openserve works with the default pppoe settings.
 
Top
Sign up to the MyBroadband newsletter
X