Hi
On Fri, Dec 4, 2015 at 9:01 PM, Jason Haar wrote:
> On 05/12/15 14:05, Selva Nair wrote:
> > That would be fine too. Say the second client gets 10.200.0.3 with
> > dhcp server at 10.200.0.254 (the default). The client will send the
> > dhcp packet to .254 (or to 255.255.255.255 if its the fir
On 05/12/15 14:05, Selva Nair wrote:
> That would be fine too. Say the second client gets 10.200.0.3 with
> dhcp server at 10.200.0.254 (the default). The client will send the
> dhcp packet to .254 (or to 255.255.255.255 if its the first time), the
> tap driver will reply to it and all will be fine
On Fri, Dec 4, 2015 at 7:16 PM, Jan Just Keijser wrote:
> Hi Selva, *,
>
>
Hi!
>
> On 04-Dec-15 06:55, Selva Nair wrote:
>
> On Fri, Dec 4, 2015 at 12:01 AM, Leroy Tennison <
> leroy.tenni...@verizon.net> wrote:
>
>> A couple of thoughts come to mind. First, if node 254 is always active
>> the
Hi Selva, *,
On 04-Dec-15 06:55, Selva Nair wrote:
On Fri, Dec 4, 2015 at 12:01 AM, Leroy Tennison
mailto:leroy.tenni...@verizon.net>> wrote:
A couple of thoughts come to mind. First, if node 254 is always
active
then "well-behaved" DHCP clients should test for that and never a
