Hey Jan, You see I am reading so much, and finding all these different ways. It's getting kind of confusing. Here is what I wrote in another mail, which should clarify my situation: "I have a pc in a LAN. I need to redirect all my outgoing traffic to different pcs over the lan.(The thing is that of all the pcs which I have selected only 1 of them should receive one packet). These pcs will direct all my traffic to the required destination. This is what I have figured out: Since I need to re-direct my outgoing traffic to different PCs I'll have to work my way on the Layer 2. So arptables is probably the best way to do it. Secondly I need to create a target extension which takes the first frame and sends it over to pc1, takes the second frame and sends it to pc2 and so on.(Obviously once the total number of pcs are over, it loopbacks). This is something like the nth patch in iptables but not the same. Finally once I build this target extension I would like to build it. So that I can use it in arptables. " This is what I have my eyes set on right now. xt_TEE seems interesting. Should I switch over to that instead? Could you describe in detail as what procedure I need to follow. It would be great help. Yours, Digvijay On Tue, Apr 3, 2012 at 5:53 PM, Jan Engelhardt <jengelh@xxxxxxxxxx> wrote: > On Tuesday 2012-04-03 02:01, Stephen Hemminger wrote: > >>> I am working on a project to create a kernel module which directs all >>> outgoing traffic from my machine to different computer in my LAN. So I >>> am starting with just trying to send the traffic to just one computer. >>> I am using the NF_BR_LOCAL_OUT hook. Along with the NFPROTO_IPV4 >>> family. But every time i run the module, my machine hangs. And I need >>> to reboot. Please see what is the problem. >> >>tc action redirect already does this > > As does xt_TEE which, at the same time, is likely to be easier to > handle. -- To unsubscribe from this list: send the line "unsubscribe netfilter" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
