tag:blogger.com,1999:blog-6811336968619276420.post946040067820821118..comments2024-01-15T23:42:40.807+10:00Comments on H. Mijail's Blog: Tcpflow and connections between local interfacesHoracio Mijailhttp://www.blogger.com/profile/10941261506308268725noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-6811336968619276420.post-25968829306072335532012-01-19T06:48:53.392+10:002012-01-19T06:48:53.392+10:00Confirmed, it was a bug in tcpflow. Fixed in a mod...Confirmed, it was a bug in tcpflow. Fixed in a modified (not the official) 1.1.0-beta3, so it should be OK in the next official beta or release.<br />Doing a capture with tcpdump -i lo0 and then feeding the output file to tcpflow -r didn't work either, by the way.Horacio Mijailhttps://www.blogger.com/profile/10941261506308268725noreply@blogger.comtag:blogger.com,1999:blog-6811336968619276420.post-27850114039146947272012-01-16T09:46:59.609+10:002012-01-16T09:46:59.609+10:00Well, looks like the problem rather is in tcpflow,...Well, looks like the problem rather is in tcpflow, since tcpdump does show the packets being routed with -i lo0! I just sent a bug report to tcpflow's current maintainer...Horacio Mijailhttps://www.blogger.com/profile/10941261506308268725noreply@blogger.com