From owner-freebsd-questions Mon Aug 24 23:54:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA10414 for freebsd-questions-outgoing; Mon, 24 Aug 1998 23:54:23 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from unix.safeweb.net (safeweb.net [207.193.55.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA10409 for ; Mon, 24 Aug 1998 23:54:18 -0700 (PDT) (envelope-from bob@safeweb.net) Received: from safeweb.net (dial-049.safeweb.net [207.193.192.49]) by unix.safeweb.net (8.8.7/8.6.12) with ESMTP id BAA06149; Tue, 25 Aug 1998 01:52:24 -0500 (CDT) Message-ID: <35E25F60.AA8403F4@safeweb.net> Date: Tue, 25 Aug 1998 01:53:21 -0500 From: Bobby Walker X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: burn@visi.com CC: freebsd-questions@FreeBSD.ORG Subject: Re: PPP, and the problems it causes References: <35E25232.6DBD@visi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG uncomfortably numb wrote: > > i have configured kernel ppp as well as user ppp on my system according > to the man pages, FAQ, and handbook, but neither of them works...kind > of. i connect and start a session alright, however, if i try using any > kind of program, like telnet, ping, ncftp, irc, etc., it just hangs and > does nothing. in X, if i am connected via PPP netscape won't even start. > I get no error messages. the strange thing is, however, that lynx works > just fine--for a numeric IP with either kernel or user PPP (DNS doesn't > work either). i'v had many people try and figure out what is going on > and why lynx is the odd one out, but no one can seem to figure it out. > i'v tried changing my modem around and rebuilding the kernel, etc. and > this is what happens. any ideas? > > thanks, > > -brian How do you have your DNS setup? -- Bob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message