Honestly I don't do DHCP at all. Keeps things honest from my perspective and makes it easier to see who's causing issues - at least from my standpoint.
Clients primarily need a Public IP for VPNs. A couple of clients run their own mail server and I've got one that runs their own web server, but those are monitored VERY closely! -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ugo Bellavance Sent: Monday, January 28, 2008 3:29 PM To: [email protected] Subject: Re: [WISPA] Private vs Public addresses for end-users Jason Hensley wrote: > Even if you buy your own from ARIN, if you're that big, then the costs > are nothing - I agree. > > I personally do private addressing on all my broadband clients. That > allows me to NAT how I see fit. I someone needs a public IP I do a > static 1-1 NAT for them. So far I've had no issues. Ok, makes sense. In what cases, for example, would they need a public IP and I guess that means that you have to make a reservation in your DHCP? Thanks, Ugo ---------------------------------------------------------------------------- ---- WISPA Wants You! Join today! http://signup.wispa.org/ ---------------------------------------------------------------------------- ---- WISPA Wireless List: [email protected] 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: [email protected] Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
