My main concern is about whether I should state nat dual-dsthost or nat dual-dsthost ingress, as I've seen in some other threads.
The same goes for nat dual-srchost.
So this really depens on where eth0.2 is facing towards. Your current config will equalize incoming (ingress) packets by their destination (dst) IP address after NAT, and outgoing packets (egress) by their source (src) IP address after NAT. If eth0.2 is your WAN interface than this will make sure all active internal IP addresses will share the available capacity equitably. If however eth0.2 points into your LAN you will share capacity equitably between external IP addresses...
Just post the output of ifstatus wan | grep -e device to confirm whether or not eth0.2 is your WAN interface....
I believe it is, since I have the modem in bridge mode.
Besides, WAN shows an external IP in Luci -> Network -> Interfaces, which I believe confirms it.
Yes, so your configuration should result in fair/equitable sharing between all internal hosts. Does this match in what you see? E.g. run concurrent speedtests on two different computers and look how much bandwidth each gets...
I would recommend a longer running data transfer for that purpose, like Belwue's:
time wget -O /dev/null http://speedtest.belwue.net/10G --report-speed=bits
I guess so, since so far none of the connected devices seemed to suffer from lack of bandwidth.
Thanks. I had two linux devices downloading that 10G file simultaneously, and also turned on a Netflix stream.
Netflix worked as expected, and it showed bandwidth usage of 6 Mbps
The two Belwue's flows were downloading but with download speed floating highly.
I ran this for about 4 minutes.
In summary, it seems to be working as expected, I guess.
EDIT: Out of curiosity, and in case it might interest someone, a 24-hour monitoring window, where the test above shows clearly as pointed by the arrow: