iglesias@draco.acs.uci.edu (Mike Iglesias) (01/16/91)
Does anyone know of/have changes to make tcpdump work under Ultrix 4.x? We're running 4.1 on DECstations if that makes a difference. A pointer to a program like tcpdump or Sun's etherfind would also be appreciated. Thanks, Mike Iglesias University of California, Irvine Internet: iglesias@draco.acs.uci.edu BITNET: iglesias@uci uucp: ...!ucbvax!ucivax!iglesias
iglesias@draco.acs.uci.edu (Mike Iglesias) (01/16/91)
In article <2793D979.17547@orion.oac.uci.edu> I wrote: >Does anyone know of/have changes to make tcpdump work under Ultrix 4.x? Ed Vielmetti pointed out that a new tcpdump was just announced that supports Ultrix 4.x. It's on ftp.ee.lbl.gov in tcpdump-2.0.tar.Z. Thanks Ed, for the quick (~20 minutes after I posted the request!) answer. Mike
mogul@wrl.dec.com (Jeffrey Mogul) (01/17/91)
In article <2793D979.17547@orion.oac.uci.edu> iglesias@draco.acs.uci.edu (Mike Iglesias) writes: >Does anyone know of/have changes to make tcpdump work under Ultrix 4.x? >We're running 4.1 on DECstations if that makes a difference. A pointer >to a program like tcpdump or Sun's etherfind would also be appreciated. Boy, do I ever! :-) Fortunately for you, I've been working on and off for months with the LBL crew to get their code to work on Ultrix 4.x. The release announced yesterday, available from ftp.ee.lbl.gov, compiles and runs just fine on Ultrix if you make the appropriate modifications to the Makefile. (They distribute a makefile that uses gcc, bison, and flex instead of cc, yacc, and lex, but all you have to do is change the Makefile symbols.) One problem: it really helps to have the "mkdep" command available if you want to use their Makefile, and vanilla Ultrix doesn't include "mkdep". So, I've put a version on gatekeeper.dec.com:pub/net/tcpdump-2.0.tar.Z that has an Ultrix-ready Makefile and includes the mkdep script. Just uncompress, unpack, and type "make". Note that binary files end up in a subdirectory called "mips-ultrix" or "vax-ultrix", as appropriate. My usual rule: don't ask me to mail you a copy. I won't respond. -Jeff
apt@menudo.uh.edu (Alan Pfeiffer-Traum) (01/17/91)
>>>>> On Thu, 17 Jan 91 01:14:50 GMT, mogul@wrl.dec.com (Jeffrey Mogul) >>>>> said: Mike> In article <2793D979.17547@orion.oac.uci.edu> Mike> iglesias@draco.acs.uci.edu (Mike Iglesias) writes: Mike> Does anyone know of/have changes to make tcpdump work under Ultrix Mike> 4.x? We're running 4.1 on DECstations if that makes a difference. Jeffrey> Fortunately for you, I've been working on and off for months Jeffrey> with the LBL crew to get their code to work on Ultrix 4.x. My thanks to Jeffrey Mogul for contributing his time adapting this wonderful tool (and for his earlier work on nfswatch). However, I should point out a nasty gotcha that appears when enabling the ethernet controller for promiscuous mode (using the packetfiler) under ULTRIX 4.1. If the system is also running LAT, you can expect to see *major* disruption to other LAT services on the LAN. This is a "known problem" as verified by the CSC ULTRIX Networking Team. I don't know the exact nature of the problem. But, in my case while I was running nfswatch DECserver users attempting to connect to various LAT services received a message indicating a "remote protocol error". I cleared this condition only by rebooting my system. This problem is peculiar to ULTRIX 4.1. I have seen no problems using the packetfilter under ULTRIX 4.0. The indications from CSC note that this problem is fixed in the next release (don't expect a patch). If you don't run LAT on your 4.1 system, promiscuous mode can be enabled without hazard to the innocent. However, in this case I've noticed that you can't *disable* promiscuous mode - short of rebooting. -- Alan Pfeiffer-Traum University of Houston