Garrett Reid <garrett.reid@gmail.com> on Tuesday, February 27, 2007 at 11:10 AM -0800 wrote:
I have a fairly fresh macports install, but a few parts seem broken. Any help would be much appreciated.
tcptraceroute doesn't work. On a tcptraceroute google.com, I get: libnet_write failed? Attempted to write 40 bytes, only wrote -1
I saw this too. There was a patch to libnet11's configure.in committed some time ago that was supposed to fix this. But it looks like autoconf is not run so it doesn't take effect. I inserted: use_autoconf yes into the libnet11 portfile and uninstalled, cleaned, reinstalled and now tcptraceroute works on my MacBook. If someone can confirm this the fix could be committed. I know Toby won't mind someone else committing the change, because I've emailed him in the past for this port. But I'm leaving town tonight and I don't want to make any changes now for safety's sake. But try it and someone else could commit it.
When I install ophcrack, it installs fine, but then won't run: Xlib: connection to ":0.0" refused by server Xlib: No protocol specified (ophcrack:11749): Gtk-WARNING **: cannot open display:
You need X11 running and this line in your shell environment. export DISPLAY=:0.0 See here: http://trac.macosforge.org/projects/macports/wiki/InstallingMacPorts
I have installed (installed in this order): wireshark ettercap-ng hping2 tcptraceroute (deactivated libnet11, activated libnet for dsniff) dsniff ophcrack
Perhaps we need to make libnet11 and libnet compatible like the FreeBSD and OpenBSD projects have done. Mark