Almond+ IPv6?

[dalrain]

Hello,
I'm really excited about my Almond+, it's SO much faster than anything I had before.  It works well, and the interface is coming along nicely through the dev process.

That said, I'm a Comcast customer at current, and in their IPv6 service area.  I wanted to try out native IPv6, but I'm having trouble seeing how I should set it up.  Are there any instructions on that somewhere, or is IPv6 not yet implemented, or some other news someone could give me?

Thanks!

EDIT: You can find a set of instructions for IPv6 on Comcast in this post: http://forum.securifi.com/index.php?topic=1238.msg3776#msg3776

I take no responsibility for the config, or safety of the firewall rules.  Use at your own risk!

[LGNilsson]

IPv6 support is implemented, but I'm going to have to have the software team help put together some instructions as I don't have access to an IPv6 network, so I haven't had the opportunity to try and set things up.
 

[dalrain]

Awesome!  So glad to hear it!  I look forward to seeing the docs.

[summat]

Pretty sure Comcast use DHCP to give a /128 for the WAN interface, and a /64 delegation for the LAN interface.

I've not got my Almond+ yet though so can't tell you how to enter those settings.

[dalrain]

I'm presuming that whatever configuration is required is probably done in OpenWRT, it doesn't look like the native interface has everything just yet.  So I may try to figure it out based on that, though a cursory glance tells me it may be non-obvious for the novice. Hmm..

[dalrain]

Any updates on this?  Still looking for Almond+ specific instructions, I haven't had much luck on the OpenWRT side of the house.

[LGNilsson]

Sorry, still waiting for someone from the software team to provide instructions.

[dalrain]

Edit: I didn't know what I was talking about in this post.

[dalrain]

Edit: I was still discovering syntax in this post.  Deleted for brevity/errors.

[dalrain]

And now to respond to myself yet again, I see that the /etc/config/dhcp6c file is a UCI config, which is supposed to be used to generate the "real" config, but it looks like the config it generates doesn't correspond to what I have in the UCI config.

[dalrain]

Nevermind, no bug here.  Found these are IDs, not booleans when the config is written.

[dalrain]

More information, Almond+ by default has ip6tables which doesn't allow dhcp6c, I found this out by disabling it entirely, but then backed it on.

Found this thread which gave me a custom rule to allow it: https://bugzilla.redhat.com/show_bug.cgi?id=591630#c1

Code: [Select]

# This file is interpreted as shell script.
# Put your custom iptables rules here, they will
# be executed with each firewall (re-)start.

/usr/sbin/ip6tables -A INPUT -m state --state NEW -m udp -p udp --dport 546 --sport 547 -s fe80::/10 -d fe80::/10 -j ACCEPT

Now I can DHCP an address on the WAN side.  Hurray!

[summat]

Nice to see you're making some progress.

So is your WAN now getting and address via DHCP6 from your ISP? Just the delegation needing to be solved?

[dalrain]

It is, and the delegation works now, too, actually.  I will post configs for Comcast when I get back tonight, but I think ip6tables is broken due to conntrack not functioning as intended.  (Of course, you can turn the firewalls off, but that's a..less great idea.)

[dalrain]

Does anyone know the kernel version the almond+ is running offhand?  I don't have mine in front of me, but I wanted to see if I could verify a theory that connection tracking might be broken in the kernel with ipv6.  Apparently it didn't work until version 2.6.20+ when they switched to xtables.