[NTLUG:Discuss] Broadcast IP address

[Ralph Green]

On 11/9/12, Burton Strauss III <bstrauss at gmail.com> wrote:
> Remember, the broadcast itself is NOT limited to the existing address.
> Otherwise you would never get one the first time :-). So if nobody answers
> when you try to extend your current lease, you broadcast and hear from the
> new server.  So in theory you can just deploy a new DHCP server with
> 192.168.5.0/23 address space and have the old one stop handing out
> addresses.
>
 Good.  I am not going to have a DHCP server for the new range.  Well,
not directly.  The VPN server will hand out IP addresses in the new
range and those are the only machines in that range for now.  Machines
don't talk to each other.  They just all talk to a couple of servers
in the original IP range.

> BUT:  it's far, far safer to first update the mask on the current server
> (and adjust the pool to give out 5s) and allow all clients to get new
> addresses with the new broadcast address through timeout of their existing
> leases.
  I adjusted the server config this morning and I have nt touched any
clients yet.  So far, so good.

>
> But as long as you are re-addressing, why not move to the 172 space
> (172.16.0.0 - 172.31.255.255)... that's usually handed out in /16s.
>
 I can see why you suggest that.  I don't think I really need it and
the biggest strike against it is that it would be a bigger change.
> -----Burton

 My purpose for all this is t deploy a new VPN server.  We currently
use pptp VPN and the server is really old.  I want to deploy an up to
date OpenVPN server.  I want to keep the old server up until all the
remote users are moved over, which means I need to let the old server
keep its allocation of IP addresses and I needed a new one.