Re: [tcpdump-workers] Regarding tcpdump pull request #614

2017-07-18 Thread alice-cyberreboot
Should be fixed now; I created the new pull request #615 and closed #614, so that I could use a different branch moving forward. Thanks for the guidance, Guy! --- šŸ™‹ al...@cyberreboot.org šŸ‘¾ Cyber Reboot Software Engineer @ In-Q-Tel -Original Message- From: Guy Harris [mailto:g...@alum.mi

Re: [tcpdump-workers] Regarding tcpdump pull request #614

2017-07-18 Thread alice-cyberreboot
Good point! Will fix this now. --- šŸ™‹ al...@cyberreboot.org šŸ‘¾ Cyber Reboot Software Engineer @ In-Q-Tel -Original Message- From: Guy Harris [mailto:g...@alum.mit.edu] Sent: Tuesday, July 18, 2017 4:41 PM To: alice-cyberreboot Cc: tcpdump-workers@lists.tcpdump.org Subject: Re: [tcpdump-w

Re: [tcpdump-workers] Regarding tcpdump pull request #614

2017-07-18 Thread Guy Harris
On Jul 18, 2017, at 12:44 PM, alice-cyberreboot wrote: > In our enhancements these flags are available both when reading from an > existing pcap file and when performing a live capture. The caveats are, this > currently works solely for the Ethernet link layer (the scope of our project), So if

[tcpdump-workers] Regarding tcpdump pull request #614

2017-07-18 Thread alice-cyberreboot
Hi everyone! I’m writing regarding a pull request I submitted (#614). My workgroup is currently working on a project utilizing machine-learning and software-defined networking to detect and respond to malicious network activity. We are currently focused on internal Ethernet traffic, and one of