From owner-freebsd-current Mon Jul 3 10:02:58 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA13781 for current-outgoing; Mon, 3 Jul 1995 10:02:58 -0700 Received: from haven.uniserve.com (haven.uniserve.com [198.53.215.121]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA13773 for ; Mon, 3 Jul 1995 10:02:55 -0700 Received: by haven.uniserve.com id <30829>; Mon, 3 Jul 1995 10:03:26 +0100 Date: Mon, 3 Jul 1995 10:03:15 -0700 (PDT) From: Tom Samplonius To: James Leppek cc: amurai@spec.co.jp, freebsd-current@freefall.cdrom.com Subject: Re: ppp In-Reply-To: <9507031546.AA01586@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: > Suppose the provider accepted the 192.0.0.1 address and arp'd > it (mine did). How does the provider know that for freebsd machines the magic You should tell your provider to fix his broken equipment. For example, using the IP of a nameserver or a mailhost would really mess things up. This gets real ugly when the PPP server is broadcasting routes to gateway routers. A large ISP in the US had similar equipment, and some joker decided to use 1.0.0.1 as an IP address, that route was actually broadcast out onto some major backbones so that you could actually traceroute to 1.0.0.1 from outside systems. > "I want an IP" address is 192.0.0.1 > Some providers offer both rotory and fixed IP service we just can't tell > them to change for fbsd. I have tried it did not work :-) What is supposed to happen, is that the PPP server should _tell_ your system what address to use. There is no need to use a "magic" IP address to signal this, as the PPP protocol has full address negotiation capability. I've setup a PPP server that can do both static and dynamic assignment with no requirement for magic IP's. Tom