The official Mikrotik router thread

I have an interesting one.. How would one block facebook videos from streaming on a Mikrotik without sacrificing too much CPU power ?
 
Yeah I wouldnt try to block videos only on the mikrotik. Its either all of facebook or non of facebook. The videos are probably hosted on their cdn, so same domain name as the images etc.
 
I've noticed that the link up and down times are 2 hours behind the router time, so assume it's reporting at UTC time rather than the router set time timezone. The log etc all the correct time only the last link up times incorrect.
Is it possible to make the set all reported Times as the selected time zone?

Screenshot 2023-11-07 at 13.10.56.png

Screenshot 2023-11-07 at 13.15.26.png
 
DStvNothingOn said:
I've noticed that the link up and down times are 2 hours behind the router time, so assume it's reporting at UTC time rather than the router set time timezone. The log etc all the correct time only the last link up times incorrect.
Is it possible to make the set all reported Times as the selected time zone?

View attachment 1614111

View attachment 1614113
Click to expand...
Would this not be depeant on what NTP server you select in NTP Client?
 
DStvNothingOn said:
I've noticed that the link up and down times are 2 hours behind the router time, so assume it's reporting at UTC time rather than the router set time timezone. The log etc all the correct time only the last link up times incorrect.
Is it possible to make the set all reported Times as the selected time zone?

View attachment 1614111

View attachment 1614113
Click to expand...
Mine match and check again in winbox or ssh as maybe its your browser misinterpreting? They should both come from the system clock
 
have just done the RouterOS update to 7.12 that came out this afternoon and seems to now bw showing correct time.
on Mac so don't use winbox, use browser GUI


R3d3mpt10n said:
Would this not be depeant on what NTP server you select in NTP Client?
Click to expand...

yogidabear said:
Mine match and check again in winbox or ssh as maybe its your browser misinterpreting? They should both come from the system clock
Click to expand...
 
How can I do a speedtest directly from the router?
I have an issue on the FNO side where my 500/500 line is limited to 100/100. I am not at home currently, so can't run a normal speedtest, but can login to the Mikrotik, so want to do a speedtest from there
 
LandyMan said:
How can I do a speedtest directly from the router?
I have an issue on the FNO side where my 500/500 line is limited to 100/100. I am not at home currently, so can't run a normal speedtest, but can login to the Mikrotik, so want to do a speedtest from there
Click to expand...
You can use this one, but its not local

IPv4: 23.162.144.120
IPv6: 2605:6340:0:1b::4
btest username: MikrotikBtest
btest password: MikrotikBtest
Quick notes - limit total testing time to less than 10 minutes.
You must wait 27 hours until you can btest again.
If you attempt to btest more than 10 minutes , then you go to btest jail for 7+ days until you can btest again
If you attempt to btest without waiting 27 hours , then you go to btest jail for 7+ days until you can btest again.
If you attempt to btest and you are in 7-day btest jail , then you reset 7-day btest jail back to 7+ days.
No automatic btest scripts on a timed schedule are permitted.
All btest must be manually performed by a human.
Repeated login failures using the old btest/btest user/password may auto place your IP address in a 7-Day btest jail.
 
Went_For_Beer said:
You can use this one, but its not local

IPv4: 23.162.144.120
IPv6: 2605:6340:0:1b::4
btest username: MikrotikBtest
btest password: MikrotikBtest
Quick notes - limit total testing time to less than 10 minutes.
You must wait 27 hours until you can btest again.
If you attempt to btest more than 10 minutes , then you go to btest jail for 7+ days until you can btest again
If you attempt to btest without waiting 27 hours , then you go to btest jail for 7+ days until you can btest again.
If you attempt to btest and you are in 7-day btest jail , then you reset 7-day btest jail back to 7+ days.
No automatic btest scripts on a timed schedule are permitted.
All btest must be manually performed by a human.
Repeated login failures using the old btest/btest user/password may auto place your IP address in a 7-Day btest jail.
Click to expand...
Ah yes, I have used that one previously, but a hit and miss sometimes.
 
You can use the cmd line fetch tool to download a file from a known server , if you have the storage available :P
 
I need to drop/disconnect a connection (eth1) from scheduler. Does anybody know the command? Also, what is the command for reboot.
 
To create a scheduler in MikroTik RouterOS that disconnects (disables) and then re-enables an Ethernet interface (like `eth1`), and another scheduler to reboot the router, you'll need to use MikroTik's scripting language within the Scheduler tool. Here's a step-by-step guide for both tasks:

