On Sep 13, 2011, at 11:16 PM, Erik Hjelmvik wrote: > The reason for why it would be great to have in tcpdump is because > tcpdump is an ubiquitous tool that is available practically everywere.
tcpdump-with-pcap-over-IP-support is a non-existent tool that is available nowhere. :-) If the tcpdump distribution (or the libpcap distribution) were to ship with pcap_over_ip_d, it would probably become a tool that's exists on all platforms that would have had tcpdump-with-pcap-over-IP-support had such a program would have been shipped. > Besides, there's nothing that would prevent tcpdump from being at the > receiving end of a "Pcap-over-IP" TCP socket. If by "receiving end" you mean that side that receives a stream of packets, no, nothing prevents that - and implementing the *sending* end in tcpdump would neither help nor hinder that; they're orthogonal. In any case, the receiving end arguably belongs in libpcap/WinPcap, so that other programs using libpcap could also be changed to support receiving pcap-over-IP streams. > However, I fully understand if you feel implementing a TCP listener or > TCP client in tcpdump would be a digression from the intended > functionality of tcpdump. I think it a pcap-over-IP packet sender would be a useful tool to put into either the tcpdump or libpcap project, but I don't see any reason why it necessarily needs to be a part of the tcpdump program.- This is the tcpdump-workers list. Visit https://cod.sandelman.ca/ to unsubscribe.
