From: Chris Lawrence <lordsutch@gmail.com>
To: "<cerowrt-devel@lists.bufferbloat.net>"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] dnsmasq ipv6 stuff
Date: Tue, 22 Jan 2013 13:52:15 -0500 [thread overview]
Message-ID: <CANJCZGLcLJEKYnwHNo8+aG92W=QcLkrJEkOz18=v6Lef7YZjxw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5iK2XgH_KiQbkh9iuko+VeR27SUwRwU1+SEon_dfYiUg@mail.gmail.com>
On Tue, Jan 22, 2013 at 1:40 AM, Dave Taht <dave.taht@gmail.com> wrote:
> I think that's this in /etc/dnsmasq.conf
>
> dhcp-range=se00,1234::, ra-stateless, ra-names
> dhcp-range=sw00,1234::, ra-stateless, ra-names
> dhcp-range=sw10,1234::, ra-stateless, ra-names
> dhcp-range=gw00,1234::, ra-stateless, ra-names
> dhcp-range=gw10,1234::, ra-stateless, ra-names
>
> It's kind of unclear to me what 1234 could be replaced with.
> "ce30" works for me...
Using ::1 on each will autoassign the addresses based on the address
of the interface, which seems like a sensible default no matter what
network address you have. Having said that I found that with
ra-stateless enabled, at least one device on my network would send
DHCPv6 requests that crashed dnsmasq. So I have:
dhcp-range=::1,constructor:se00,ra-names
(etc.)
I think with test11 that can be further simplified to:
dhcp-range=::1,constructor:*,ra-names
This uses SLAAC only, which seems sufficient for my network purposes.
I tried adding an end to the range to see if that was the problem with
DHCP, but that doesn't seem to help, at least in test10.
The other thing I noticed in 3.7.2-4 is that both dnsmasq and
dnsmasq-dhcpv6 are installed, but the dnsmasq binary is actually the
non-v6 version unless you reinstall the dnsmasq-dhcpv6 package
(according to upstream OpenWRT, only one or the other should be
installed since they conflict).
Chris
next prev parent reply other threads:[~2013-01-22 18:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 6:40 Dave Taht
2013-01-22 18:52 ` Chris Lawrence [this message]
2013-01-22 22:19 ` Maciej Soltysiak
2013-01-22 23:12 ` Dave Taht
2013-01-23 0:14 ` Chris Lawrence
2013-01-23 7:24 ` Phil Pennock
2013-01-25 19:21 ` Török Edwin
[not found] <mailman.5741.1358880757.1742.cerowrt-devel@lists.bufferbloat.net>
2013-01-25 1:47 ` Richard Brown
[not found] ` <FC4C3393-3EA4-4130-915E-373FAA458A32@intermapper.com>
2013-01-25 1:55 ` Richard Brown
2013-01-30 21:40 Simon Kelley
2013-01-30 23:44 ` Chris Lawrence
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANJCZGLcLJEKYnwHNo8+aG92W=QcLkrJEkOz18=v6Lef7YZjxw@mail.gmail.com' \
--to=lordsutch@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox