On Mon, Mar 18, 2013 at 11:08 PM, Wesley Shields w...@freebsd.org wrote:
On Fri, Mar 15, 2013 at 06:37:25PM -0700, Guy Harris wrote:
On Mar 15, 2013, at 2:45 PM, Michael Richardson m...@sandelman.ca wrote:
wen == wen lui esolvepol...@gmail.com writes:
wen I used libpcap function
On Thu, Mar 21, 2013 at 01:03:56PM -0400, Bill Fenner wrote:
On Mon, Mar 18, 2013 at 11:08 PM, Wesley Shields w...@freebsd.org wrote:
On Fri, Mar 15, 2013 at 06:37:25PM -0700, Guy Harris wrote:
On Mar 15, 2013, at 2:45 PM, Michael Richardson m...@sandelman.ca wrote:
wen == wen lui
On Fri, Mar 15, 2013 at 06:37:25PM -0700, Guy Harris wrote:
On Mar 15, 2013, at 2:45 PM, Michael Richardson m...@sandelman.ca wrote:
wen == wen lui esolvepol...@gmail.com writes:
wen I used libpcap function pcap_next() to capture some tcp packets
wen I checked the bytes of the
I used libpcap function pcap_next() to capture some tcp packets I checked
the bytes of the captured packets and notice that the ethernet and ip
header of packets are distorted, in a mess with a lot 0's but the TCP
header is fine
what are potential reasons for this?
On Mar 15, 2013, at 9:07 AM, wen lui esolvepol...@gmail.com wrote:
I used libpcap function pcap_next() to capture some tcp packets I checked
the bytes of the captured packets and notice that the ethernet and ip
header of packets are distorted, in a mess with a lot 0's but the TCP
header is
wen == wen lui esolvepol...@gmail.com writes:
wen I used libpcap function pcap_next() to capture some tcp packets
wen I checked the bytes of the captured packets and notice that the
wen ethernet and ip header of packets are distorted, in a mess with
wen a lot 0's but the TCP
On Mar 15, 2013, at 2:45 PM, Michael Richardson m...@sandelman.ca wrote:
wen == wen lui esolvepol...@gmail.com writes:
wen I used libpcap function pcap_next() to capture some tcp packets
wen I checked the bytes of the captured packets and notice that the
wen ethernet and ip header
