dhcp subnet, different network relay.

Glenn Satchell glenn.satchell at uniq.com.au
Tue Apr 9 04:13:12 UTC 2013


Looks like you need a shared-network around the 58 and 14 subnet
definitions. eg:

shared-network {
  subnet 58.***.***.0 netmask 255.0.0.0 {
  }

  subnet 14.137.118.0 netmask 255.255.255.0 {
         ## dhcp start  and end IP range ##
         range 14.137.118.2 14.137.118.253;
         option subnet-mask 255.255.255.0;        ## subnet
         option broadcast-address 14.137.118.255; ## broadcast
         option routers 14.137.118.254;           ## router IP
  }
}

The values in the subnet line *must* match the ranges you offer within
that subnet.

Have a look in the dhcpd.conf man page for more details.

regards,
-glenn

On Tue, April 9, 2013 11:09 am, Simon Collyer wrote:
> Hi all,
>
> Having a few issues with getting the dhcp server to act as a "proper"
> relay.
>
> Current setup or process is as follows:
>
>
> (home user) -> (wholesale) -> **DHCP transaction** --> (our DHCP server)
>     ^^---------------------------DHCP REPLY-----------------------^^
>
> So the endpoint customer, is trying to get a DHCP address which is passed
> through our wholesaler.  We then want to route a different range to
> the customer than what we have seen the address as:
>
> Currently the config sits at:
>
>
> subnet 203.***.***.0 netmask 255.255.255.0 {
> }
> subnet 58.***.***.0 netmask 255.0.0.0 {
>          ## dhcp start  and end IP range ##
>          range 14.***.***.2 14.***.***.253;
>          option subnet-mask 255.255.255.0;     ## subnet
>          option broadcast-address 14.***.***.255; ## broadcast
>          option routers 14.***.***.254; ## router IP
>
> }
>
> subnet 14.***.***.0 netmask 255.255.255.0 {
>          ## dhcp start  and end IP range ##
>          range 14.137.118.2 14.137.118.253;
>          option subnet-mask 255.255.255.0;     ## subnet
>          option broadcast-address 14.137.118.255; ## broadcast
>          option routers 14.137.118.254; ## router IP
> }
>
> Obviously this does not work and we are seeing the dhcp request being
> proxied
> through to us from a different subnet than the one we want to lease out.
>
>
> DHCPDISCOVER from a4:b1:e9:6c:10:34 via 58.***.***.194: network
> 58.***.***.0/24: no free leases
>
> I've change the configuration around and removed the 58.*** range, but
> get the following:
>
> DHCPDISCOVER from a4:b1:e9:6c:10:34 via 58.***.***.194: unknown
> network segment
>
>
> What do I need to change or do to allow any request coming through to
> hand out what range I specify?
>
> Any thoughts, help would be appreciated.
>
> Have been through google, but their is nothing that matches * similar*
> to what I need to do.  Perhaps I may not have had enough coffee yet as
> well :-)
>
> //Simon
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
>




More information about the dhcp-users mailing list