For example, a client IP address that we set and we give the public IP src-nat (assumed not to go through a proxy) in Mikrotik is: 172.168.1.0/30
A. Login to your Mikrotik OS, and type:
system script
2. Type the script to turn off customer connections to the public:
add name = "customer-off" \
policy = ftp, read, write, policy, winbox, password \
source = {/ ip firewall nat set [/ ip firewall nat find \
src-address = 172.168.1.0/30] disabled = yes}
3. While the script to turn the customer connection to the public:
add name = "customer-on" \
policy = ftp, read, write, policy, winbox, password \
source = {/ ip firewall nat set [/ ip firewall nat find \
src-address = 172.168.1.0/30] disabled = no}
4. Then, the final step is to determine the hours when customers need to connect to the public (internet) or turn off the public IP customers we have had input into the script. For example, we specify the hours of 9:00 a.m. to 2:30 p.m. at the connection alive, while the death of the connection time at 14:31 to 08:59. Simply we are calling the script name in the schedule:
.. scheduler
add name = hidup09-1430 start-time = 09:00:00 \
interval = 1d on-event = customer-on
add name = mati1431-0859 start-time = 14:31:00 \
interval = 1d on-event = customer-off
--------------- O ------------
The other method, in theory (Halah) can be done with such an idea:
* Set on the Local Interface or Interface is used as a gateway by our Client, with its ARP Reply Status Only. Furthermore we statiskan IP ARP List. Well, with a mode such that only a registered client MAC and IP addresses that can pass Addressnyalah Internet connection. So you can also create a script to disable the IP and ARP mengenable List, then contrived skedulnya the Scheduler.
* Set the Queue, whether it's Simple Queue or Queue Tree, with a large decrease packet traffic passing by, let alone given at 8kb. As for the hours normally set to the beginning of the packet. So the connection as "gag"
* Set the IP Filter Firewall Input Rules give the chain to the customer's IP address, if you need to set any given port, then give the Action Drop, if you want to pass more traffic on the ACCEPT of course on the Action. Note, Mikrotik seems to read the rule in sequence from top to bottom, as if the interpreter is Languange programming. Drop Rule so that the set position at the top of the action other than Drop rule.
Which method is effective, it seems to try too, hehehe.
Please try, but do not in any use.
A. Login to your Mikrotik OS, and type:
system script
2. Type the script to turn off customer connections to the public:
add name = "customer-off" \
policy = ftp, read, write, policy, winbox, password \
source = {/ ip firewall nat set [/ ip firewall nat find \
src-address = 172.168.1.0/30] disabled = yes}
3. While the script to turn the customer connection to the public:
add name = "customer-on" \
policy = ftp, read, write, policy, winbox, password \
source = {/ ip firewall nat set [/ ip firewall nat find \
src-address = 172.168.1.0/30] disabled = no}
4. Then, the final step is to determine the hours when customers need to connect to the public (internet) or turn off the public IP customers we have had input into the script. For example, we specify the hours of 9:00 a.m. to 2:30 p.m. at the connection alive, while the death of the connection time at 14:31 to 08:59. Simply we are calling the script name in the schedule:
.. scheduler
add name = hidup09-1430 start-time = 09:00:00 \
interval = 1d on-event = customer-on
add name = mati1431-0859 start-time = 14:31:00 \
interval = 1d on-event = customer-off
--------------- O ------------
The other method, in theory (Halah) can be done with such an idea:
* Set on the Local Interface or Interface is used as a gateway by our Client, with its ARP Reply Status Only. Furthermore we statiskan IP ARP List. Well, with a mode such that only a registered client MAC and IP addresses that can pass Addressnyalah Internet connection. So you can also create a script to disable the IP and ARP mengenable List, then contrived skedulnya the Scheduler.
* Set the Queue, whether it's Simple Queue or Queue Tree, with a large decrease packet traffic passing by, let alone given at 8kb. As for the hours normally set to the beginning of the packet. So the connection as "gag"
* Set the IP Filter Firewall Input Rules give the chain to the customer's IP address, if you need to set any given port, then give the Action Drop, if you want to pass more traffic on the ACCEPT of course on the Action. Note, Mikrotik seems to read the rule in sequence from top to bottom, as if the interpreter is Languange programming. Drop Rule so that the set position at the top of the action other than Drop rule.
Which method is effective, it seems to try too, hehehe.
Please try, but do not in any use.
Labels:
Network
Thanks for reading Tips n Tricks Timer in Mikrotik.. Please share...!
0 Komentar untuk "Tips n Tricks Timer in Mikrotik."