From owner-freebsd-current Mon Jul 3 13:13:53 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA22805 for current-outgoing; Mon, 3 Jul 1995 13:13:53 -0700 Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA22794 for ; Mon, 3 Jul 1995 13:13:51 -0700 Received: from mail.barrnet.net (mail.barrnet.net [131.119.246.7]) by who.cdrom.com (8.6.11/8.6.11) with ESMTP id NAA01300 for ; Mon, 3 Jul 1995 13:13:35 -0700 Received: from haven.uniserve.com (haven.uniserve.com [198.53.215.121]) by mail.barrnet.net (8.6.10/MAIL-RELAY-LEN) with ESMTP id MAA11631 for ; Mon, 3 Jul 1995 12:35:32 -0700 Received: by haven.uniserve.com id <30869>; Mon, 3 Jul 1995 12:33:13 +0100 Date: Mon, 3 Jul 1995 12:32:31 -0700 (PDT) From: Tom Samplonius To: James Leppek cc: freebsd-current@freefall.cdrom.com Subject: Re: ppp In-Reply-To: <9507031757.AA01662@borg.ess.harris.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk On Mon, 3 Jul 1995, James Leppek wrote: > How did you configure your netblazer(what they have) to do this? IMO, Netblazer's don't make a very good PPP server. I don't believe that dynamic IP assignment out of an address pool is possible with the 2.3 software. You can get different systems with proper PPP negotiation for much less. > was it configured to assert a particular IP based on password like most? > As I indicated, I asked that they should certainly refused IP's they > do not have authority over as a minimum, but I have no "real" > ability to do anything. I also love to constantly hear "the windows > and linux users do not have a problem" AAARRRRGGGG If you need to convince them that there is problem, see if the their mail server(s) is on the same subnet as the Netblazer and use that IP address. This will convince them quite quickly. > what is magic about 192.0.0.1? should ppp map a users configuration > request to some arbitrary alternate IP. Set ifaddr is there for > a purpose and even gives "ifaddr 0 0" in an example. Nothing is special about 192.0.0.1. No magic remapping should actually be taking place. Tom