Virtual Ethernet and VQManager
One of the interesting issues that I have resolved of late has been making the VQManager work in the Virtual Ethernet environment. For starters, the VQManager is a sniffing based application that relies on the packet capture functionality of the underlying kernel. Typically the VQManager sniffs ethernet packets, decodes them. The sniffed packet follows the order of Ethernet headers->Ip Headers -> UDP Header -> Payload (SIP/RTP etc.,). But in a Virtual ethernet, this packet format is a bit different. A Virtual Ethernet, as the name suggests is a virtual interface of the computer. Typical virtualization softwares (like VMware, OpenVZ, Virtuzzo etc.,) provides these options. Ie., the applications are NOT exposed to the 'real' Ethernet but a 'virtual' layer on top of that. Now, why did this Virtual Ethernet thing create issues with VQManager? Well, as mentioned earlier, the VQManager expects the packet to be of the order. In a virtual ethernet environment, the Eth