Luigi Rizzo <ri...@iet.unipi.it> wrote:
mcr> So, basically if we use a device name like "netmap:" or "vale",
mcr> then we would get support for it. Are there dependancies that would
mcr> piss off distros that we should worry about? You say that we need
mcr> netmap,
mcr> but I don't see where in the build it references some new library.
> There isn't any new library, which eases distributing binaries.
> ./configure checks for the presence of the netmap headers,
> and if so compiles the extra file.
where do those headers come from? Would it make sense to just include
those headers with libpcap? That way netmap would always be available.
> At runtime, netmap only uses open(), ioctl(), mmap() and poll().
> Data structures are simple enough that a few macros
> or inline functions in netmap_user.h are all is needed
> to access the port and do I/O.
Are there any issues if someone makes tcpdump (or wireshark, or some other
libpcap using program) setuid? (I don't see any call to popen()...)
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] m...@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
_______________________________________________
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
