Add Network Telemetry Output to Packet Sender

[dannagle]

From the PR #197 from @packet46

As discussed previously on Social Media;

Can a network telemetry exporter option be added to Packet Sender? Since the application is creating (writing) the packet format, writing a second copy of the IP header information may be possible?

Telemetry output would need a configurable, separate target IP address (i.e. collector/bucket) which could then process the data and report on performance, security etc.

There are a number of formats of network telemetry but IPFIX is the IETF/IEEE open standard, also known as Flexible NetFlow 9 (FNF). Most vendors who run proprietary telemetry formats (NetFlow = Cisco, JFlow = Juniper, SFlow = Riverbed & others) are being asked to move toward IPFIX.. Cisco already have adopted IPFIX in parallel to NetFlow on their equipment.

This, in effect, would be a duplicate packet (64 bytes) created either as the original packet egresses the computer interface or as a copy of a log entry.

IPFIX offers a lot of scalable features to extract from the IP header in addition to the default 5 flow fields. If Packet Sender has all of this information then re-writing it to a separate entity (packet) could be an excellent addition to a Network Security Architect's tool bag.