This interface list row is definitely an error - my script should have changed
ether10 to
wan2-100 on it. I've tested it on my lab CHR and it worked, interesting.
Nevertheless, this does not explain why you cannot ping the LTE IP. So once you fix that row, make the command line window as wide as your screen allows, run
/tool sniffer quick ip-address=192.168.9.1 in it, and start pinging 192.168.9.1 from a PC connected to a bridge port of the 3011. If everything was OK, you would see the following:
etherX ... <- ... ip.of.the.pc 192.168.9.1 ... ip:icmp
bridge ... <- ... ip.of.the.pc 192.168.9.1 ... ip:icmp
wan2-100 ... -> ... 192.168.9.2 192.168.9.1 ... ip:icmp
bridge ... -> ... 100 192.168.9.2 192.168.9.1 ... ip:icmp
ether10 ... -> ... 100 192.168.9.2 192.168.9.1 ... ip:icmp
ether10 ... <- ... 100 192.168.9.1 192.168.9.2 ... ip:icmp
bridge ... <- ... 100 192.168.9.1 192.168.9.2 ... ip:icmp
wan2-100 ... <- ... 192.168.9.1 192.168.9.2 ... ip:icmp
bridge ... -> ... 192.168.9.1 ip.of.the.pc ... ip:icmp
etherX ... -> ... 192.168.9.1 ip.of.the.pc ... ip:icmp
But I assume you actually get
etherX ... <- ... ip.of.the.pc 192.168.9.1 ... ip:icmp
bridge ... <- ... ip.of.the.pc 192.168.9.1 ... ip:icmp
ether1 ... -> ... 192.168.8.2 192.168.9.1 ... ip:icmp
In another words, this has nothing to do with moving the WAN 2 configuration from bare
ether10 to
wan2-100, it's your PCC rules that causes this. When you ping from a PC, the PCC rule in mangle.forward may assign a
connection-mark value
WAN1_conn, which one of the subsequent rules translates to
routing-mark value
to_WAN1.
And since ICMP uses no ports, the result of the PCC evaluation only depends on source and destination addresses, so you get always the same result when pinging from the same PC.
You've fallen into the same rabbit hole like many others - the match condition
dst-address-type=!local matches on any other destination address than one of the router's own ones, so it does not prevent the rule assigning WAN1_conn from acting on packets towards 192.168.9.1.
So add all the connected subnets (192.168.8.0/24, 192.168.9.0/24, 172.16.10.0/24, 10.0.0.0/24) to an address-list called
connected-subnets and replace
dst-address-type=!local in the PCC rules by
dst-address-list=!connected-subnets.