Hello,
I’m discovering https://wiki.mikrotik.com/wiki/Manual:Performance_Testing_with_Traffic_Generator.
I tried to reproduce these tests in my lab but failed miserably
Before defining tests with
/tool traffic-generator packet-template
commands, what are the appropriate set of commands to run on Trafic Generator box to check network settings are correct ?
For instance, test r12 is about sending traffic to destination 2.2.2.2 passing through gateway 1.1.1.254.
- Is the command bellow expected to succeed ?
/ping src-address=1.1.1.1 interface=ether5 2.2.2.2
- How can I make sure the traffic in the above command passes through DUT and not using Traffic Generator “internal routes” ? (I can plug a cable on or off while ping is running but …)
Best regards
I could at last get some positive testing.
Referring to [1], I simply had to run both r12 and r21 traffic to have “quick tx-template …” command stop displaying “100% Lost”.
(Previously, I ran r12 traffic alone, as a first step).
I hope this would help others
[1]https://wiki.mikrotik.com/wiki/Manual:Performance_Testing_with_Traffic_Generator
Here’s an alternative for sending traffic between two directly connected devices.
DUT IP- x.x.x.x/xx
TG IP- x.x.x.y/xx
You can create single packet template on TG:
/tool traffic-generator packet-template add ip-dst=x.x.x.y ip-gateway=x.x.x.x ip-src=x.x.x.y
This will send traffic from TG, through DUT and back to TG.
Am I correct this only involves one DUT interface ?
When would prefer to use such traffic as opposed to traffic going in through one interface and leaving through another ?