*** From dhcp-server -- To unsubscribe, see the end of
this message. ***
Shaun wrote:
>I have 1 server on it's own vlan, the vlan has 2
subnets assigned to it.
>First subnet is 204.15.133.128/26 and the second is
204.15.134.224/27
>
>The problem i'm having is that the dhcp server seams to
only be picking up
>the first subnet and when requests come in on the second
subnet i get this
>message in my /var/log/messages.
Just to be absolutely clear, the two subnets are one the
same VLAN -
ie the same physical network ?
In that case this is what is called a shared network, so
your config
is wrong as it doesn't match the network configuration.
Also be aware
that there is no concept of requests coming in on one or the
other
subnet - they come in on an interface and are then matched
to a
subnet.
>'DHCPDISCOVER from fe:fd:cc:0f:86:ee via br0: network
204.15.133.128/26: no
>free leases'
That is correct, there are no free leases. There is no host
statement
for this client (in the config you posted), and since there
are no
dynamic ranges either, there is no way to give it an
address.
>My config is pretty long because i'm doing static mac
to ip assignments but
>here is the short version.
It's always dangerous to edit what you post, what you leave
out
thinking it's irrelevant may be important.
I'll guess that there IS a host statement for this client,
but it's
allocated an address in the 204.15.134.224/27 subnet and
your server
has it's primary interface in the 204.15.133.128/26.
If so, then what is happening is that because you've missed
out the
shared-network statement, the server can ONLY give the
client in the
ONE subnet it thinks it's connected to. Since it cannot
give the
client the address you've specified, AND there are no
dynamic
addresses available, it cannot give it an address at all.
>ddns-update-style ad-hoc;
This is irrelevant if you only use static addresses - the
server
won't attempt any DNS updates for static addresses unless
you tell it
to.
>subnet 204.15.133.128 netmask 255.255.255.192 {
> option routers 204.15.133.131;
> option subnet-mask 255.255.255.192;
> option domain-name-servers 204.10.37.58;
>
> host CC0F8585 {
> hardware ethernet FE:FD:CC:0F:85:85;
> fixed-address 204.15.133.133;
> }
>}
>subnet 204.15.134.224 netmask 255.255.255.224 {
> option routers 204.15.134.227;
> option subnet-mask 255.255.255.224;
> option domain-name-servers 204.10.37.58;
>
> host CC0F86E4 {
> hardware ethernet FE:FD:CC:0F:86:E4;
> fixed-address 204.15.134.228;
> }
>}
>
>Where am i going wrong here? It's almost like dhcpd is
ignoring the config
>for the second subnet?
It is !
Try this :
ddns-update-style none;
option domain-name-servers 204.10.37.58;
shared-subnet "mynet" {
subnet 204.15.133.128 netmask 255.255.255.192 {
option routers 204.15.133.131;
option subnet-mask 255.255.255.192;
}
subnet 204.15.134.224 netmask 255.255.255.224 {
option routers 204.15.134.227;
option subnet-mask 255.255.255.224;
}
}
host CC0F8585 {
hardware ethernet FE:FD:CC:0F:85:85;
fixed-address 204.15.133.133;
}
host CC0F86E4 {
hardware ethernet FE:FD:CC:0F:86:E4;
fixed-address 204.15.134.228;
}
IMPORTANT NOTE - you will see that I've moved the host
declarations
out of the subnet declarations. They are ALWAYS global in
scope, and
it seems that nearly everyone makes the mistake of putting
them in
the subnet declaration expecting them to be associated.
You can also put common options (such as your DNS option) in
the
global scope, or in the shared network statement - it just
reduces
the size of the config. You can set a global value and
override it
for a specific subnet etc if most of the subnets use a
common value
but one or two are different.
Simon
------------------------------------------------------------
-----------
List Archives : http://www.isc.org/ops/
lists/
Unsubscribe : http://www.
isc.org/sw/dhcp/dhcp-lists.php
-or- : mailto:dhcp-server-request isc.org?Subject=unsubscribe
------------------------------------------------------------
-----------
|