I've come across a packet that causes me to get a stack trace something
like this:
#0 0x in ?? ()
#1 0x0807a0bd in handle_ctrl_proto (proto=32855, pptr=0x8195c82 "\001", length=14) at
print-ppp.c:450
#2 0x0807be24 in handle_ppp (proto=32855, p=0x8195c82 "\001", length=14) at
print-ppp.
On Mon, Jul 12, 2004 at 03:13:33PM +0200, Klaus Schrod wrote:
> Does anybody have any idea why we still get this error?
Because, for whatever reason, the dissector for the protocol atop which
the purported IP traffic is running thinks it's IP even though it isn't?
(The version field has 11, not 4
Hello,
I created a new tcpdump 3.8.1 with libpcap 0.8.1 (last stable versions
at sourgeforge).
I tried to catch ipsec's ESP protocol traffic between two computers. One
side is connected with a DSL router and a fixed ip address to the net
and the other side is connected with pppoe.
As a test I
