Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!sdd.hp.com!spool.mu.edu!uunet!stanford.edu!morrow.stanford.edu!pangea.Stanford.EDU!farrell
From: farrell@pangea.Stanford.EDU (Phil Farrell)
Newsgroups: comp.unix.ultrix
Subject: packetfilter and LAT bug
Message-ID: <1991May9.185718.25580@morrow.stanford.edu>
Date: 9 May 91 18:57:18 GMT
References: <1991May7.141459.11191@fcom.cc.utah.edu> <tih.673686101@barsoom> <1991May8.230816.25416@pa.dec.com>
Sender: news@morrow.stanford.edu (News Service)
Organization: Stanford Univ. Earth Sciences
Lines: 22

In article <tih.673686101@barsoom> tih@barsoom.nhh.no (Tom Ivar Helbekkmo)
writes:
>I set up my packet filter to run in promiscuous mode here yesterday, on
>a 5000/200 with 4.1, and our whole VAXcluster (VMS) started crashing like
>nobody's business...  I've heard that promiscuous mode will break LAT if
>you've got LAT installed on the Ultrix host running it, which I haven't,
>but I'm wondering if it still may have been my experimenting that killed
>the VAXen.  We use LAT very extensively, in fact 3 out of every 4 packets
>on our ethernet are LAT packets.  Anybody know anything about it?
>
In reference to an unrelated kernel problem on my DECsystem 5810
running RISC Ultrix, I saw (but was not able to copy) one of those DEC
"for internal use only" memos listing all current patches to RISC
Ultrix 4.1.  One of them was a kernel patch that specifically addressed
this issue of promiscuous mode packet filter incompatibility with LAT.
I don't even recall the name of the routine, unfortunately, but I think
it is time for everyone who has reported this problem on the net to
start harassing DEC Ultrix support to get this patch.

-Phil Farrell, Computer Systems Manager
Stanford University School of Earth Sciences
farrell@pangea.stanford.edu