http://comcast6.net/ tells me that the local cmts is v6 enabled. my
modem, a cisco dpc3008, is in the supported products list. so how do
i turn the sucker on?
randy
do you see PD from your modem? or RA's? (guessing probably not, or
you'd not be asking)... for my arris, it was just automatically
working. My dlink, another story 
do you see PD from your modem? or RA's?
still trying to educate the opwnwrt (attitude adjustment on netgear
3800).
root@wrt-biwa:~# opkg update
Downloading http://downloads.openwrt.org/attitude_adjustment/12.09/ar71xx/generic/packages//Packages.gz.
Inflating http://downloads.openwrt.org/attitude_adjustment/12.09/ar71xx/generic/packages//Packages.gz.
Updated list of available packages in /var/opkg-lists/attitude_adjustment.
root@wrt-biwa:~# opkg install luci-proto-ipv6
Unknown package 'luci-proto-ipv6'.
Collected errors:
* opkg_install_cmd: Cannot install package luci-proto-ipv6.
root@wrt-biwa:~# opkg install ipv6-support
Unknown package 'ipv6-support'.
Collected errors:
* opkg_install_cmd: Cannot install package ipv6-support.
sigh
randy
yea, so my 'saga' started with:
1) "dlink 615 doesn't like dhcp-pd ... and is flat broken for v6"
a) gets v6 addr on WAN from arris-RA
b) gets PD alloction from arris, does RA's to LAN
c) sets default-gw for v6 on the LAN side to something unreachable
d) manually resetting default-gw ... gets me zippy... can't ping
either side of the dlink, nor the arris
e) dlink's v6 code (for that platform) is just boarked, badly.
2) oh! dd-wrt does this platform too, and v6
a) install dd-wrrt
b) fiddle-fart around with v6 configs
c) oh.. dhcp-pd is one of the things dd-wrt didn't implement
d) oh, their 'v6 support' is really only 'v6 tunnel support'
e) boned.
basically ... this is much harder to do than it shoudl be and yes,
I can probably do something like plug in my raspberry-pi and make that
a 'router' but come on... in 2013 I have to home-brew something to get
a protocol developed and engineered in 2000 to work?
(this raised itself above my level of 'fixed in a weekend' project, so
my comcast v6 lays fallow... NOTE: this is NOT comcast's fault, in my
eyes.)
-chris
(this raised itself above my level of 'fixed in a weekend' project, so
my comcast v6 lays fallow... NOTE: this is NOT comcast's fault, in my
eyes.)
i could take a picture, but i think you would recognize the boat. sigh.
randy
>> do you see PD from your modem? or RA's?
>
> still trying to educate the opwnwrt (attitude adjustment on netgear
> 3800).
...
yea, so my 'saga' started with:
1) "dlink 615 doesn't like dhcp-pd ... and is flat broken for v6"
...
2) oh! dd-wrt does this platform too, and v6
...
basically ... this is much harder to do than it shoudl be
and yes,
I can probably do something like plug in my raspberry-pi and make that
a 'router' but come on... in 2013 I have to home-brew something to get
a protocol developed and engineered in 2000 to work?(this raised itself above my level of 'fixed in a weekend' project, so
my comcast v6 lays fallow... NOTE: this is NOT comcast's fault, in my
eyes.)
Another option to try out is CeroWRT. Its based on OpenWRT
development releases and focuses on good IPv6 support in addition to
its raison d'�tre, debloating buffers.
http://www.bufferbloat.net/projects/cerowrt/wiki/Wiki
Still waiting for my CMTS to be upgraded...
I feel your pain. I am on the Comcast Business trial and have tried pfsense and now trying monowall. I followed all the different instructions I could find for pfsense 2.1 and while I could pull the WAN IP, I never could get a LAN ip nor could I get an ip on any of my computers.
I am now in the process of trying m0n0wall and have gotten IP's on the WAN, LAN, and on my workstation. Can ping from my workstation to my m0n0wall LAN and WAN IP's but nothing will route out to the net.
It should really be easier than this.
Robert
I have no issues with the comcast business netgear box and normal ra+dhcpv6. Not trying anything fancy as when I do, I spend too much time doing tech support for my family. Flat lan makes it work.
Jared Mauch
According to Comcast’s DOCSIS Devices page, http://mydeviceinfo.comcast.net/?s=i&so=1&e=0&d3=1&tier=-1&sc=84, the Cisco DPC3008 is not supported for IPv6. You could always try enabling IPv6 on a system directly connected to the Cisco and see what happens. I’m not optimistic.
I opted for my minimal-effort solution. I installed a Motorola SB6121 and a 5th gen Airport Extreme and turned them on. Of course I configured the Airport Extreme with a name, management password, and confirmed IPv6 was set to to configure Automatically and Native. When the Comcast drop was plugged in and Comcast authorized the modem, I had a multistacked LAN.
Going on 11 months of IPv4/IPv6 service. I’ve had about 1 hour of downtime.
James R. Cutler
james.cutler@consultant.com
I had very borken things happen at home on my dlink-615 with their busted-ass IPv6 code. Specifics are here: http://serverfault.com/q/252083/2101
Although in that case, I wasn't trying to use it to route anywhere. It really was written as thought it Would Be the gateway.
The dlink stock firmwares even have support for he.net and other tunnel brokers now. But the stack isn't nearly as mature and there's too few users.
pfSense is the way to go here.
I'll try re-deploying the dir-615 it as an IPv6-only gateway device and see how it behaves.
M.
Oh, I agree. If I plug the Netgear box directly into my network, everything works great. I
really believe it is a pFsene/m0n0wall issue.
Robert
I should be fair to the problem (and my lack of patience with it) and:
1) document with some pictures and packet-captures and interface configs
2) take a better stab at making the stock deployment work
3) write all this up somewhere searchable by askjeeves.
if work doesn't eat my evening I'll make an attempt at that tonight/tomorrow.
-chris
Thanks for reminding me that I need to get back on Verizon's case about getting IPv6 on Fios... 
jms
That page also says the Zoom 5341 cable modem doesn't do IPv6, although
the device in my living room says it does indeed do so but its upstream
refuses to provision it.
good luck! and I think their plans currently are to provide you CGN
first (happy if i"m wrong about that)
Since my Fios router has a way to configure IPv6 on it, I turned it on to
see but I couldn't get it to work. I called their technical to ask for
help/information about IPv6 support and was told "We don't even support
IPv5 yet, so it will be a while before we support v6."
John Lightfoot
Naturally, as the odd-numbered releases of IP are experimental. They should be focusing on the even-numbered releases for production use.
M.
is this a StarTrek reference? 
Oops, I slipped up or down a line scanning across the page.
I am now more optimistic.
Cutler
My testing on OS X Mavericks shows that an Airport5,117 with firmware 7.6.4 creates the guest wireless network:
1. With an IPv4 address from an automatically assigned RFC1918 LAN connected through NAT to WAN.
2. With NO IPv6 addressing of any kind.
My conclusion is that Apple does not yet support IPv6 in any fashion for Wireless Guest networks.
James R. Cutler
james.cutler@consultant.com