From owner-freebsd-isp Mon Sep 13 3: 9: 9 1999 Delivered-To: freebsd-isp@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.128.198]) by hub.freebsd.org (Postfix) with ESMTP id 6693415549 for ; Mon, 13 Sep 1999 03:08:57 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (root@localhost [127.0.0.1]) by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id LAA32199; Mon, 13 Sep 1999 11:08:47 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id LAA54420; Mon, 13 Sep 1999 11:13:45 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199909131013.LAA54420@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Steven Honson Cc: freebsd-isp@FreeBSD.ORG Subject: Re: pricing question? In-reply-to: Your message of "Mon, 13 Sep 1999 19:37:14 +1000." <3.0.5.32.19990913193714.007cbb80@mail.planetquake.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Sep 1999 11:13:45 +0100 From: Brian Somers Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I do a similar thing myself, but it's not a great ``general'' solution as you end up with lots of names with very small DNS ttls. > Another way around giving users static ip's would be to write a small > dynamic dns daemon that assigns users a host name which is updated when > ever a user dials up, this could be done by hacking pppd and writing a > small perl/c program that updates a BIND zone file. Of course that could > only be done if you used FreeBSD/Linux systems. > You could use the naming sceme, username.cust.myisp.net > Just a idea, > Steven Honson > > At 11:06 AM 9/13/99 +0200, you wrote: > >On Mon, Sep 13, 1999 at 09:41:17AM +0100, Brian Somers wrote: > >> [.....] > >> > When I worked for an ISP, a private subscriber could not be given > >> > a fixed IP. If you had a corporate dial-in you could get even blocks > >> > of IP##. Of course the price was noticably different. But private > >> > customers "doesn't need a fixed IP#" (yes, you may flame me now) ;-) > >> > >> Of course the ``correct'' thing would be to have the NASs smart > >> enough to allow the client to request the IP number that they had > >> last time and allocate it if they can. Currently, no NASs that I > >> know of are smart enough to do this (except ppp(8) of course!). > > > >Cisco AS5300 does exactly this. The user doesn't even has to request it, > >if the IP number the customer had the last time, is available the > >customer gets them same number. > > > >/Jesper > > > >-- > >Jesper Skriver (JS4261-RIPE), Network manager > >Tele Danmark DataNet, IP section (AS3292) > > > >One Unix to rule them all, One Resolver to find them, > >One IP to bring them all and in the zone to bind them. > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > >with "unsubscribe freebsd-isp" in the body of the message > > > --------------------------------------- > Steven Honson > Internet Technologist & Consultant > Taroona High School, Australia > shonson@hubbub.ths.tased.edu.au -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message