Date: Tue, 4 Apr 2000 18:34:51 -0700 From: Alfred Perlstein <bright@wintelcom.net> To: Jens Rehsack <rehsack@informatik.uni-halle.de> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: connection problem: FreeBSD Computer does not respond Message-ID: <20000404183451.Z20770@fw.wintelcom.net> In-Reply-To: <38EA8F06.7E09594D@informatik.uni-halle.de>; from rehsack@informatik.uni-halle.de on Wed, Apr 05, 2000 at 02:55:34AM %2B0200 References: <38EA7F40.FE128093@informatik.uni-halle.de> <20000404172309.V20770@fw.wintelcom.net> <38EA84C5.73EC3E1A@informatik.uni-halle.de> <20000404175445.X20770@fw.wintelcom.net> <38EA8F06.7E09594D@informatik.uni-halle.de>
next in thread | previous in thread | raw e-mail | index | archive | help
* Jens Rehsack <rehsack@informatik.uni-halle.de> [000404 18:25] wrote: > > > Alfred Perlstein schrieb: > > > > * Jens Rehsack <rehsack@informatik.uni-halle.de> [000404 17:41] wrote: > > > > > > > > > Alfred Perlstein schrieb: > > > > > > > > * Jens Rehsack <rehsack@informatik.uni-halle.de> [000404 17:19] wrote: > > > > > Hi! > > > > > > > > > > I'm a FreeBSD "newbie" (you would call it so, wouldn't you?), and I have > > > > > installed > > > > > a machine with FreeBSD 3.4 (distribution from Walnut Creek CDROM). > > > > > The system works fine, except that the system doesn't answer for any > > > > > ip-requests > > > > > (ECHO REQ., FTP-Connect, NFS-Connect) before I didn't ping a machine. > > > > > which machine > > > > > that is makes no different. > > > > > When I've pinged a machine, the system will answer incoming packets for > > > > > half an > > > > > hour (or so), and the theater begins again... > > > > > > > > > > outgoing connection I can start from this machine without any problems. > > > > > What may the reason for such an incredible behavior? > > > > > > > > I would try upgrading to 3-stable, see: > > > > http://www.freebsd.org/handbook/cutting-edge.html > > > I think my 3.4-stable is the most current version? > > > > No, if you've installed from CDrom then you have 3.4-RELEASE, some time > > has passed since the release and various fixes have been put into the > > source since then, read the URL i sent you and do the upgrade, it may > > help. > > Ok. I'm just downloading ftp://.../FreeBSD-STABLE/src/sys.tar.gz > I hope it will work :-) Er, you really ought to use cvsup and make world: (option b) b.Use the cvsup program with this supfile. This is the second most recommended method, since it allows you to grab the entire collection once and then only what has changed from then on. Many people run cvsup from cron and keep their sources up-to-date automatically. For a fairly easy interface to this, simply type: # pkg_add -f \ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz > > > > > > > > In the future it's much more helpful if you can include such > > > > information as which ethernet card you're using and perhaps > > > > what other system components you have installed as well as > > > > the motherboard type. > > > > > > The system is an i486DX2-66, > > > HiNT motherboard (EISA), Y2K compliant > > > 32MB RAM (8x4MB) > > > eth0 => vx0 => 3c597 (3Com Fast-Etherlink III - EISA) > > > > it looks like guido@freebsd.org is the writer/maintainer of the driver, > > you may want to toss him an mail directly and describe the problem. > > I don't think that it's a problem with the ethernet card, because the > computer > seems to receive the packets. I will try an tcpdump to check, but I'm > sure... :-) Yes, but there can be a problem with the driver that causes this sort of problem. > > > > disk-controller: AHA-2742AT (twin-channel aic7xxx compatible with floppy > > > port) > > > two scsi-disks (both id0, on different channels) > > > yamaha cdr-200 on id 1, channel B (primary) > > > Spea-V7 1MB VL vga card > > > 8-bit I/O-card for mouse > > > > > > > Lastly, are you sure you don't have some sort of power-management > > or APM on? I'm kinda grasping at straws here, but 30 minutes seems > > to be a nice round number for APM/power-management. > > As sure as I could be. I didn't tried to setup the computer with > the dos-based AMI-SETUP program, so that I don't have seen all options, > but in the official parts I didn't recognize sth. about APM. > Therefore, the computer answers all packets, if I run a ping fw > (firewall > machine in LAN) on it. > The only problem is after boot (it starts not to answering before I've > send > a packet out) > And it seems I've lied - now my ping on it runs for 2 hours and runs > again. > But last time, I was for 2 weeks in holiday, I've runned a ping and this > ping > stops getting answers after ca. 9000 send packets. (ca. 4 hours) weird, best of luck with the upgrade, you really ought to contact the driver maintainer about this. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000404183451.Z20770>