[EMAIL PROTECTED] wrote:
there is a debug variable in the sock structure that you can enable at
various points, and use in instrumentation to conditionally print out
data at various points. I usually turn in on in sys_socket, or
sys_connect, etc, based on information I have on hand at the time
> >>there is a debug variable in the sock structure that you can enable at
> >>various points, and use in instrumentation to conditionally print out
> >>data at various points. I usually turn in on in sys_socket, or
> >>sys_connect, etc, based on information I have on hand at the time
> >>(pr
[EMAIL PROTECTED] wrote:
Thx but this means that i must recompile the kernel...right?
I ll check it thx again
Quoting Neil Horman <[EMAIL PROTECTED]>:
Thats right. The only other thing I could think of (that doesn't
require kernel recompiles) would be to use iptables and the ip_queue or
ip_log t
Thx but this means that i must recompile the kernel...right?
I ll check it thx again
Quoting Neil Horman <[EMAIL PROTECTED]>:
> [EMAIL PROTECTED] wrote:
> > Hi... do u know how i can "watch" the path that a packet follows after it
> have
> > been received from the kernel?
> > I need a low level pa
[EMAIL PROTECTED] wrote:
Hi... do u know how i can "watch" the path that a packet follows after it have
been received from the kernel?
I need a low level packet debuger or something else that shows what a packet do
inside the kernel..
Any suggestion?
Thx
there is a debug variable in the sock struct
Hi... do u know how i can "watch" the path that a packet follows after it have
been received from the kernel?
I need a low level packet debuger or something else that shows what a packet do
inside the kernel..
Any suggestion?
Thx
Th
