Tue May 29, 2018 12:23 am
Concur using RAW perhaps for both instances....
For the original OP, one could make the rules in RAW and thus block any communication input, forward etc....
/ip raw
add chain=prerouting source-address-list=Block Addresses action=drop log yes logprefix="Stopped the SOB COLD again"
For the follow-on query...... I dont think one can actually state a port without a protocol??
Also i am not sure what you mean by range?? Do you mean an LAN IP on your network, or a WAN IP that people connect to.
Seeing as its a 192.168 type of private address I suspect the former as I do not think that is a legitimate WAN IP.
The problem with that is what is to stop the offending person from attempting to get another private IP on your LAN to conduct this ugly affair.
/ip raw
add chain=prerouting protocol tcp dest-port 8292 action=drop logyes logprefix="Not on my Watch Sucker"
add chain=prerouting protocol udp dest-port 8292 action=drop logyes logprefix="Not on my Watch Sucker"
Be aware that this stops any traffic to or from the router and LANS by anyone using that port as a destination.
If you wanted to isolate it to the the LAN, include in-interface-list=LAN
What I am not sure is if this approach is valid at stopping layer 2 traffic between two IPs on the same LAN?????
As stated what if the program allows the person to change the port used for this purpose.
It may be best to find a way to separate this user silently from the rest of the network.
Doing this at layer 3, firewall rule is easy, BUT doing it at layer 2 means somehow you have to push him to a different layer 2 container, like a lan on a bridge or a VLAN..
I will let the gurus chime in if thats a feasible approach?