<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFCC" text="#000000">
Hmm?<br>
<br>
fixed-address 1.1.1.2;
<br>
subnet 1.1.1.0 netmask 255.255.255.252 {
<br>
option routers 1.1.1.1;
<br>
}
<br>
<br>
As far as I can see that fixed address IS contained in the subnet?
and the subnet is part of the shared network?<br>
<br>
On 25/11/11 19:58, Simon Hobson wrote:
<blockquote cite="mid:p062408a7caf5959d6b00@simon.thehobsons.co.uk"
type="cite">Sten Carlsen wrote:
<br>
<br>
<blockquote type="cite">
<blockquote type="cite">host customer101public {
<br>
hardware ethernet 00:11:22:33:44:55;
<br>
fixed-address 1.1.1.2;
<br>
}
<br>
<br>
shared-network vlan101 {
<br>
subnet 10.0.0.0 netmask 255.255.255.248 {
<br>
option routers 10.0.0.1;
<br>
pool {
<br>
range 10.0.0.2 10.0.0.6;
<br>
deny known-clients;
<br>
}
<br>
}
<br>
<br>
subnet 1.1.1.0 netmask 255.255.255.252 {
<br>
option routers 1.1.1.1;
<br>
}
<br>
}
<br>
</blockquote>
</blockquote>
<br>
<blockquote type="cite">You still have the mistake to have a fixed
address in a range. Declare subnet 1.1.1.0 with no range
statement. There is a risk that an unknown client will be given
the 1.1.1.2 address when it is defined as a range.
<br>
</blockquote>
<br>
Err, no he hasn't. The range is in a different (RFC1918) subnet).
<br>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Best regards
Sten Carlsen
No improvements come from shouting:
"MALE BOVINE MANURE!!!"
</pre>
</body>
</html>