> Do you think, that such approach may be extended to unix-domain > traffic as well, or there are other ways to sniff such packets?
I don't know if similar things exists or have existed for UNIX sockets. That could be useful having an infrastructure that'll enable to redirect certain socket type traffic to a virtual netdev. Is it something that has already been discussed here ? > Security people will cry, but sometimes we need good troubleshooting > means in userland. Yes, the deed is to enable netlink troubleshooting from kernel and userland (and to learn more about the kernel actually). I'm aware that hooking af_netlink.c methods may not be very standard and is probably not done in a safe way. That's why I'm looking forward for any comments about how to do things properly. What I feel is done awkwardly is : * not setting up the interface flags (up & running by default on my setup) * no tasklet scheduling, does it have to be envisaged for such interface type ? * having to do by hand a dev_queue_xmit + dev_put (refcnt problems in the past) * interface name hardcoded Cheers -- Mathieu Geli - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
