[Dnsmasq-discuss] why do I need to forward UDP port and have Upnp enabled?

2016-05-26 Thread Johnny Appleseed 
I tried searching for documentation on why do I need to forward UDP port 
and I found none.  For some reason dnssec-check-unisgned will not work 
without me openeing a port for it to talk to?


___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] dnsmasq lease file not updating properly

2016-05-26 Thread Albert ARIBAUD 
Hello,

Le Thu, 26 May 2016 19:27:33 +0530
Gopi Krishna M  a écrit:

> Hi Albert,
> 
> Thanks for your suggestion.
> 
> I believe it is not in the slaac mode and in dhcpv6 only.
> 
> I confirmed with below things.
> 
> 1) Router advertise, solicit, request things are happening while every
> client getting connected.
> 2) The bit Managed address configuration is set. Checked through
> wireshark. It will be set
> in DHCPv6 only and not for slaac.
> 
> If you believe still it is in slaac mode, Please tell the config
> changes to make
> dnsmasq run as a dhcpv6 server.

OK, so this confirms you're indeed not using SLAAC and are indeed using
DHCPv6. Sorr then, I have no other idea why the leases file does not
mention the DHCPv6 lease -- and no idea if it should, actually.

> Thanks,
> Gopi krishna M

Amicalement,
-- 
Albert.

___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] dnsmasq lease file not updating properly

2016-05-26 Thread Gopi Krishna M 
Hi,

Thanks for your time albert. I will try to look into that.

Thanks,
Gopi krishna M

On Thu, May 26, 2016 at 10:19 PM, Albert ARIBAUD 
wrote:

> Hello,
>
> Le Thu, 26 May 2016 19:27:33 +0530
> Gopi Krishna M  a écrit:
>
> > Hi Albert,
> >
> > Thanks for your suggestion.
> >
> > I believe it is not in the slaac mode and in dhcpv6 only.
> >
> > I confirmed with below things.
> >
> > 1) Router advertise, solicit, request things are happening while every
> > client getting connected.
> > 2) The bit Managed address configuration is set. Checked through
> > wireshark. It will be set
> > in DHCPv6 only and not for slaac.
> >
> > If you believe still it is in slaac mode, Please tell the config
> > changes to make
> > dnsmasq run as a dhcpv6 server.
>
> OK, so this confirms you're indeed not using SLAAC and are indeed using
> DHCPv6. Sorr then, I have no other idea why the leases file does not
> mention the DHCPv6 lease -- and no idea if it should, actually.
>
> > Thanks,
> > Gopi krishna M
>
> Amicalement,
> --
> Albert.
>

-- 


DISCLAIMER

The information in this e-mail is confidential and may be subject to legal 
privilege. It is intended solely for the addressee. Access to this e-mail 
by anyone else is unauthorized. If you have received this communication in 
error, please address with the subject heading "Received in error," send to 
i...@msystechnologies.com,  then delete the e-mail and destroy any copies of 
it. If you are not the intended recipient, any disclosure, copying, 
distribution or any action taken or omitted to be taken in reliance on it, 
is prohibited and may be unlawful. The views, opinions, conclusions and 
other information expressed in this electronic mail and any attachments are 
not given or endorsed by the company unless otherwise indicated by an 
authorized representative independent of this message.
MSys cannot guarantee that e-mail communications are secure or error-free, 
as information could be intercepted, corrupted, amended, lost, destroyed, 
arrive late or incomplete, or contain viruses, though all reasonable 
precautions have been taken to ensure no viruses are present in this e-mail. 
As our company cannot accept responsibility for any loss or damage arising 
from the use of this e-mail or attachments we recommend that you subject 
these to your virus checking procedures prior to use
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] dnsmasq lease file not updating properly

2016-05-26 Thread Gopi Krishna M 
Hi Albert,

Thanks for your suggestion.

I believe it is not in the slaac mode and in dhcpv6 only.

I confirmed with below things.

1) Router advertise, solicit, request things are happening while every
client getting connected.
2) The bit Managed address configuration is set. Checked through wireshark.
It will be set
in DHCPv6 only and not for slaac.

If you believe still it is in slaac mode, Please tell the config changes to
make
dnsmasq run as a dhcpv6 server.

Thanks,
Gopi krishna M


On Wed, May 25, 2016 at 8:20 PM, Albert ARIBAUD 
wrote:

