[tcpdump-workers] setsockopt with Netlink socket

filter options in the netlink socket case ? As this time the packet queued in netlink socket have some extra details appended, wont this be a problem ? Please guide appropriately Thanks in advance Madhuresh - This is the tcpdump-workers list. Visit https://cod.sandelman.ca/ to unsubscribe.

Re: [tcpdump-workers] why not filtering at driver level ?

come from driver/kernel side. Then libpcap will simply read it up (using PF_PACKET ??). 2. Netlink socket between libpcap and driver code. Can you suggest which option is better and what can be possible issues with the implementation. Thanks again -Madhuresh Guy Harris wrote: On Oct 23

Re: [tcpdump-workers] why not filtering at driver level ?

Guy Harris wrote: madhuresh wrote: I am just anxious to know that why we do filtering of packets at user space and not at driver level (kernel space). Because, on those OSes where filtering is done in user space, the OS and drivers either don't have a filtering mechanism or don'

[tcpdump-workers] why not filtering at driver level ?

filter options) to kernel as other applications might be waiting for these packets. So is it possible to transfer only filtered packets to the libpcap under the constraint of above statement ? How ? Please answer. Thanks -Madhuresh - This is the tcpdump-workers list. Visit https

[tcpdump-workers] libpcap + netlink socket

read the packet from netlink socket created between it and the driver. Let me know if i am thinking correctly and is it feasible. A quick reply will be highly appreciated. Thanks -Madhuresh PS: Please forgive me for poor english - This is the tcpdump-workers list. Visit https

[tcpdump-workers] libpcap: Reading from driver

ncluding 802.11. Please let me know what major changes in libpcap i have to do in connection with this approach. Also in case there are some other ideas please let me know. It kindaa urgent, so a quick reply will be highly appreciated. Thanks -madhuresh - This is the tcpdump-workers list. Vis

Re: [tcpdump-workers] libpcap : Reading from kernel interface

Guy Harris wrote: madhuresh wrote: Yes you are right. I was mentioning about hostap-driver-0.4.7 which works as a module with linux kernel. (The linux-2.6.17.3 kernel has a drivers/net/wireless/hostap directory. What's the difference between that driver - or any versions from later

Re: [tcpdump-workers] libpcap : Reading from kernel interface

interface. Please let me know if i am thinking in the right direction. Any other nice approach to get these extra details from kernel space to user space ? - This is the tcpdump-workers list. Visit https://cod.sandelman.ca/ to unsubscribe. -- Madhuresh Agrawal Senior Undergraduate Dep