Re: DHCP unicast

2018-05-01 Thread Alexander Mukhin
On Mon, Apr 30, 2018 at 05:32:30PM +0200, Denys Vlasenko wrote: > On Sat, Apr 28, 2018 at 11:12 AM, Alexander Mukhin > wrote: > > Dear Denys, > > > > I have a doubt on your commit a6a3ad327360669e0c12552f680382e3b9713489, > > when you introduced a requirement that

Re: DHCP unicast

2018-04-30 Thread Denys Vlasenko
On Sat, Apr 28, 2018 at 11:12 AM, Alexander Mukhin wrote: > Dear Denys, > > I have a doubt on your commit a6a3ad327360669e0c12552f680382e3b9713489, > when you introduced a requirement that the DHCP Server ID must be > directly reachable. > > Please consider a very

DHCP unicast

2018-04-28 Thread Alexander Mukhin
Dear Denys, I have a doubt on your commit a6a3ad327360669e0c12552f680382e3b9713489, when you introduced a requirement that the DHCP Server ID must be directly reachable. Please consider a very common case when a DHCP relay is used. Here, the Server ID will never be a direcly connected address.