<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://wiki.plecko.hr/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://wiki.plecko.hr/feed.php">
        <title>Eureka Moment mikrotik:scripting</title>
        <description></description>
        <link>https://wiki.plecko.hr/</link>
        <image rdf:resource="https://wiki.plecko.hr/lib/tpl/bootstrap3/images/favicon.ico" />
       <dc:date>2026-04-25T16:46:08+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://wiki.plecko.hr/doku.php?id=mikrotik:scripting:block_invalid_login&amp;rev=1572509100&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.plecko.hr/doku.php?id=mikrotik:scripting:block_known_viruses&amp;rev=1572509100&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.plecko.hr/doku.php?id=mikrotik:scripting:block_portscanners&amp;rev=1572509100&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.plecko.hr/doku.php?id=mikrotik:scripting:clk_sync&amp;rev=1572509100&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.plecko.hr/doku.php?id=mikrotik:scripting:connected_users_list_to_email&amp;rev=1572509100&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.plecko.hr/doku.php?id=mikrotik:scripting:private_dyndns&amp;rev=1572509100&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.plecko.hr/doku.php?id=mikrotik:scripting:queue_stats_to_email&amp;rev=1572509100&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.plecko.hr/doku.php?id=mikrotik:scripting:start&amp;rev=1572509100&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://wiki.plecko.hr/lib/tpl/bootstrap3/images/favicon.ico">
        <title>Eureka Moment</title>
        <link>https://wiki.plecko.hr/</link>
        <url>https://wiki.plecko.hr/lib/tpl/bootstrap3/images/favicon.ico</url>
    </image>
    <item rdf:about="https://wiki.plecko.hr/doku.php?id=mikrotik:scripting:block_invalid_login&amp;rev=1572509100&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-10-31T09:05:00+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>mikrotik:scripting:block_invalid_login</title>
        <link>https://wiki.plecko.hr/doku.php?id=mikrotik:scripting:block_invalid_login&amp;rev=1572509100&amp;do=diff</link>
        <description>Mikrotik: Block invalid SSH and FTP login attempts

Paste this into Mikrotik terminal


/ip firewall filter
add action=log chain=input comment=&quot;Drop FTP Brute Force&quot; disabled=no dst-port=21 log-prefix=FTP_DROP protocol=tcp src-address-list=ftp_blacklist
add action=drop chain=input comment=&quot;Drop FTP Brute Force&quot; disabled=no dst-port=21 protocol=tcp src-address-list=ftp_blacklist
add action=accept chain=output comment=&quot;Drop FTP Brute Force - Allow 'Incorrect Login' reply&quot; content=&quot;530 Login incorr…</description>
    </item>
    <item rdf:about="https://wiki.plecko.hr/doku.php?id=mikrotik:scripting:block_known_viruses&amp;rev=1572509100&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-10-31T09:05:00+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>mikrotik:scripting:block_known_viruses</title>
        <link>https://wiki.plecko.hr/doku.php?id=mikrotik:scripting:block_known_viruses&amp;rev=1572509100&amp;do=diff</link>
        <description>Mikrotik: Block known viruses

If you want to stop (some of the) known viruses that always come in through the same port, add some rules to your Mikrotik firewall.

Paste this into Mikrotik terminal


/ip firewall filter
add chain=virus protocol=tcp dst-port=135-139 action=drop comment=&quot;Drop Blaster Worm&quot;
add chain=virus protocol=udp dst-port=135-139 action=drop comment=&quot;Drop Messenger Worm&quot;
add chain=virus protocol=tcp dst-port=445 action=drop comment=&quot;Drop Blaster Worm&quot;
add chain=virus protoco…</description>
    </item>
    <item rdf:about="https://wiki.plecko.hr/doku.php?id=mikrotik:scripting:block_portscanners&amp;rev=1572509100&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-10-31T09:05:00+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>mikrotik:scripting:block_portscanners</title>
        <link>https://wiki.plecko.hr/doku.php?id=mikrotik:scripting:block_portscanners&amp;rev=1572509100&amp;do=diff</link>
        <description>Mikrotik: Block port scanners

