Date: Thu, 26 Oct 2000 06:55:14 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: josh@zipperup.org (Josh Tiefenbach) Cc: receiver@RedDust.BlueSky.net.au (Idea Receiver), freebsd-current@FreeBSD.ORG Subject: Re: strange problem of PPPoE + NAT Message-ID: <200010260655.XAA12955@usr08.primenet.com> In-Reply-To: <20001025195050.A44709@zipperup.org> from "Josh Tiefenbach" at Oct 25, 2000 07:50:51 PM
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200010260655.XAA12955>