Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 10 Jan 2006 13:36:09 +0300
From:      Gleb Smirnoff <glebius@FreeBSD.org>
To:        Victor Snezhko <snezhko@indorsoft.ru>
Cc:        freebsd-current@FreeBSD.org, Goran Gajic <ggajic@afrodita.rcub.bg.ac.yu>
Subject:   Re: 7.0-CURRENT ppp related panic
Message-ID:  <20060110103609.GG87430@cell.sick.ru>
In-Reply-To: <umzi4tlrb.fsf@indorsoft.ru>
References:  <Pine.LNX.4.63.0601071339370.24791@afrodita.rcub.bg.ac.yu> <20060110095926.GE87430@FreeBSD.org> <umzi4tlrb.fsf@indorsoft.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jan 10, 2006 at 04:34:00PM +0600, Victor Snezhko wrote:
V> > G> I have managed to trigger two panics by doing ifconfig ppp0 destroy while
V> > G> ppp was running.
V> >
V> > Kernel ppp(4) is known to have problems. At least there are problems with
V> > interaction of Giant-locked tty layer and Giant-less network layer.
V> >
V> > I'd recommend you to use user-level ppp(8), or mpd, which routes traffic
V> > through kernel ng_ppp(4).
V> 
V> I may be mistaken, but I saw pppd in the panic report, isn't it an
V> indication of user-level ppp?

pppd(8) is a daemon that controls kernel level PPP.
ppp(8) is a daemon implementing PPP in userland.

V> P.S.: I'm using user-level ppp(it comes before kernel one in the
V> handbook :)) and I am lucky enough not to experience any problem since
V> I switched to -current in November (besides INET6-caused one, which is
V> now fixed). Thanks for notice, though.

-- 
Totus tuus, Glebius.
GLEBIUS-RIPN GLEB-RIPE



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060110103609.GG87430>