Getting tired of port scanners like I am? Block them with these few simple rules. It is not bullet proof but it will reduce your daily headache.

Paste this into Mikrotik terminal


/ip firewall filter
add chain=input protocol=tcp psd=21,3s,3,1 action=add-src-to-address-list address-list=&quot;port scanners&quot; address-list-timeout=2w comment=&quot;Port scanners to list &quot; disabled=no
add chain=input protocol=tcp tcp-flags=fin,!syn,!rst,!psh,!ack,!urg action=add-src-to-address-l…</description>
    </item>
    <item rdf:about="https://wiki.plecko.hr/doku.php?id=mikrotik:scripting:clk_sync&amp;rev=1572509100&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-10-31T09:05:00+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>mikrotik:scripting:clk_sync</title>
        <link>https://wiki.plecko.hr/doku.php?id=mikrotik:scripting:clk_sync&amp;rev=1572509100&amp;do=diff</link>
        <description>Clock synchronization on Mikrotik

Create a scheduler with 24-hour interval with the following code:


/system clock manual set dst-delta=+01:00 dst-end=&quot;jan/01/2020 00:00:00&quot; dst-start=&quot;jan/01/1970 00:00:00&quot; time-zone=+01:00
/system ntp client set enabled=yes mode=unicast primary-ntp=192.168.1.12</description>
    </item>
    <item rdf:about="https://wiki.plecko.hr/doku.php?id=mikrotik:scripting:connected_users_list_to_email&amp;rev=1572509100&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-10-31T09:05:00+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>mikrotik:scripting:connected_users_list_to_email</title>
        <link>https://wiki.plecko.hr/doku.php?id=mikrotik:scripting:connected_users_list_to_email&amp;rev=1572509100&amp;do=diff</link>
        <description>Send a list of connected users to e-mail on Mikrotik

If you need a semi-accurate (more often you run it, more accurate it will be) list of active users on your Mikrotik (including wireless and VPN connections), here is a script for you.

Set your clock correctly and then create a script:</description>
    </item>
    <item rdf:about="https://wiki.plecko.hr/doku.php?id=mikrotik:scripting:private_dyndns&amp;rev=1572509100&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-10-31T09:05:00+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>mikrotik:scripting:private_dyndns</title>
        <link>https://wiki.plecko.hr/doku.php?id=mikrotik:scripting:private_dyndns&amp;rev=1572509100&amp;do=diff</link>
        <description>Privately owned dyndns server (sort of) and Mikrotik

If you constantly connect to your home network (as I do), you have, on occasion, experienced that frustrating moment when the dynamic dns service is down for whatever reason. Let’s assume that you are a person who likes to have more controll over the services you use, and have setup your private</description>
    </item>
    <item rdf:about="https://wiki.plecko.hr/doku.php?id=mikrotik:scripting:queue_stats_to_email&amp;rev=1572509100&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-10-31T09:05:00+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>mikrotik:scripting:queue_stats_to_email</title>
        <link>https://wiki.plecko.hr/doku.php?id=mikrotik:scripting:queue_stats_to_email&amp;rev=1572509100&amp;do=diff</link>
        <description>Send Queue tree stats to e-mail

If you have Queues set up per IP address, you can send yourself Queue stats via email. You might want to see where your bandwidth is going, or you might want to detect who's been making a backup of the internet and preventing other users from using the Internet.</description>
    </item>
    <item rdf:about="https://wiki.plecko.hr/doku.php?id=mikrotik:scripting:start&amp;rev=1572509100&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-10-31T09:05:00+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>mikrotik:scripting:start</title>
        <link>https://wiki.plecko.hr/doku.php?id=mikrotik:scripting:start&amp;rev=1572509100&amp;do=diff</link>
        <description>Scripting




	* Clock synchronization on Mikrotik
	* Mikrotik: Block invalid SSH and FTP login attempts
	* Mikrotik: Block known viruses
	* Mikrotik: Block port scanners
	* Privately owned dyndns server (sort of) and Mikrotik
	* Send a list of connected users to e-mail on Mikrotik
	* Send Queue tree stats to e-mail</description>
    </item>
</rdf:RDF>