> Hi,
>
> Le Wed, 25 May 2016 19:17:31 +0530
> Gopi Krishna M  a écrit:
>
> > Hi All,
> >
> > I have been using dnsmasq 2.70 vesrion as dhcp server for ipv4 and
> > ipv6. My lease file is not getting updated properly when
> > running dnsmasq. It is updating properly for ipv4  but not correct
> > for ipv6.
> >
> >  #cat /etc/dnsmasq_new.leases
> > 2082886681 00:80:48:4b:83:12 192.168.10.161 host-mysy *
> > duid 00:01:00:01:43:b8:34:78:00:80:a3:a0:bb:38
> > 2082843195 1212908306 *18:2001:2002:2003:: **
> > 00:01:00:01:00:80:10:7e:ea:09
> >
> > It is marked as above and its actual lease ip is
> > *2001:2002:2003::10a* but its not showing. Meanwhile even if we
> > connect multiple clients then the same *18:2001:2002:2003:: *is
> > getting repeated. Meanwhile it is not showing the
> > proper mac also.
> >
> > for your kind ref:
> >
> > config file
> > # cat /etc/dnsmasq_gateway.conf
> > interface=lan0
> > except-interface=lo
> > bind-interfaces
> > dhcp-range=192.168.10.20, 192.168.10.254, 14h
> > dhcp-range=2001:2002:2003::105, 2001:2002:2003::110, 64, 14h
> > enable-ra
> >
> > Interface IP: 192.168.10.1
> > IPv6: 2001:2002:2003::100
> >
> > running as
> >
> >
> > *dnsmasq -C /etc/dnsmasq_gateway.conf -l /etc/dnsmasq_new.leases*
> > Please tell your suggestions.
> >
> > Note: Clients are getting IPv4 and IPv6 properly. Everything is fine
> > apart from updating the lease file. Compiled for ARM(linux 3.10)
> >
> > Thanks in advance.
> >
> > Regards,
> > Gopi krishna M
>
> (anyone feel free to correct me if I got the following wrong)
>
> You are using SLAAC for IPv6 configuration. In this mode, it is the
> client, not the DHCP server, which selects its own IPv6.
>
> Therefore there are no actual IPv6 leases: dnsmasq just informs the
> client about the /64 subnet under which the client, not dnsmasq, shall
> select its address; the client does not inform dnsmasq back.
>
> This is /probably/ why the actual address does not show up in the lease
> file.
>
> If you want dnsmasq to control which address the client receives (and
> possibly log this in the lease file) then you should use DHCPv6 rather
> than SLAAC.
>
> Amicalement,
> --
> Albert.
>

-- 


DISCLAIMER

The information in this e-mail is confidential and may be subject to legal 
privilege. It is intended solely for the addressee. Access to this e-mail 
by anyone else is unauthorized. If you have received this communication in 
error, please address with the subject heading "Received in error," send to 
i...@msystechnologies.com,  then delete the e-mail and destroy any copies of 
it. If you are not the intended recipient, any disclosure, copying, 
distribution or any action taken or omitted to be taken in reliance on it, 
is prohibited and may be unlawful. The views, opinions, conclusions and 
other information expressed in this electronic mail and any attachments are 
not given or endorsed by the company unless otherwise indicated by an 
authorized representative independent of this message.
MSys cannot guarantee that e-mail communications are secure or error-free, 
as information could be intercepted, corrupted, amended, lost, destroyed, 
arrive late or incomplete, or contain viruses, though all reasonable 
precautions have been taken to ensure no viruses are present in this e-mail. 
As our company cannot accept responsibility for any loss or damage arising 
from the use of this e-mail or attachments we recommend that you subject 
these to your virus checking procedures prior to use
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] Segmentation fault with newest dnsmasq 2.76

2016-05-26 Thread Simon Kelley 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Since this seems to be easily reproducible, it should be fairly easy
to chase down.

Ideally, we need to recomiple dnsmasq with debugging symbols, and the
then run it under gdb to get information about exactly where it's
failing. If you know how to do that, please go ahead, if you're not
sure come back here and I'll walk you through the process.

Posting the contents of /etc/dnsmasq.conf would be useful too.


Cheers,

Simon.


