Date: Mon, 13 Sep 1999 12:07:57 +0200 From: Rico Pajarola <pajarola@cybertime.ch> To: freebsd-isp@freebsd.org Subject: Re: pricing question? Message-ID: <4.1.19990913114238.00a74c10@mail.cybertime.ch> In-Reply-To: <3.0.5.32.19990913193714.007cbb80@mail.planetquake.com> References: <19990913110619.A59569@skriver.dk> <199909130841.JAA53625@keep.lan.Awfulhak.org> <CD4DE0181670D211AC5400A0C94BD1B8B4046A@dksmsx30.idk.intel.com> <199909130841.JAA53625@keep.lan.Awfulhak.org>
next in thread | previous in thread | raw e-mail | index | archive | help
i think the original question was not how to fake static ip's, but how to charge for them... it depends on how many static ip's they want: if it's a whole block, we charge them for filling out the application form for ripe (i think in us it's arin, www.arin.net) and the setup of routes, talkin to our backbone provider etc. If they can't convince ripe to give them a block of ip addresses, because they can't justify having a whole block (16 addresses) or because they have no real reason at all, we charge them a monthly fee for giving them one of *our* precious ip addresses. --Rico Pajarola At 19:37 13.09.99 +1000, you wrote: >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 > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-isp" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.1.19990913114238.00a74c10>