<!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">
<tt>hi simon,<br>
you're absolutely right; i was really close! :) so here's my conf:<br>
[by the way i omitted the fact that the 2 gateways are actually 2
relays. i thought i would have to class each gw like <i>class
"gw1"{match if gw == "gw1";}</i>]<br>
cheers!<br>
marco<br>
</tt><br>
<br>
# -*- mode: conf; indent-tabs-mode: t; tab-width: 2 -*-<br>
<br>
deny bootp;<br>
ignore client-updates;<br>
authoritative;<br>
ddns-update-style none;<br>
local-port 65000;<br>
omapi-port 999;<br>
log-facility local7;<br>
default-lease-time 3600;<br>
max-lease-time 7200;<br>
allow unknown-clients;<br>
deny duplicates;<br>
<br>
option domain-name-servers 8.8.4.4, 8.8.8.8;<br>
<br>
# Option 43 suboption 1: <a class="moz-txt-link-freetext" href="http://192.168.8.102:7547">http://192.168.8.102:7547</a><br>
option vendor-encapsulated-options
01:27:68:74:74:70:3A:2F:2F:31:39:32:2E:31:36:38:2E:38:2E:31:30:32:3A:37:35:34:37;<br>
<br>
subnet 192.168.0.0 netmask 255.255.255.0 {}<br>
<br>
shared-network "2.101" {<br>
subnet 192.168.2.0 netmask 255.255.255.0 {}<br>
<br>
subnet 178.45.23.0 netmask 255.255.255.0 {
<br>
option subnet-mask 255.255.255.255;
<br>
option broadcast-address 178.45.23.255;
<br>
option routers 178.45.23.1;
<br>
range 178.45.23.2 178.45.23.254;
<br>
}
<br>
}<br>
<br>
shared-network "98.101" {<br>
subnet 192.168.98.0 netmask 255.255.255.0 {}<br>
<br>
subnet 178.48.11.0 netmask 255.255.255.0 {
<br>
option subnet-mask 255.255.255.255;
<br>
option broadcast-address 178.48.11.255;
<br>
option routers 178.48.11.1;
<br>
range 178.48.11.2 178.48.11.254;
<br>
}
<br>
}<br>
<br>
include "/etc/dhcp/fixed.conf";<br>
<br>
#######################################################<br>
<br>
<br>
Il 16/12/2010 14:59, Simon Hobson ha scritto:
<blockquote cite="mid:p0624082bc92fcaaf83f8@simon.thehobsons.co.uk"
type="cite">marco perugini wrote:
<br>
<br>
<blockquote type="cite">my dhcp server [which is 192.168.0.110]
can receive DHCPDISCOVER from two different gateways
[192.168.98.101 and 192.168.2.101]. i have several entire
subnets to assign to 98.101's requests and several other entire
subnets to assign to 2.101's requests. so the only feature i'm
trying to resolve is to differentiate who's asking me for an
addr.
<br>
i thought something like this would work best:
<br>
<br>
shared-network "98.101" {
<br>
allow unknown-clients;
<br>
deny duplicates;
<br>
<br>
# gw1 subnet
<br>
subnet 192.168.98.0 netmask 255.255.255.0 {
<br>
}
<br>
# my subnet
<br>
subnet 192.168.0.0 netmask 255.255.255.0 {
<br>
}
<br>
# to assign subnet
<br>
subnet 178.45.23.0 netmask 255.255.255.0 {
<br>
option subnet-mask 255.255.255.255;
<br>
option broadcast-address 178.45.23.255;
<br>
option routers 178.45.23.1;
<br>
range 178.45.23.2 178.45.23.254;
<br>
}
<br>
}
<br>
shared-network "2.101" {
<br>
allow unknown-clients;
<br>
deny duplicates;
<br>
<br>
# gw1 subnet
<br>
subnet 192.168.2.0 netmask 255.255.255.0 {
<br>
}
<br>
# my subnet
<br>
subnet 192.168.0.0 netmask 255.255.255.0 {
<br>
}
<br>
# to assign subnet
<br>
subnet 178.48.11.0 netmask 255.255.255.0 {
<br>
option subnet-mask 255.255.255.255;
<br>
option broadcast-address 178.48.11.255;
<br>
option routers 178.48.11.1;
<br>
range 178.48.11.2 178.48.11.254;
<br>
}
<br>
}
<br>
</blockquote>
<br>
Close, but 192.168.0.0 must **NOT** be in the shared-network
statements. It is on a separate network according to your
description.
<br>
<br>
And don't forget that all the clients must be able to route
packets to/from the server - when they renew their leases, it is
done by unicast packets.
<br>
<br>
</blockquote>
</body>
</html>