On Thu, 17 Feb 2005, Steve Iribarne wrote:
Hi guys. I'm back! :)
I have written a netfilter "hook" for the 127 net. I basically setup a post route hook. I check to see if it is on the 127 net I want. I think the problem I have is a bit more complicated than I thought.
So "users" of my system, basically applications, will need to talk out the 127.100 network (I'm going to leave the 127.0.0.1 alone).
So my understanding was this:
1. Write a nf_ip_post_routing filter. 2. Check if the out device my "lo" interface. 3. Check if the dest/src addresses are for the 127.100 net.
** this is where it gets hairy **
4. It's for the 127.100 net. 4a. I need to resolved the IP Address. 4b. I need to add that value to an arp cache. 5. Fill in the Src/Destination Mac addresses along with the source/dest IP addresses. (because as a loopback device, the src = dest).
What I am missing from this picture is what you want to happen with the packet, or why you at all need to write your own netfilter module...
Regards Henrik - To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
