mock@watt.support.Corp.Sun.COM (Joseph Mocker) (03/01/91)
I have encountered a rather strange problem with the Clarkson Packet driver for the 3c503 card...here it is... I've been dorking around with the TCP/IP protocols lately. I decided that I wanted to write a little TCP/IP watcher/analyzer. Since I didn't want to muck around with all that low level ethernet junk I picked up a copy of the Clarkson Pkt Drvrs and got to it. During my messing around, I found that there is a problem with the 3c503 packet driver in promiscuous mode. My program basically does the following: 1. find packet driver 2. get stats of interface: driver_info() 3. initialize IP packet watching: access_type() 4. retrieve all packets: set_rcv_mode() 5. loop 6. if packet available: display it 7. end loop What is happening is that after a while of chugging along, I stop receiving packets. If I quit the program and start it up (without rebooting) it will work for a while and stop again. I recently slapped a WD8003e in my machine, and my program chugged along like a charm. I even shoved a NI5010 in there and it hasn't had any problems either. (I used the packet drivers for each of these as well) I seem to have noticed that it hangs after receiving a 1500 byte UDP packet, but it doesn't happen on receiving all 1500 byte UDP packets. That is, it will sometimes receive these packets fine, and other times, just stop up. I think it is just a problem when the 503 is in promiscuous mode, I have used the packet drivers with the pc-nfs compatibility kit w/o any problems... Any Ideas??? -- ------------------------------------------------------------------------------ Joe Mocker//USAC//PC-NFS Support :: mock@Corp.Sun.COM :: Sun Microsystems Inc. :: there's still lofty dreams :: meager desires :: still sillyness ::
brotzman@nssdcb.gsfc.nasa.gov (Lee E. Brotzman) (03/02/91)
In article <MOCK.91Feb28220846@watt.support.Corp.Sun.COM>, mock@watt.support.Corp.Sun.COM (Joseph Mocker) writes... > >I have encountered a rather strange problem with the Clarkson Packet driver >for the 3c503 card...here it is... > [description of problem program deleted] > >What is happening is that after a while of chugging along, I stop receiving >packets. If I quit the program and start it up (without rebooting) it will >work for a while and stop again. I just put a 3c505 in my 386SX clone and I am experiencing similar problems. NCSA telnet seems to crash at random intervals (the clock in the lower right corner stops running, so it isn't just network lag time). FTP, Inc. telnet crashes also (in fact FTP's telnet goes down even earlier than NCSA). Anyone considering sending an answer to the original posting, please either post to the net, or cc: a copy of your E-mail to me, too. Thanks a bunch. -- Lee E. Brotzman Internet: brotzman@nssdca.gsfc.nasa.gov -- ST Systems Corp. SPAN: NSSDCA::BROTZMAN -- National Space Science Data Center BITNET: ZMLEB@SCFVM -- "My thoughts are my own" "Prayer: the last refuge of a scoundrel" -- Lisa Simpson, 1990
jbvb@FTP.COM ("James B. Van Bokkelen") (03/04/91)
I just put a 3c505 in my 386SX clone and I am experiencing similar
problems. FTP, Inc. telnet crashes...
You don't say if you're using our linked-in driver (PC-204) or the Packet
Driver (PC-210). If you're having problems with the Clarkson 3C505 Packet
Driver, I'd recommend trying the direct version (ask Tech Support for it),
because (since v2.05) it loads code onto the board to fix a number of bugs
in the on-board ROM driver that 3Com ships. 3Com gave us the down-load
module, but you'd need their permission to distribute source before the
Clarkson driver could be upgraded to use it. Alternatively, get 3Com's
NDIS driver for the board and use the DIS_PKT adapter module...
James B. VanBokkelen 26 Princess St., Wakefield, MA 01880
FTP Software Inc. voice: (617) 246-0900 fax: (617) 246-0901