I am affraid of asymmetric routing problem here.
Also will Mikrotik keep tracking all connections from both directions between each public ip and its own related (translated) internal ip.
Yes, this works automatically, NAT is a property of connection tracking, so no worry here.
The nth method is for load balancing....I have to check it also for this purpose here.
That does not mean that it would not work here. The
table is only passed by packets with
. The only issue is that the way I've quickly put them they wouldn't distribute the traffic among the addresses evenly because there is no
table, so you would have to order them, top to bottom,
The easiest solution, will be to use a script that changes each hour for example the srcnatted public ip.
It would work but I cannot see the sense if you would rotate the addresses that slowly. Normally you use several src-nat addresses to have a larger pool of ephemeral TCP ports. Plus you'd brush the disk
Instead of writing novels, post /export hide-sensitive. Use find&replace in your favourite text editor to systematically replace all occurrences of each public IP address potentially identifying you by a distinctive pattern such as my.public.ip.1.