Date: Wed, 25 Oct 2000 21:57:42 -0400 From: Josh Tiefenbach <josh@zipperup.org> To: Idea Receiver <receiver@RedDust.BlueSky.net.au> Cc: freebsd-current@FreeBSD.ORG Subject: Re: strange problem of PPPoE + NAT Message-ID: <20001025215742.B44709@zipperup.org> In-Reply-To: <Pine.BSF.4.10.10010261128190.12282-100000@RedDust.BlueSky.net.au>; from receiver@RedDust.BlueSky.net.au on Thu, Oct 26, 2000 at 11:35:36AM %2B1000 References: <20001025195050.A44709@zipperup.org> <Pine.BSF.4.10.10010261128190.12282-100000@RedDust.BlueSky.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001025215742.B44709>