First one must define public address. Meaning public IPs used belonging to 
the upstream ISP or the WISP owning their own block of public IPs. Owning 
your own block, you must ask... Is it worth the technical admin headache to 
manage them, and is the expertise there to do it. And is the benefit there, 
if the expertise was. The primary benefit for a small ISP is just to be 
portable between upstrewam providers, any time you want to be.  Usually the 
answer is its not worth owning your own, unless you have scaled large enough 
to justify a /19 or higher.  However, using an upstream's public IPs, costs 
nothing in most cases. And they do the painful management of it.
Using private IPs, is also making it portable between providers, because its 
very quick and easy to create a new NAT rule to map the private addresses to 
any new Upstream's shared public IP.  So the real question come up as... Is 
it a benefit to your subscribers to use public IPs, different than every 
other subscriber.  Some VPN protocols require static IPs. Some corporate 
firewalling requires static IPs. Some VOIP services require public static 
IPs. Web servers and Mail servers require static IP.  Access the subscriber 
from a remore PC for remote desoktop requires public static IP.  Sharing 
IPs, will mean that if one customer gets blacklisted for sending SPAM, so 
will all your other subscribers.

It is definately possible to offer services using private IPs to the end 
users, many residential ISPs have chosen to do so. But doing so, does 
restrict the services that your subscribers will be able to do. But that may 
be a benefit. If you are selling $9.99 broadband, you won't want them to 
ahve the ability to host mail and web servers.  IF you are competing against 
commodity monopolies, you may want the added features to distinguish your 
self.

Step 1 is defining what services that you'd like your subscribers to be able 
to do.  And then you make an IP allocation method that enables that.


Tom DeReggi
RapidDSL & Wireless, Inc
IntAirNet- Fixed Wireless Broadband


----- Original Message ----- 
From: "Ugo Bellavance" <[EMAIL PROTECTED]>
To: <wireless@wispa.org>
Sent: Monday, January 28, 2008 4:37 PM
Subject: Re: [WISPA] Private vs Public addresses for end-users


> Tom DeReggi wrote:
>> whether to give private or public address has nothing to do with cost.
>>
>
> Oh, what are the thing to consider exactly?
>
> Regards,
>
> Ugo Bellavance
>
>
>
> --------------------------------------------------------------------------------
> WISPA Wants You! Join today!
> http://signup.wispa.org/
> --------------------------------------------------------------------------------
>
> WISPA Wireless List: wireless@wispa.org
>
> Subscribe/Unsubscribe:
> http://lists.wispa.org/mailman/listinfo/wireless
>
> Archives: http://lists.wispa.org/pipermail/wireless/ 



--------------------------------------------------------------------------------
WISPA Wants You! Join today!
http://signup.wispa.org/
--------------------------------------------------------------------------------
 
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/

Reply via email to