Long story short, tcpreplay allows users to replay traffic in "verbose
mode" which basically involves forking tcpdump and writing each packet
over a socketpair(). This has worked for quite a while (years now)
but recently I've realized something broke along the way and I'm at a
loss to as why.
Ba
On Aug 22, 2010, at 4:15 PM, Aaron Turner wrote:
> Long story short, tcpreplay allows users to replay traffic in "verbose
> mode" which basically involves forking tcpdump and writing each packet
> over a socketpair(). This has worked for quite a while (years now)
> but recently I've realized som
On Mon, Aug 23, 2010 at 12:08 PM, Guy Harris wrote:
>
> On Aug 22, 2010, at 4:15 PM, Aaron Turner wrote:
>
>> Long story short, tcpreplay allows users to replay traffic in "verbose
>> mode" which basically involves forking tcpdump and writing each packet
>> over a socketpair(). This has worked fo
So building the latest tcpdump from git and it won't link against the
latest libpcap from git:
ld: warning: in /usr/local/lib/libpcap.dylib, file was built for
unsupported file format which is not the architecture being linked
(i386)
running file against the actual file (libpcap.dylib is a symlin
On Aug 23, 2010, at 8:30 PM, Aaron Turner wrote:
> So building the latest tcpdump from git and it won't link against the
> latest libpcap from git:
>
> ld: warning: in /usr/local/lib/libpcap.dylib, file was built for
> unsupported file format which is not the architecture being linked
> (i386)
>
Grrr, it's "git pull" not "git fetch". libpcap tree was out of date
and that seems to be the cause of the problem. Thanks for the help,
sorry about the crappy bug report.
--
Aaron Turner
http://synfin.net/ Twitter: @synfinatic
http://tcpreplay.synfin.net/ - Pcap editing and replay tool
> "Aaron" == Aaron Turner writes:
Aaron> Grrr, it's "git pull" not "git fetch". libpcap tree was out
Aaron> of date and that seems to be the cause of the problem.
Aaron> Thanks for the help, sorry about the crappy bug report
Yes.
git pull == git fetch then git merge
--
]
