From owner-freebsd-questions@FreeBSD.ORG Tue Jun 19 12:42:40 2007 Return-Path: X-Original-To: questions@freebsd.org Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C26F116A46C for ; Tue, 19 Jun 2007 12:42:40 +0000 (UTC) (envelope-from iaccounts@ibctech.ca) Received: from pearl.ibctech.ca (pearl.ibctech.ca [208.70.104.210]) by mx1.freebsd.org (Postfix) with ESMTP id 7F5E913C4AD for ; Tue, 19 Jun 2007 12:42:40 +0000 (UTC) (envelope-from iaccounts@ibctech.ca) Received: (qmail 30316 invoked by uid 1002); 19 Jun 2007 12:42:39 -0000 Received: from iaccounts@ibctech.ca by pearl.ibctech.ca by uid 89 with qmail-scanner-1.22 (spamassassin: 2.64. Clear:RC:1(208.70.107.100):. Processed in 6.236936 secs); 19 Jun 2007 12:42:39 -0000 Received: from unknown (HELO ?192.168.1.210?) (steve@ibctech.ca@208.70.107.100) by pearl.ibctech.ca with (DHE-RSA-AES256-SHA encrypted) SMTP; 19 Jun 2007 12:42:33 -0000 Message-ID: <4677CF3A.7090003@ibctech.ca> Date: Tue, 19 Jun 2007 08:42:34 -0400 From: Steve Bertrand User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: questions@freebsd.org References: <50096.68.236.193.86.1182222005.squirrel@mail.panix.com> <20070619034736.D0AE1B874@shodan.nognu.de> In-Reply-To: <20070619034736.D0AE1B874@shodan.nognu.de> X-Enigmail-Version: 0.95.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: Apparent IP configuration change . . . X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jun 2007 12:42:40 -0000 Frank Steinborn wrote: > John Williams wrote: >> FreeBSD users: >> >> Until recently I've been running a very low-maintenance FreeBSD router >> with FBSD 6.2. >> >> The IP setup was a dynamic IP configuration with Verizon as my DSL >> provider in NJ. The connection was virtually trouble-free. >> >> I switched to a static IP about 10 days ago and the IP configuration no >> longer works. > > [ ... ] > >> Here's what worked for the dynamic IP connection: >> >> verizon: >> set device PPPoE:rl0 >> set authname xxx >> set authkey xxx >> add default HISADDR >> >> Here's what I've set up for the static IP connection: >> >> verizon: >> set device PPPoE:rl0 >> set authname xxx >> set authkey xxx >> add default HISADDR >> set ifaddr 70.0.0.54 70.0.0.1 255.255.255.255 0.0.0.0 > > You are suggesting the peer that your IP should be 0.0.0.0, but you > will only accept 70.0.0.54. Moreover, you only accept peer as > 70.0.0.1. Are you sure that this is what you want? ppp(8) gives a > wonderful overview of 'set ifaddr'. > > It's kind of hard to help without further information, it would be > really nice to know the data you got from the provider about the > static IP setup. > > Just a naive shoot in blue: Did you try without setting 'set ifaddr' > at all? Probably your peer will negotiate the right setting with your > ppp-client anyway. I agree with this statement. Any ISP I have dealt with, including the one I work at, a 'static' PPP IP address is actually configured within the RADIUS authentication server, is directly associated with your username and is not usually configured on the client premises equipment as a 'standard' static IP address. When your PPP client logs in using the supplied user/pass, the Framed-IP-Address is sent back to you in response to your successful login attempt. Steve