<!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>
<blockquote
cite="mid:AANLkTintMrCrHR85_45-ApgP=QQ2YU63N3+N=jEnAnUy@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<blockquote style="border-left: 1px solid rgb(204, 204, 204);
margin: 0px 0px 0px 0.8ex; padding-left: 1ex;"
class="gmail_quote">
<div text="#000000" bgcolor="#ffffff">
<div class="im">
<blockquote 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>
</div>
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.
<div class="im"><br>
</div>
</div>
</blockquote>
<div> </div>
<div> </div>
<div> </div>
<div>Which means that there's no "right way" :-)</div>
<div>But surely there are many wrong... </div>
</div>
<pre wrap="">
</pre>
</blockquote>
Okay, I said that wrong. . . your 'right way' is a subset of the
REAL 'right way' which is to end up with a subnet big enough to
handle your clients. Either a big enough block, or multiple VLANs
with the right number of client machines for the block assigned to
it.<br>
<br>
So, we're both right, I'm just more right than you :-D<br>
</body>
</html>