-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 23/01/17 17:45, wkitt...@gmail.com wrote:
> On 01/23/2017 06:49 AM, Simon Kelley wrote:
>> Actually, it's permitted to have more than once DHCP server, but
>> the client is entitled to wait for some time to hear from them
>> all, and then pick w
On Mon, Jan 23, 2017 at 12:45:28PM -0500, wkitt...@gmail.com wrote:
> On 01/23/2017 06:49 AM, Simon Kelley wrote:
> > Actually, it's permitted to have more than once DHCP server, but the client
> > is entitled to wait for some time to hear from them all, and then pick
> > whichever one it prefers,
On 01/23/2017 06:49 AM, Simon Kelley wrote:
Actually, it's permitted to have more than once DHCP server, but the client
is entitled to wait for some time to hear from them all, and then pick
whichever one it prefers,
that's interesting... i can't say that i've ever heard that before... maybe it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Actually, it's permitted to have more than once DHCP server, but the
client is entitled to wait for some time to hear from them all, and
then pick whichever one it prefers, so trying to implement server
priority by speed-of-reply is doomed to failure
On 01/22/2017 08:02 PM, Sebastian Tarach wrote:
Hello,
I'm trying to make *dnsmasq* work on my Debian Virtualbox guest but I keep
getting reply from my VBox host DHCP first.
there should only ever be one DHCP server running on any net segments... turn
off or otherwise disable all the others a
Hello,
I'm trying to make *dnsmasq* work on my Debian Virtualbox guest but I keep
getting reply from my VBox host DHCP first.
I have configured bridge ( br0 ) using openvswitch:
$ ovs-vsctl show
> cbda5c6b-c9ba-4fb4-8143-a1f0683e1e96
> Manager "ptcp:6640"
> Bridge "br0"
> Port "e
