<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<br>
On 02/01/2011 11:54 AM, José Queiroz wrote:
<blockquote
cite="mid:AANLkTin86HT_gsvo7YFXen2EsUSX1r6j6RaCAHex+HPe@mail.gmail.com"
type="cite"><br>
<div class="gmail_quote">2011/2/1 Tim Gavin <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:livewire98801@gmail.com">livewire98801@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
What's wrong with that, and why would it break?<br>
</blockquote>
<div><br>
Each broadcast domain should correspond to a subnet range. If
you have several subnets on the same broadcast domain, the
DHCP server cannot tell apart which request came from which
subnet.<br>
</div>
</div>
</blockquote>
<br>
The DHCP server doesn't need to know where the request is coming
from. . . if it knows, the request should be a 'renew', and should
renew the address no matter which block it was assigned from.<br>
<br>
<blockquote
cite="mid:AANLkTin86HT_gsvo7YFXen2EsUSX1r6j6RaCAHex+HPe@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<div>
<br>
The "right way" to solve your problem is break your network in
several broadcast domains (e.g. VLANs), and assign a subnet
range to each broadcast domain.<br>
</div>
</div>
</blockquote>
<br>
No, the "right way" is to have a big enough block to handle all your
clients. If that means segregating your client base into separate
VLANs, then sure, but my ultimate solution was to get a bigger
allocation of IPs. Maybe neither one would work for someone else.
Or, like my example, my final solution was to get a bigger block,
but I had to deal with two blocks on one VLAN for a while until that
happened.<br>
<br>
<blockquote
cite="mid:AANLkTin86HT_gsvo7YFXen2EsUSX1r6j6RaCAHex+HPe@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<div><br>
Another way to deal with your problem is create fixed address
assignments, to the machines in all subnet ranges, except one.
This last one can work from the address pool, that now is
unique.</div>
</div>
</blockquote>
<br>
In my example it was an ISP network. . . fixed assignments work in a
corporate campus, but not on an ISP network, at least not well.<br>
</body>
</html>