Re: Unexpected behavior after altering inetsw[] switch table

2006-06-11 Thread Max Laier
On Sunday 11 June 2006 14:29, Shaun Colley wrote: > Hi Max & group, > > > As you can see in netinet/in_proto.c, tcp does not use pr_output, but > > calls > > tcp_output() directly where needed. Depending on what you want to achive > > it > > might be enough to hack up tcp_usr_send() and replace >

Re: Unexpected behavior after altering inetsw[] switch table

2006-06-11 Thread Shaun Colley
Hi Max & group, > As you can see in netinet/in_proto.c, tcp does not use pr_output, but > calls > tcp_output() directly where needed. Depending on what you want to achive > it > might be enough to hack up tcp_usr_send() and replace tcp_usrreqs.pru_send > instead. Replaceing tcp_output() is not e

Re: Unexpected behavior after altering inetsw[] switch table

2006-06-11 Thread Max Laier
On Sunday 11 June 2006 02:36, Shaun Colley wrote: > I'm writing a kernel module whose job is to modify the inetsw[] switch > table for the IPPROTO_TCP protocol. The pr_output hook for TCP needs to > be changed, such that my own custom tcp_output function will be called > when transmitting TCP pack