From owner-freebsd-isdn Fri Apr 21 17:28:50 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from boombox.zaphods.net (dusdi4-145-253-188-011.arcor-ip.net [145.253.188.11]) by hub.freebsd.org (Postfix) with ESMTP id 5F01137BDF4 for ; Fri, 21 Apr 2000 17:28:46 -0700 (PDT) (envelope-from zaphodb@zaphods.net) Received: from localhost (zaphodb@localhost [127.0.0.1]) by boombox.zaphods.net (8.9.3/8.9.3) with ESMTP id CAA28983; Sat, 22 Apr 2000 02:27:15 +0200 (CEST) (envelope-from zaphodb@zaphods.net) Date: Sat, 22 Apr 2000 02:27:11 +0200 (CEST) From: Stefan Schmidt To: hg@glaess.ndh.com Cc: freebsd-isdn@freebsd.org Subject: Re: a problem with i4b or with FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 11 Apr 2000 hg@glaess.ndh.com wrote: > ok following are the enviroment . mine is: FreeBSD 3.4-REL P133 128mb (SiS board) (a HP vectra) AVM Fritz!Card PnP(ISA) NE2000-comp. ISA NIC natd (same config) > what wrong anyone here that he know this problem it is a bug in the VM from > FreeBSD ? i dont think its the VM system for i have similar problems My System does spontanous reboots every 3-7 days or so plus my internet connectivity hangs if someone accesssed the ftp or web or other server on the given machine. dont get me wrong i can transfer hours at wire-speed from my other machine which is connected via NAT and i can use the above server to download but as soon as someone transfers more than lets say a megabyte from the above machine to the internet its connectivity gets freezed. by freezed i mean i cannot send a packet from/to the net anymore. all i know is that at least one source of error is the Fritz!Card because i previously had the same card in another computer and it showed the same problems in the same manner which mean, spontanous reboots and freezing the isdn-sppp-link. oh yes, the interface stays up and the sppp link does NOT drop, but there simply is no more ip-traffic on it. to me that behaviour first sounded quite clearly like an software problem with the NAT , but i'm not sure anymore since other setups seem to work with i4b and NAT very proper. so my question at this point simply is: could it be a hardware problem with that damn Fritz!Card ? Stefan Schmidt - -- Q. What's the difference between Los Angeles and yogurt? A. Yogurt has a living, active culture. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.0 (FreeBSD) Comment: Made with pgp4pine iD8DBQE5APHiukA5Jvp3yMERAuJ9AKDFKPzetaLTsaawSN0N2ImkXjEgHQCgoLyp EDvWwzfA2gRrbvXUyNXtMrg= =ih2z -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message