Bug#734064: tcpflow with no -i doesn't work

2014-02-04 Thread Dan Jacobson
Good to know. > "SG" == Simson Garfinkel writes: SG> Thanks. Fixed in 9915ef4..9abeb43. SG> tcpflow now defaults to the default device if neither -i or -r is given. SG> On Jan 3, 2014, at 4:49 PM, jida...@jidanni.org wrote: SG> Well all I know is the man page perhaps should say where o

Bug#734064: tcpflow with no -i doesn't work

2014-01-03 Thread Simson Garfinkel
Thanks for the email. Unfortunately, I didn’t write the man page; that’s from the original developer. I’ll see if I can fix the code to mirror the behavior of tcpdump. On Jan 3, 2014, at 4:49 PM, jida...@jidanni.org wrote: > Well all I know is the man page perhaps should say where one can obt

Bug#734064: tcpflow with no -i doesn't work

2014-01-03 Thread jidanni
Well all I know is the man page perhaps should say where one can obtain a current list of interfaces to know what the choices are, so one doesn't try "localhost" instead of "lo" (not all of us are "regarded as a leader in the fields of Digital forensics and Usable Security."!!) -- To UNSUBSCRIBE

Bug#734064: tcpflow with no -i doesn't work

2014-01-03 Thread Simson Garfinkel
Thanks for the email. It seems that on your system there is no reasonable default. I’m thinking of removing the default action because it is confusing. That is, I’m thinking of making tcpflow without a -r or -i generate an error. This is because these days most computers have multiple internet

Bug#734064: tcpflow with no -i doesn't work

2014-01-03 Thread jidanni
Package: tcpflow X-Debbugs-Cc: sims...@acm.org Version: 1.4.3+repack1-1 Severity: minor File: /usr/share/man/man1/tcpflow.1.gz -i iface Interface name. Capture packets from the network interface named iface. If no interface is specified with -i , a reason-