The IP address that was issued by WAN2 still applies to all connected devices.
config redirect
option name 'Rewrite secondary WAN IP to LAN host'
option proto 'all'
option src 'wan'
option src_dip '**.***.**.223' # WAN2 ip
option dest_ip '192.168.1.229' # LAN ip
option target 'DNAT'
config nat
option name 'Rewrite LAN host to secondary WAN IP'
option src 'wan'
option src_ip '192.168.1.229' # LAN ip
option snat_ip '**.***.**.223' # WAN2 ip
option target 'SNAT'
list proto 'all'
I am not sure what you mean with "applies to all connected devices". Do you mean it is used as source IP for outgoing traffic?
In your "wan2" interface, advanced settings uncheck both "Use default gateway" and "Use DNS servers advertised by peer". See if it solves it.
You can also replace '**.***.**.223' with a literal wan2 in the firewall rules. This way the IP should be automatically derived from the interface so you do not need to update the config in case it ever changes.
Yeah, likely because the WAN2 default route overwrote the WAN one and now after disabling it you have none. Either try reconnecting WAN after disabling the default gateway on WAN2 or reboot the entire router.
Yeah... that is likely caused by the other SNAT rule rewriting all outgoing traffic from 192.168.1.229 to your other *.*.*.223 WAN IP, due to that all ports forwards from the primary WAN IP to this LAN host will likely fail.
There is no good clean solution to this I can think of. If you don't care whether your 192.168.1.229 LAN host uses the primary or secondary WAN IP for internet browsing you could try disabling/removing the SNAT rule.