This part will be an introduction of the Packet Generator/Injector feature that Skydive provide. We'll keep playing with the WebUI which allow us to get started smoothly. The goal of the Packet Generator is to forge packets and to inject them into an interface of the topology. Using this feature with the packet capture allow us to verify if the traffic is forwarded as expected.
Starting with the lab created in the previous part, two network namespaces with a `ShortestPath` capture, we are going to use the Packet Injector to generate pings instead of the "ping" utility.
For that purpose, on the WebUI, we just need to click on the `Generator` tab on the right panel. Here you can select the type of the packet that will be generated. For now we will use the default one. Then you have to select the source, the destination and the number of packets you want to generate. By default Skydive will use the first IP address available of the node, but you can change it. There are some other options like the delay between two packets or the payload length but for the demo we will use the default values.
As in the previous part, we can click on a node of the path to check if we see our generated packets.
Let's drop some packets
Now we can simulate an issue somewhere in order to see how we can detect where the issue occurs. For that we are going to add an iptables rule in order to drop traffic for specify TCP port. Let say the port 4567.Now we can use the generator or anything else like Netcat to generate some UDP or TCP packets, then we can refresh the flow view in order to check where our packets have been seen. It will confirm that the packets were dropped around the bridge `br0`.
We saw how easy it is to target where a packet is dropped. Of course this can be achieved with the Skydive client too. In the following part we will see how to use the client to get the same result.