From owner-freebsd-current Wed Oct 25 18:33:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from RedDust.BlueSky.net.au (reddust.bluesky.net.au [203.31.37.15]) by hub.freebsd.org (Postfix) with ESMTP id 3024337B479 for ; Wed, 25 Oct 2000 18:33:42 -0700 (PDT) Received: from localhost (receiver@localhost) by RedDust.BlueSky.net.au (8.9.3/8.9.3) with ESMTP id LAA12302; Thu, 26 Oct 2000 11:35:36 +1000 (EST) (envelope-from receiver@RedDust.BlueSky.net.au) Date: Thu, 26 Oct 2000 11:35:36 +1000 (EST) From: Idea Receiver To: Josh Tiefenbach Cc: freebsd-current@FreeBSD.ORG Subject: Re: strange problem of PPPoE + NAT In-Reply-To: <20001025195050.A44709@zipperup.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 25 Oct 2000, Josh Tiefenbach wrote: > Interestingly enough, I've been having the same problem with PPPoE ever since > it hit the tree 'bout a year ago. It happens infrequently enough that I tend > to blame my provider, rather than ppp. > > 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? it happen so frequently, it is impossible to run a stable server with PPPoE! > > module_register: module netgraph already exists! > > linker_file_sysinit "netgraph.ko" failed to register! 17 > > Just a guess, but thats probably because you're trying to kldload netgraph.ko, > but have already compiled it into your kernel with options NETGRAPH nope. i didnt kldload netgraph.ko at all. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message