Hey,
I was reading and implementing this (https://github.com/RMerl/asuswrt-merlin/wiki/Using-ipset) and noticed that when you actually use the iptables command with the --match-set flag, the command does not process because the --match-set flag is invalid or isn't implemented in the firmware.
My firmware is: 378.56_2 / ASUSWRT-Merlin RT-N66U_3.0.0.4 Wed Nov 4 02:03:42 UTC 2015
http://10.10.10.1/Advanced_FirmwareUpgrade_Content.asp
An example of the issue:
This same command would work perfectly fine on my linux box, so I am wondering if there is something wrong (or missing) with the implementation in merlin-wrt.
I was reading and implementing this (https://github.com/RMerl/asuswrt-merlin/wiki/Using-ipset) and noticed that when you actually use the iptables command with the --match-set flag, the command does not process because the --match-set flag is invalid or isn't implemented in the firmware.
My firmware is: 378.56_2 / ASUSWRT-Merlin RT-N66U_3.0.0.4 Wed Nov 4 02:03:42 UTC 2015
http://10.10.10.1/Advanced_FirmwareUpgrade_Content.asp
An example of the issue:
Code:
knight:/tmp/home/root# iptables -I FORWARD -m set --match-set MicrosoftSpyServers dst -j DROP
iptables v1.3.8: Unknown arg `--match-set'
Try `iptables -h' or 'iptables --help' for more information.
This same command would work perfectly fine on my linux box, so I am wondering if there is something wrong (or missing) with the implementation in merlin-wrt.