Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Richard Brown <Rich.Brown@intermapper.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Richard Brown <Rich.Brown@intermapper.com>,
	"<cerowrt-devel@lists.bufferbloat.net>"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] cerowrt 3.7.2-3 released, still in a battle with ipv6
Date: Fri, 18 Jan 2013 15:53:20 +0000	[thread overview]
Message-ID: <54532012A5393D4E8F57704A4D55237E42ADB172@CH1PRD0510MB381.namprd05.prod.outlook.com> (raw)
In-Reply-To: <CAA93jw59V=kCyN0wzORtMpzjCenwPPS+CJghxjW4mZmz-y7fRw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 937 bytes --]

Dave,

There are multiple threads on the stateless dhcp and dhcp implementation going on here:

http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2013q1/thread.html

among other things, "enable-ra" should be getting set in the generated dnsmasq conf file and probably isn't right now. Perhaps it can be manually set?

OK. I'll check that list.

I'm hoping ipv6 support isn't mission critical for anyone? I really wasn't planning on A) breaking it, or B) fixing it - this week. I DO care about exercising the ipv6 portion of the stack a lot though, there are still a few new instruction traps left to kill in the kernel (see bug 419)

(dhcpv6 support also has trouble - can't even assign the delegated prefix)

ipv6 isn't critical for me - I'm just doing my walk around to see if things are still working. (And it sounds as if you're going to keep after IPv6 for a while.)

Thanks again for all this work!

Rich

[-- Attachment #2: Type: text/html, Size: 4505 bytes --]

  reply	other threads:[~2013-01-18 15:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.5563.1358459264.1742.cerowrt-devel@lists.bufferbloat.net>
2013-01-18 13:23 ` Richard Brown
2013-01-18 15:26   ` Dave Taht
2013-01-18 15:53     ` Richard Brown [this message]
2013-01-18 15:54     ` Dave Taht
2013-01-18 18:07       ` Robert Bradley
2013-01-18 18:11         ` Dave Taht
2013-01-18 18:30           ` Robert Bradley
2013-01-19  0:41       ` Richard Brown
2013-01-19  9:45         ` Maciej Soltysiak
2013-01-16 11:37 Dave Taht
2013-01-16 21:12 ` Maciej Soltysiak
2013-01-16 21:48   ` Dave Taht
2013-01-16 21:53     ` Maciej Soltysiak
2013-01-17 21:45       ` Maciej Soltysiak
2013-01-17 21:47         ` Dave Taht

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=54532012A5393D4E8F57704A4D55237E42ADB172@CH1PRD0510MB381.namprd05.prod.outlook.com \
    --to=rich.brown@intermapper.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.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