On 25/05/16 19:27, Andreas Kuropka wrote:
> Hi,
> 
> I've noticed that dnsmasq gets killed once a VPN client (SoftEther
> VPN with bridge configuration) tries to aquire an IP.
> 
> ● dnsmasq.service - A lightweight DHCP and caching DNS server 
> Loaded: loaded (/usr/lib/systemd/system/dnsmasq.service; enabled;
> vendor preset: disabled) Active: failed (Result: signal) since Mi
> 2016-05-25 20:16:02 CEST; 13s ago Docs: man:dnsmasq(8) Process:
> 10868 ExecStart=/usr/bin/dnsmasq -k --enable-dbus --user=dnsmasq
> --pid-file (code=killed, signal=SEGV) Process: 10863
> ExecStartPre=/usr/bin/dnsmasq --test (code=exited,
> status=0/SUCCESS) Main PID: 10868 (code=killed, signal=SEGV)
> 
> Mai 25 20:14:41 raspberry dnsmasq-dhcp[10868]: read /etc/ethers -
> 22 addresses Mai 25 20:14:41 raspberry systemd[1]: Started A
> lightweight DHCP and caching DNS server. Mai 25 20:16:02 raspberry
> dnsmasq-dhcp[10868]: DHCPDISCOVER(br0) ca:53:c6:b7:2d:59 Mai 25
> 20:16:02 raspberry dnsmasq-dhcp[10868]: DHCPOFFER(br0)
> 192.168.188.20 ca:53:c6:b7:2d:59 Mai 25 20:16:02 raspberry
> systemd[1]: dnsmasq.service: Main process exited, code=killed,
> status=11/SEGV Mai 25 20:16:02 raspberry systemd[1]:
> dnsmasq.service: Unit entered failed state. Mai 25 20:16:02
> raspberry systemd[1]: dnsmasq.service: Failed with result
> 'signal'.
> 
> This did not happen with 2.75 and before:
> 
> ● dnsmasq.service - A lightweight DHCP and caching DNS server 
> Loaded: loaded (/usr/lib/systemd/system/dnsmasq.service; enabled;
> vendor preset: disabled) Active: active (running) since Mi
> 2016-05-25 20:16:55 CEST; 4min 38s ago Docs: man:dnsmasq(8) 
> Process: 11011 ExecStartPre=/usr/bin/dnsmasq --test (code=exited,
> status=0/SUCCESS) Main PID: 11018 (dnsmasq) Tasks: 1 (limit: 512) 
> CGroup: /system.slice/dnsmasq.service └─11018 /usr/bin/dnsmasq -k
> --enable-dbus --user=dnsmasq --pid-file
> 
> Mai 25 20:16:55 raspberry dnsmasq[11018]: read /etc/hosts - 26
> addresses Mai 25 20:16:55 raspberry dnsmasq-dhcp[11018]: read
> /etc/ethers - 22 addresses Mai 25 20:17:05 raspberry
> dnsmasq-dhcp[11018]: DHCPDISCOVER(br0) ca:53:c6:b7:2d:59 Mai 25
> 20:17:05 raspberry dnsmasq-dhcp[11018]: DHCPOFFER(br0)
> 192.168.188.20 ca:53:c6:b7:2d:59 Mai 25 20:17:05 raspberry
> dnsmasq-dhcp[11018]: DHCPREQUEST(br0) 192.168.188.20
> ca:53:c6:b7:2d:59 Mai 25 20:17:05 raspberry dnsmasq-dhcp[11018]:
> DHCPACK(br0) 192.168.188.20 ca:53:c6:b7:2d:59 w987098 Mai 25
> 20:17:05 raspberry dnsmasq-dhcp[11018]: DHCPINFORM(br0)
> 192.168.188.20 00:8e:18:1b:1f:35:58:f2:42:b4:be:95:a7:32:34:8e:23 
> Mai 25 20:17:05 raspberry dnsmasq-dhcp[11018]: DHCPACK(br0)
> 192.168.188.20 00:8e:18:1b:1f:35:58:f2:42:b4:be:95:a7:32:34:8e:23
> w987098
> 
> I'm using RPi3 with Arch Linux arm.
> 
> I just want to give you this to your information; if you need
> further please let me know.
> 
> Best Regards,
> 
> Andreas
> 
> 
> ___ Dnsmasq-discuss
> mailing list Dnsmasq-discuss@lists.thekelleys.org.uk 
> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBCAAGBQJXRr4CAAoJEBXN2mrhkTWip68P/RMpg1HmdpZNbwcFveauArqe
gZq3CNsCTLpCECsRVeym1IFOf9iCLEXwzJ1mC29BmqamQxlb2Nyz8MIiF7Yx1Xb5
TsIsuQZ6u/7XEBWVv4aKfXoUa8Kfvohg/TRBy4knJA9elsWTlgLZAvfWyHU1Ow+L
cqySpb4Cb/a3Chot4n+8Hr0F2iD3uS11iVnlDayZi0Oahk+5anhlX1NKEMdQ2Bbk
xL+FTu/+TOOI+7P7+rWWxTgUKYKICSlG0nITmKgA0kWK4m2xPohirmxt+BFKAKNd
SXdlV4ZQzQyQId2ogIhJOlBVwcue95IhZRnIBWBO1KK3KUhXV2m6Rzs4/y1arm+s
6vHpX0RRN8650xG7Dd9MtPW7DLZZ8u1L8Mg1agPTgpQWt0jTUAWV7/dcr/rigqke
/qZv6n6SL/GAzY3T8EUeI8YCRmvQ+ESLmDqoEiAGmJFeDzLTwaxN91PtdjAyVR9G
3KdsD6QKyQlu6jgGC7gejJhMj/bghX94GRy7D7p4dHopajYrz6LozAE3/EnY86cU
yf4sF8Sim1bUDGEhdx0LjICb0Q8x8RoJoHyTGdYF3XV23UpQKNJnr6Z39h1tky67
7KRQze1A2UVzOL87CMhnojQ4htjzIZKVgMWbhfxzV2bo4R1HDwbPjita5tut+AK5
zSksHjKvnZStadIXstWC
=Apoe
-END PGP SIGNATURE-

___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss