Still get no results for dst-nat. Thing is, it's very simple to reproduce by anyone who has any MT device. Commands below are for devices with at least 2 ethernet ports, otherwise you need to change ether2 for example to wlan1.
/system reset-configuration no-defaults=yes skip-backup=yes
/interface bridge add name=bridge1
/interface bridge port add bridge=bridge1 interface=ether1
/interface bridge port add bridge=bridge1 interface=ether2
/interface bridge nat add chain=dstnat action=dst-nat to-dst-mac-address=DST_MAC dst-mac-address=!FF:FF:FF:FF:FF:FF/FF:FF:FF:FF:FF:FF mac-protocol=!arp
Comments:
dst-mac-address=!FF:FF:FF:FF:FF:FF/FF:FF:FF:FF:FF:FF - not to lose communication with MT (connecting to MAC address is via broadcast)
mac-protocol=!arp - to be sure that problem is not arp issue
DST_MAC - is MAC of a device able to monitor traffic: tcpdump, Wireshark, MT with Torch, etc.
Now we ping any host behind the MT:
1. When out-interface is different from in-interface - redirection works OK.
2. When out-interface is same as in-interface - packets are dropped.
Topology:
1a. Pinging host on ether1, monitoring host on ether2, pinged host on ether2
1b. Pinging host on ether1, monitoring host on ether3, pinged host on ether2
2. Pinging host and monitoring host on same interface.
You do not have the required permissions to view the files attached to this post.