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,
>>> 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:
On Thu, Jan 10, 2019 at 05:48:26PM +0530, Sandeep K M wrote:
> On Wed, Jan 9, 2019 at 10:33 PM Simon Kelley wrote:
> > On 04/01/2019 06:25, Sandeep K M wrote:
> > >
> > > Attached are the packet captures:
> > >
> > > 1. Packets exchanged between client and relay (client-relay.pcap)
> > > 2.
Thanks again for the response.
I will be happy to be your tester :)
Its fairly a simple setup with two hosts and a switch. I can create this
any time you want.
Please provide me the instructions. I am using dnsmasq version 2.78.
On Wed, Jan 9, 2019 at 10:33 PM Simon
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:
thanks for your reply.
I did some tests with your
Thanks for the offer. I think there may be a simpler answer, worth
Looking back through the git history, this looks like a bug introduced
into 2.78 by the patches for security problems found by Google, in 2017.
It was fixed for 2.79, by patch
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 name? when i was supporting winwhatever, the install
generated a machine name... that is