From owner-freebsd-current Wed Oct 25 23:55:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (Postfix) with ESMTP id 1566A37B479 for ; Wed, 25 Oct 2000 23:55:32 -0700 (PDT) Received: (from daemon@localhost) by smtp03.primenet.com (8.9.3/8.9.3) id XAA19631; Wed, 25 Oct 2000 23:53:45 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp03.primenet.com, id smtpdAAA0DayqM; Wed Oct 25 23:53:35 2000 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id XAA12955; Wed, 25 Oct 2000 23:55:14 -0700 (MST) From: Terry Lambert Message-Id: <200010260655.XAA12955@usr08.primenet.com> Subject: Re: strange problem of PPPoE + NAT To: josh@zipperup.org (Josh Tiefenbach) Date: Thu, 26 Oct 2000 06:55:14 +0000 (GMT) Cc: receiver@RedDust.BlueSky.net.au (Idea Receiver), freebsd-current@FreeBSD.ORG In-Reply-To: <20001025195050.A44709@zipperup.org> from "Josh Tiefenbach" at Oct 25, 2000 07:50:51 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > the other problem i had after switch that system to -current > > is that after a random time, the connection will frzzed. > > the routing table still exist, connection is still up. > > just cant connect to anywhere outside the network. no error > > or anything been loged in ppp.log. > > 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. Drop Julian or Archie a line; Julian wrote the code for netgraph for PPPoE, and Archie modified it most recently. BTW: I believe PPPoE in both Julian and Archie's cases specifically uses the netgraph PPP implementation, so it's an "all in the kernel" approach; the problem may be your use of user space code (i.e. killable code, since you can't kill it in the kernel, only unlink or unload it). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message