From owner-freebsd-current Wed Oct 25 18:57:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.snickers.org (snickers.org [216.126.90.2]) by hub.freebsd.org (Postfix) with ESMTP id 2552837B479 for ; Wed, 25 Oct 2000 18:57:44 -0700 (PDT) Received: by mail.snickers.org (Postfix, from userid 1037) id 1BE593D06; Wed, 25 Oct 2000 21:57:43 -0400 (EDT) Date: Wed, 25 Oct 2000 21:57:42 -0400 From: Josh Tiefenbach To: Idea Receiver Cc: freebsd-current@FreeBSD.ORG Subject: Re: strange problem of PPPoE + NAT Message-ID: <20001025215742.B44709@zipperup.org> References: <20001025195050.A44709@zipperup.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from receiver@RedDust.BlueSky.net.au on Thu, Oct 26, 2000 at 11:35:36AM +1000 Organization: Hah Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > When it happens, killing ppp and restarting it is usually enough. > > > > I have no idea what causes it. > > > > kill ppp and restart it doesnt help at all. > will it make any different if i change a network card? I dont think so. There are times when I cant do a simple kill/restart, and I have to physically shut off the modem, cycle power on my server, and bring it up again. While this *may* be a function of the PPPoE code, I'm inclined to blame my provider, if only because they've had issues in the past. I presently lack the resources to adequately debug the issue. > it happen so frequently, it is impossible to run a stable > server with PPPoE! Might I suggest you drop a note over on freebsd-net? Perhaps you'll rustle up some more support there. josh -- "Watching those 2 guys [Bush and Gore] debate is like watching Ben Stein read 'The Story of O'" -- Dennis Miller To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message