There are control packets which don't have payload, and data packets which have the application data after the header.
On Fri, Jul 15, 2016, 20:32 Guy Harris <g...@alum.mit.edu> wrote: > On Jul 15, 2016, at 7:32 AM, Gerard Garcia <ggar...@abra.uab.cat> wrote: > > > vSockets are used for host<>guest communication using the standard > socket API. They already supported in the mainline Linux kernel and can be > used in VMware VMs. > > > > There is an ongoing work to implement a virtio transport which will add > vSockets support to QEMU. Additionally, it will include a vsockmon device > that will allow the host to monitor the data exchanged through vSockets. > > > > The vsockmon device has already been reviewed and its header is already > defined: > > > > http://marc.info/?l=linux-netdev&m=146661193816961&w=2 > > > https://github.com/GerardGarcia/linux/blob/vsockmon/include/uapi/linux/vsockmon.h > > So what follows the header? I.e., what's the payload of a vSocket packet? > _______________________________________________ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
