Guy Harris writes:
> so the mmap interface should work between a 64-bit kernel and 32-bit
> userland *if* the kernel supports TPACKET_V2, as libpcap should choose
> TPACKET_V2 rather than TPACKET_V1 if TPACKET_V2 is supported. I'd need
> to know what version of the kernel is running on the system
On Feb 1, 2012, at 11:12 AM, Guy Harris wrote:
> so the mmap interface should work between a 64-bit kernel and 32-bit userland
> *if* the kernel supports TPACKET_V2, as libpcap should choose TPACKET_V2
> rather than TPACKET_V1 if TPACKET_V2 is supported.
I tried building 32-bit versions of top
On Feb 1, 2012, at 5:32 AM, Michael Richardson wrote:
> No, openvz is a container, not a virtualization.
As I suspected.
> So the kernel is 64-bit, the userland in a chroot/jail+++ is 32-bit.
> The kernel would be doing 32-bit emulation of many calls, but I'll bet
> things like the mmap() inter
> "Guy" == Guy Harris writes:
Guy> On Jan 31, 2012, at 11:31 PM, Graeme Sheppard wrote:
>> I have a problem capturing in a 32 bit guest on a 64 bit
>> VZ/OpenVZ host. It worked in a 64 bit guest but I had to change
>> to 32 (another story.)
Guy> So the host on which you
On Feb 1, 2012, at 12:26 AM, Guy Harris wrote:
> On Jan 31, 2012, at 11:31 PM, Graeme Sheppard wrote:
>
>> I have a problem capturing in a 32 bit guest on a 64 bit VZ/OpenVZ host.
>> It worked in a 64 bit guest but I had to change to 32 (another story.)
>
> So the host on which you're capturing
On Jan 31, 2012, at 11:31 PM, Graeme Sheppard wrote:
> I have a problem capturing in a 32 bit guest on a 64 bit VZ/OpenVZ host.
> It worked in a 64 bit guest but I had to change to 32 (another story.)
So the host on which you're capturing is running a 32-bit Linux kernel and a
32-bit version of
Hi,
I have a problem capturing in a 32 bit guest on a 64 bit VZ/OpenVZ host.
It worked in a 64 bit guest but I had to change to 32 (another story.)
The software can tell the captured data is there but chokes or aborts on
it. Here are a couple of pings then a fatal web request.
# ./tcpdump -f 'no