Re: ifnet_input problem
Re: ifnet_input problem
- Subject: Re: ifnet_input problem
- From: Kevin Brock <email@hidden>
- Date: Fri, 24 Apr 2009 17:38:40 -0700
Terry Lambert wrote:
Probably a dumb question, but you said you recalculated the IP
checksum; did you also recalculated the TCP checksum, and did you do
it first, before the IP checksum?
Also, are you handling the source port redirect in the outbound
SYN/ACK? Maybe that's what's getting lost.
If I were doing this, I'd be doing two machine debugging of the NKE,
possibly even building my own kernel so I could add additional
instrumentation to see where things are failing.
I am doing two machine debugging. I've been debugging into the stack.
I'm starting to think that it's not what I thought it was. Debugging
through the stack things sometimes just, well, stop working. Maybe
because I'm using an Ethernet cable for the debugging... It looks like
the packet is getting farther than I thought, and the problem may lay
somewhere else. The debugging breakdowns in the stack were making it
look more complicated than it was--Heisenberg strikes again :-)
Thanks for the various suggestions.
Maybe using FirewireKDP will help with the problems debugging through
the network stack if I need to do that again.
Kevin
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden