Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!network.ucsd.edu!news.cerf.net!ent-img.com!pete From: pete@ent-img.com (Pete Carah) Newsgroups: comp.os.386bsd.questions Subject: Problem with we0 and TCP Date: Wed, 21 Jul 1993 22:45:32 GMT Organization: CST Entertainment Imaging Lines: 25 Message-ID: <CAJDvw.95J@ent-img.com> Reply-To: pete@puffin.ent-img.com NNTP-Posting-Host: ent-img.ent-img.com I installed the 0.1-dist and am partway through the 0.2.3 patches (through 0100, not counting some compiler patches; I've replaced the compiler with 2.4.5 except for kernel compiles, as noted by others). I haven't gotten the 0.2.4 patches yet; should I abandon the 0.2.3 and start again on 0.2.4 or are they cumulative?) The first time I rebuilt the kernel (using GENERICISA as it came) the ability to connect with TCP went away. It does notice whether the remote socket is open or not; if it isn't I get an immediate reject message and if it is, then the connect just hangs. Ping works fine, so IP routing is not broken. Question is has anyone seen this before; In case it's from corrupted sources, I've downloaded the netinet directory from agate to compare and replace my copy with but haven't had time to do it. A related question which may have to do with the 8/16 bit bus problem but may not, since I'm not using the 8013 driver (but do have an 8013 card) is that we0 isn't recognized on a soft boot (even the automatic reboot after an unsuccessful fsck). I need to hard-reset the machine to get we0 recognized at all. All else works (and neither the 8013 ram or rom is configured at cxxxx. Haven't tried exxxx). -- Pete