### Scheduler to Disable and Re-Enable `eth1`

1. **Log in** to your MikroTik router via Winbox or WebFig.
2. Navigate to **System** > **Scheduler**.
3. Click on **Add New** to create a new scheduler.
4. **Name** your scheduler (e.g., `DisableEth1`).
5. Set the **Start Time** to when you want the task to begin.
6. Set the **Interval** to how often you want this task to repeat.
7. In the **On Event** field, enter the following script to disable `eth1`:

Bash: 
/interface ethernet disable [find where name="eth1"]
   :delay 10s
/interface ethernet enable [find where name="eth1"]

This script will disable `eth1`, wait for 10 seconds (you can adjust the delay as needed), and then re-enable it.
8. Click **OK** to save the scheduler.

### Scheduler for Rebooting the Router

1. Follow steps 1-4 as above, but name the scheduler something like `RebootRouter`.
2. Set the **Start Time** and **Interval** according to your preference.
3. In the **On Event** field, enter the following command:
Bash: 
/system reboot

4. Click **OK** to save the scheduler.

This will create two separate schedulers: one for disabling and re-enabling `eth1` and another for rebooting the router at specified times. Remember to carefully set these schedulers, as they can impact your network's operation. Also, it's good practice to test these settings in a controlled environment before deploying them in a production network.
 
Anthro said:
To create a scheduler in MikroTik RouterOS that disconnects (disables) and then re-enables an Ethernet interface (like `eth1`), and another scheduler to reboot the router, you'll need to use MikroTik's scripting language within the Scheduler tool. Here's a step-by-step guide for both tasks:

### Scheduler to Disable and Re-Enable `eth1`

1. **Log in** to your MikroTik router via Winbox or WebFig.
2. Navigate to **System** > **Scheduler**.
3. Click on **Add New** to create a new scheduler.
4. **Name** your scheduler (e.g., `DisableEth1`).
5. Set the **Start Time** to when you want the task to begin.
6. Set the **Interval** to how often you want this task to repeat.
7. In the **On Event** field, enter the following script to disable `eth1`:

Bash: 
/interface ethernet disable [find where name="eth1"]
   :delay 10s
/interface ethernet enable [find where name="eth1"]

This script will disable `eth1`, wait for 10 seconds (you can adjust the delay as needed), and then re-enable it.
8. Click **OK** to save the scheduler.

### Scheduler for Rebooting the Router

1. Follow steps 1-4 as above, but name the scheduler something like `RebootRouter`.
2. Set the **Start Time** and **Interval** according to your preference.
3. In the **On Event** field, enter the following command:
Bash: 
/system reboot

4. Click **OK** to save the scheduler.

This will create two separate schedulers: one for disabling and re-enabling `eth1` and another for rebooting the router at specified times. Remember to carefully set these schedulers, as they can impact your network's operation. Also, it's good practice to test these settings in a controlled environment before deploying them in a production network.
Click to expand...

Thanks I'll try this out.
 
Gurus, how would I block access to Spotify for a specific device on my network?

Basically I don't want my AVR to be able to stream from Spotify, while still allowing users on their laptops/phones to do so.
 
Naks said:
Gurus, how would I block access to Spotify for a specific device on my network?

Basically I don't want my AVR to be able to stream from Spotify, while still allowing users on their laptops/phones to do so.
Click to expand...
I think you could do this with some clever firewall rules to discard traffic matching a Spotify regex and the device IP/mac

If you have PiHole, you can do it there, too. If you don’t have PiHole, now is a good time to start
 
PhireSide said:
I think you could do this with some clever firewall rules to discard traffic matching a Spotify regex and the device IP/mac
If you have PiHole, you can do it there, too. If you don’t have PiHole, now is a good time to start
Click to expand...

no PiHole, so I tried this: https://scoop.co.za/blog/mikrotik-traffic-filter, but it's not working.

Code: 
/ip/firewall/address-list> print
Columns: LIST, ADDRESS, CREATION-TIME
# LIST     ADDRESS         CREATION-TIME       
0 Spotify  35.186.224.25   dec/02/2023 10:02:41
1 Spotify  52.70.106.183   dec/02/2023 10:18:45
2 Spotify  104.199.65.124  dec/02/2023 10:19:46
3 Spotify  35.186.0.0/16   dec/02/2023 10:23:09
4 Spotify  35.184.0.0/13   dec/02/2023 10:23:22

Drop all Spotify traffic from T778 only
      chain=forward action=drop src-address=X dst-address-list=Spotify log=no log-prefix=""
 
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
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X