On 09.01.19 08:14, john doe wrote:
On 1/8/2019 11:31 AM, smicha wrote:
Hi John,
thanks for your reply.
I did some tests with your hints.
On 7.1.2019 17:41, john doe wrote:
Some hints from dnsmasq.conf:
# Give the machine which says its name is "bert" IP address
# 192.168.0.70 and an infin
Hi John,
many thanks for your reply and help.
On 1/10/19 9:28 AM, john doe wrote:
> On 1/9/2019 11:38 AM, MIchael Schleicher wrote:
>>
>> On 09.01.19 08:14, john doe wrote:
>>> On 1/8/2019 11:31 AM, smicha wrote:
>>>> Hi John,
>>>>
>>>>
Hi Geert,
thanks for you mail.
On 1/11/19 6:50 PM, Geert Stappers wrote:
> On Fri, Jan 11, 2019 at 11:29:13AM +0100, MIchael Schleicher (smicha) wrote:
>> On 11.01.19 10:53, john doe wrote:
>>> On 1/11/2019 9:49 AM, MIchael Schleicher (smicha) wrote:
>>>>
Hi,
thanks for your reply.
On 10.01.19 22:25, wkitt...@gmail.com wrote:
On 1/10/19 3:26 PM, Michael Schleicher wrote:
As I said, for Linux VM's, I can set a uniq Client-ID that helps, but on
Windows you can not set define a Client-ID (as far as I know).
isn't this the machine na
Hi John,
On 11.01.19 10:53, john doe wrote:
On 1/11/2019 9:49 AM, MIchael Schleicher (smicha) wrote:
Hi,
thanks for your reply.
On 10.01.19 22:25, wkitt...@gmail.com wrote:
On 1/10/19 3:26 PM, Michael Schleicher wrote:
As I said, for Linux VM's, I can set a uniq Client-ID that helps
Hi John,
thanks for your reply.
On 12.01.19 07:48, john doe wrote:
If the maintaner of dnsmasq has not chimed in that leav us with to options:
- To much on his plate, something could be done to answer this question.
- The issue lies elsewhere (predicting way for MAC addressing).
Ok, than we wa
