From owner-freebsd-questions Fri Jan 16 10:49:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA06748 for questions-outgoing; Fri, 16 Jan 1998 10:49:00 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA06731 for ; Fri, 16 Jan 1998 10:48:47 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id KAA01408; Fri, 16 Jan 1998 10:47:58 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Date: Fri, 16 Jan 1998 10:47:58 -0800 (PST) From: Doug White Reply-To: Doug White To: Victor Sudakov cc: freebsd questions mailing list Subject: Re: iijppp + slirp In-Reply-To: <199801141900.CAA07043@vas.tsu.tomsk.su> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk On Thu, 15 Jan 1998, Victor Sudakov wrote: > Could you please help me make iijppp work with SLiRP on the server side? How is SLiRP called? You aren't running it in your dialup script.. > I start ppp as 'ppp -auto phantom'. It logs in but is never up, and the > default route is not changed. The /var/log/ppp.log grows though :-) It works > fine with the non-slirp provider BTW (the other entry called mpeks). Did you look in the ppp.log to find out just why it won't connect? You can post the relevant section(s) if you want us to decode it. Post a sample attempted connect to phantom. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major