DHCP server on a different subnet

[Simon Hobson]

Lyle Giese wrote:

>But if an interface is on the same broadcast domain, but on a 
>different subnet, how will that interface determine what subnet the 
>broadcast packet came from?  I don't think it can.

You would need a lot of shared network statements. Eg, if 1.2.3.96/29 
was the client's subnet, you might have :

shared-subnet ninety-six {
   subnet 1.2.3.96.0 ... {
     option routers 1.2.3.97 ;
     range 1.2.3.98 1.2.3.102 ;
   }
   subnet 192.168.3.96 ... {
   }
}
The DHCP server could be on any address in the 192.168.3.96 subnet. 
It would recognise that the broadcast request arrived on that 
interface, and work out from the shared network that 1.2.3.96 
addresses are also valid on that wire. When broadcasting responses 
back to the client, it would use that interface.

When the client came to unicast a renewal, it would do so to the 
servers public IP (you may have to explicitly set server-identifier), 
and the packet would go via the normal routing to get to the server. 
When replying, the server would also send the packet back using it's 
normal routing table - it wouldn't have a direct attach route to a 
1.2.3.96/29 address since it doesn't have an IP in that range on the 
directly attached interface.

But I'm not entirely sure what this gets anyone, what sort of routing 
device doesn't have a BOOTP/DHCP Relay Agent ?

-- 
Simon Hobson

Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed
author Gladys Hobson. Novels - poetry - short stories - ideal as
Christmas stocking fillers. Some available as e-books.