From: Dave Taht <dave.taht@gmail.com>
To: Steven Barth <cyrus@openwrt.org>
Cc: Matt Mathis <mattmathis@google.com>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] 6relayd
Date: Sun, 5 Jan 2014 19:48:59 -0800 [thread overview]
Message-ID: <CAA93jw7kjVK5Sqfgb_oodwZ5bJHHTmjXUBYpMZyAZs3-qQFRYQ@mail.gmail.com> (raw)
In-Reply-To: <52C7D4CA.9030108@openwrt.org>
On Sat, Jan 4, 2014 at 1:30 AM, Steven Barth <cyrus@openwrt.org> wrote:
> On 03.01.2014 19:43, Dave Taht wrote:
>>
>>
>> I was also experiencing a race condition with dnsmasq, while I had it
>> enabling
>> ra and dhcpv6 via dnsmasq. At the moment that's turned off by default, but
>> I did rather prefer having dns names for my ipv6 addresses...
>
> Well 6relayd and odhcpd collect hostnames of clients acquired via stateful
> DHCPv6 and export them to dnsmasq in an additional hostfiles. At least that
> seemed to work when I last tried it a few months ago. The only disadvantage
> is that there is no "ra-names" feature there.
Getting to names from dhcpv4 to slaac was a neat hack and a potential
RFC. So i figure spending the time to add the same functionality into
into something other than dnsmasq would be useful towards writing that
rfc.
>
>>
>> is there a good way for 6relayd and dnsmasq-dhcpv6 to co-exist?
>
> Ideally they could coexist in a way that you could select dnsmasq and / or
> odhcpd for different interfaces on the same machine. odhcpd supports that
> but dnsmasq the last time I've looked seemed to use a single socket binding
> to all interfaces for DHCP/v6 which prevents coexistance from working
> correctly because odhcpd / 6relayd can't bind the socket after dnsmasq did
> and vice versa.
>
>
>>
>>> Feel free to provide me with some debugging information of the system
>>> while
>>> PD fails for you so I can have a look at the probable cause:
>>>
>>> * "ifstatus ge00" (replace ge00 with your IPv6 upstream interface)
>>> * "ip addr list dev ge01" (replace ge01 with the interface your
>>> downstream
>>> router is connected)
>>> * "ps | grep 6relayd"
>>>
>>> Anyway I will migrate all the stuff to odhcpd soon (it's successor which
>>> shares a good part of the codebase but is a bit better integrated with
>>> the
>>> rest of the environment).
>>
>> same question re dnsmasq.
>
> Yeah as pointed out coexistence is a matter of binding sockets. odhcpd will
> bring the functionality of dynamically enabling / disabling DHCPv4/v6 on
> interfaces without restarting the daemon and loosing state. This is one of
> the main reasons for the change and very much eases things for high-level
> protocols that do dynamic wan/lan detection.
>
>
> Cheers,
>
> Steven
>
>
>
>>
>>>
>>> Regards,
>>>
>>> Steven
>>>
>>>
>>>
>>> On 03.01.2014 18:31, Dave Taht wrote:
>>>>
>>>> On Fri, Jan 3, 2014 at 11:50 AM, cb.list6 <cb.list6@gmail.com> wrote:
>>>>>
>>>>>
>>>>>
>>>>> On Fri, Jan 3, 2014 at 8:40 AM, Dave Taht <dave.taht@gmail.com> wrote:
>>>>>>
>>>>>> At one level I am happy to figure out this is a recently introduced
>>>>>> bug.
>>>>>>
>>>>>> On the other hand I am not sure if it is 6relayd.
>>>>>>
>>>>>> What version of cero was working for you?
>>>>>
>>>>>
>>>>> I am not entirely sure, but i think it was from September.
>>>>>
>>>>> CB
>>>>
>>>> At the moment I lack the ability to debug the breakage in ipv6 dhcp-pd
>>>> (which is odhcpd) (I am travelling).
>>>>
>>>> I will on my next stop next week (tuesday) setup a dhcpv6pd server and
>>>> see what I can see.
>>>>
>>>>>> On Jan 3, 2014 12:21 AM, "cb.list6" <cb.list6@gmail.com> wrote:
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I have been using CeroWRT on Comcast with a 3800 for about 6 month.
>>>>>>> The
>>>>>>> DHCP-PD config has always been a little unstable for me, but working.
>>>>>>>
>>>>>>> I recently upgraded to:
>>>>>>>
>>>>>>> root@cerowrt:/etc/config# uname -a
>>>>>>> Linux cerowrt 3.10.24 #1 Tue Dec 24 10:50:15 PST 2013 mips GNU/Linux
>>>>>>>
>>>>>>> My WAN gets a /128, but i cannot get DHCP-PD to work to get addresses
>>>>>>> on
>>>>>>> the rest of my interfaces. The router does seem to have good IPv6
>>>>>>> access.
>>>>>>>
>>>>>>>
>>>>>>> I fiddled with the 6relayd config and came up with this, but it does
>>>>>>> not
>>>>>>> work. Any pointers on how to get this back on track? The result of
>>>>>>> the
>>>>>>> below config is that the /128 from the WAN interfaces is now present
>>>>>>> on
>>>>>>> all
>>>>>>> the interfaces but my attached computers get no addresses.
>>>>>>>
>>>>>>>
>>>>>>> config server 'default'
>>>>>>> option rd 'server'
>>>>>>> option dhcpv6 'server'
>>>>>>> option management_level '1'
>>>>>>> list network 'ge01'
>>>>>>> list network 'gw00'
>>>>>>> list network 'gw01'
>>>>>>> list network 'gw10'
>>>>>>> list network 'gw11'
>>>>>>> list network 'se00'
>>>>>>> list network 'sw00'
>>>>>>> list network 'sw10'
>>>>>>> option fallback_relay 'rd dhcpv6 ndp'
>>>>>>> option master 'ge00'
>>>>>>>
>>>>>>> root@cerowrt:/etc/config# uname -a
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Cerowrt-devel mailing list
>>>>>>> Cerowrt-devel@lists.bufferbloat.net
>>>>>>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>>>>>>>
>>>>
>>
>>
>
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
next prev parent reply other threads:[~2014-01-06 3:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 5:18 cb.list6
2014-01-03 16:40 ` Dave Taht
2014-01-03 16:50 ` cb.list6
2014-01-03 17:31 ` Dave Taht
2014-01-03 18:15 ` Steven Barth
2014-01-03 18:43 ` Dave Taht
2014-01-04 9:30 ` Steven Barth
2014-01-06 0:42 ` Matt Mathis
2014-01-06 0:48 ` cb.list6
2014-01-06 3:15 ` Dave Taht
2014-01-06 3:48 ` Dave Taht [this message]
2014-01-17 6:52 ` Matt Mathis
2014-01-17 12:58 ` Dave Taht
2014-01-18 14:23 ` Steven Barth
2014-01-18 14:38 ` Dave Taht
2014-01-18 14:46 ` Steven Barth
2014-01-18 16:22 ` Dave Taht
2014-01-18 16:34 ` Steven Barth
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=CAA93jw7kjVK5Sqfgb_oodwZ5bJHHTmjXUBYpMZyAZs3-qQFRYQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=cyrus@openwrt.org \
--cc=mattmathis@google.com \
/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