it is so easy to find the offending parameter with a simple method : ELIMINATION
six parameters to verify
CUSTOMFORWARD : does the chain exist in v2 ?
-i wlan-1 -o wan-1 : well, optional, try without them
-j DROP : well this one as really a good chance to be exact
d ! 22.214.171.124/255.255.255.255 :
so many possibility to annoy iptables here. First the mask. In 100% systems, an IP is not a network. Perhaps iptables find now that this mask is an error. It may also find the syntax 255.255.255.255 long long and prefer shorter /240 /255. And last the 'not' ! Try whitout it.
Once you find what triggers the errors, the solution will come immediately. Three minutes max to solve except is the chain CUSTOMFORWARD moved
when you -A add a rule, you -D delete it immediatly, with same line just -A => -D