Re: [Dnsmasq-discuss] IPv6 Router Advertisements not working

2018-01-23 Thread Matthew Keeler 
Yes, one of my interfaces is fd01::1/64.

I just got it working actually. In my case I have a test lab setup with a
couple networks. The first is a smaller /24 with no ipv6 that is generally
accessible in my company. The second is a /16 using the 198.18/15 address
space for testing with the fd01::/64 ipv6 addressing. Originally I had two
dnsmasq configurations to provide DNS/DHCP (1 per network). When I switched
over to a single configuration with all the dhcp-option, dhcp-range
configurations including the network interface they should be applicable
to, things just started working. I am not sure why it helped but either way
I would rather have a single configuration anyways.

-- 
Matthew Keeler

On January 23, 2018 at 12:18:47, Erik Nordmark (nordm...@sonic.net) wrote:

On 01/22/2018 02:27 AM, Andy Hawkins wrote:
> Hi,
> In article <8534ac3c-30d0-095a-8bde-179bdbe8f...@thekelleys.org.uk>,
> Simon Kelley wrote:
>> Do you have an interface configured with an address in fd01::/64 ?
>
> Is this a requirement? radvd is able to send advertisements out on an
> interface that has no IPv6 address configured (indeed, I have been using
> this facility to automatically configure the interface that router
> advertisements are being sent on).
>
> Would be nice to be able to do the same with dnsmasq without having to
> manually configure the IPv6 address of the interface.

Andy,

I've run into this limitation as well, due to using the "no on-link
prefixes" option in neighbor discovery (meaning that I use dhcpv6 for
address assignment, and radvd doesn't advertise any onlink prefix).

This means I don't have a /64 prefix configured on any interface which
matches the range from which dnsmasq assigns IPv6 addresses.

My workaround is to remove the /64 check from dnsmasq (see below). I've
been meaning to discuss this on the list.

Erik


diff -r -u ../dnsmasq-orig/dnsmasq-2.75/src/option.c src/option.c
--- ../dnsmasq-orig/dnsmasq-2.75/src/option.c 2015-07-30
12:59:07.0 -0
700
+++ src/option.c 2017-06-13 15:14:58.109166818 -0700
@@ -2734,9 +2734,6 @@
ret_err(_("prefix length must be exactly 64 for subnet constru
ctors"));
}

- if (new->prefix < 64)
- ret_err(_("prefix length must be at least 64"));
-
if (!is_same_net6(>start6, >end6, new->prefix))
ret_err(_("inconsistent DHCPv6 range"));


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

Re: [Dnsmasq-discuss] IPv6 Router Advertisements not working

2018-01-23 Thread Erik Nordmark 

On 01/22/2018 02:27 AM, Andy Hawkins wrote:

Hi,
In article <8534ac3c-30d0-095a-8bde-179bdbe8f...@thekelleys.org.uk>,
Simon Kelley wrote:

Do you have an interface configured with an address in fd01::/64 ?


Is this a requirement? radvd is able to send advertisements out on an
interface that has no IPv6 address configured (indeed, I have been using
this facility to automatically configure the interface that router
advertisements are being sent on).

Would be nice to be able to do the same with dnsmasq without having to
manually configure the IPv6 address of the interface.


Andy,

I've run into this limitation as well, due to using the "no on-link 
prefixes" option in neighbor discovery (meaning that I use dhcpv6 for 
address assignment, and radvd doesn't advertise any onlink prefix).


This means I don't have a /64 prefix configured on any interface which 
matches the range from which dnsmasq assigns IPv6 addresses.


My workaround is to remove the /64 check from dnsmasq (see below). I've 
been meaning to discuss this on the list.


   Erik


diff -r -u ../dnsmasq-orig/dnsmasq-2.75/src/option.c src/option.c
--- ../dnsmasq-orig/dnsmasq-2.75/src/option.c	2015-07-30 
12:59:07.0 -0

700
+++ src/option.c2017-06-13 15:14:58.109166818 -0700
@@ -2734,9 +2734,6 @@
  ret_err(_("prefix length must be exactly 64 for subnet constru
ctors"));
  }

-   if (new->prefix < 64)
- ret_err(_("prefix length must be at least 64"));
-   
if (!is_same_net6(>start6, >end6, new->prefix))
  ret_err(_("inconsistent DHCPv6 range"));


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

Re: [Dnsmasq-discuss] Syntax for srv-records

2018-01-23 Thread Guido Schmidt 

Am 18.01.2018 um 22:28 schrieb Simon Kelley:

My guess is that you need to add the domain to the last two.

eg _sip._tcp gets the domain (as specified to dnsmasq by the domain
keyword) added automatically, so assuming

domain=guido.org
srv-host=_sip._tcp,sipx2.example.org,5060,20,10

You'll get a SRV records called
_sip._tcp.guido.org

once you start adding anything else, dnsmasq assumes you're specifying
the domain, so


  srv-host="_sip._tcp.rr",sipx2.example.org,5070,20,10

gives you a record called _sip._tcp.rr, but you probably want a record
called _sip._tcp.rr.guido.org, so you need to specify that completely

srv-host="_sip._tcp.rr.guido.org",sipx2.example.org,5070,20,10



Simon,

thanks, problem solved! Would have never guessed that.

Guido



On 16/01/18 12:44, Guido Schmidt wrote:

I'm trying to set up some srv-records for sip. These are the records I
have in bind syntax:

;; RECORDS: rr
_sip._tcp    IN    SRV    30 10 5060 sipx2
_sip._udp    IN    SRV    30 10 5060 sipx2
_sips._tcp    IN    SRV    30 10 5061 sipx2
_sip._tls    IN    SRV    30 10 5061 sipx2
_sip._tcp.rr    IN    SRV    30 10 5070 sipx2
_sip._tcp.rr.sipx2    IN    SRV    10 10 5070 sipx2


I successfully managed to translate the first four to

srv-host=_sip._tcp,sipx2.example.org,5060,20,10
srv-host=_sip._udp,sipx2.example.org,5060,20,10
srv-host=_sips._tcp,sipx2.example.org,5061,20,10
srv-host=_sip._tls,sipx2.example.org,5061,20,10


But the last two won't work:

srv-host="_sip._tcp.rr",sipx2.example.org,5070,20,10
srv-host="_sip._tcp.rr.sipx2",sipx2.example.org,5070,20,10

Can someone enlighten me what would be the right syntax?

Guido


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

[Dnsmasq-discuss] --synth-domain enhancement

2018-01-23 Thread Andy Hawkins 
Hi,

I'm contemplating a move from bind and isc-dhcpd to dnamasq. 

One of the features of bind that I take advantage of in my domain is
generating sequences of DNS entries using a single line. For example, in my
zone file I have:

$GENERATE 50-70 dyn-${-50}  IN  A   192.168.202.$

This will generate the following DNS entries:

dyn-0.gently.org.uk on address 192.168.202.50
dyn-1.gently.org.uk on address 192.168.202.51

...

dyn-19.gently.org.uk on address 192.168.202.69
dyn-20.gently.org.uk on address 192.168.202.70

I realise that dnsmasq has the 'synth-domain' option, but the names
generated by this are a little ugly. Is there any chance an enhancement
could be made to so something similar to the facilities available in bind?

Thanks

Andy


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