Hey wagonza, thanks for the reply!

I'm won't have the time today to futz around with it, but will tomorrow… and iirc, I used to have all that info plugged in to the DHCP server config page but then pulled it out for some reason or another. I'll replace it all tomorrow and post back, but that makes total sense, thanks again man!

added validation to only pick up on ipv6 nameservers.

@kionez:

Where I'm wrong? I've installed from a wrong source?

I've just missed a step!

Updated to "2.1-DEVELOPMENT (i386) built on Mon Sep 5 04:07:51 EDT 2011" via Auto Update, then gitsync and now /sbin/route seems working fine.

If i remove the default route for inet6, then "change" it ,route gives "No such process" error, but then the new default is set!

thanks

k.

Ok, I've edited the original fbegin.inc with the necessary layout changes to make it work with the widescreen package. I've uploaded a copy here and I found a thread discussing a similar issue in the packages forum where I've also uploaded it.

Edit: Sorry, the version of fbegin.inc I had didn't have the DHCPv6 Relay link in the Services menu. I've reuploaded the new version.

fbegin.inc.txt

Thanks!!!  ;D I'm back up and running.

Hmm. Tried again today to go from my working snap 08/05 to the latest…
IPv6 connection wasn't working and also WLAN was broken...the SSID showed up but my iPhone didn't get an ip address assigned...

Well back to my good ole snap then ;-)

that one should be fixed right about now, was introduced when I added link local gateways support (which is completely valid).

The gogo client is not supported yet. It's on the todo list for dynamic tunnels.
Jim added a HE.net dyndns type that will fixup the tunnel IP for you if you change WAN address. The Sixxs tunnel obviously can't do that.

The gogo client is a nice way to completely autoconfigure the entire machine, but that doesn't fit well with the rest of the pfSense mechanics.

Thanks to CMB, i found my problem.

I had an old dhcp config for this interface. I had to delete it manualy from the XML config, then restore it.
Now working flawlessly :)

Well, normall filterdns does that, but some other parts of the system might use host instead.

Filterdns definitely used for the aliases and firewall rules though.
But resolving from the firewall is not the issues that others are seeing, with dig or otherwise.

Okay, thanks.  I gave it a try using managed, just so dns would work right.  So far, so good - I pass the test-ipv6 site :)  Great work on this!

If you save the alias and then edit it should work. Known issue that needs a javascript person to look at.

It's already fixed in git, a sync should just pick it up.

Haha jeeepii it's working

You can't have a route for ipv4 and ipv6.

So only one for IPv6

tnx for the help

IPv4 is fine. Just tested.

I have no access to those either. So that's a bit hard.

6rd is a rather specific type of rollout which I don't think will be widely supported in the feature. Free.fr does have a huge deployment but needs to renumber before they actually give clients native Ipv6.

I sent a message to the support list detailing that you can now configure DHCP6 on your WAN interface of choice, either dynamic, static or pppoe.
It should basically work. I tested on a lab setup with a Cisco 1811 PPPoE server with DHCP6 Server, similar to what Comcast uses for their native deployments.

Lion has a dhcp6 client, that wasn't there before, thus more addresses assigned.

Sweet this is Fantastic!!  Thanks!!  Looks really nice housed on official pfsense doc location as well..

@johnpoz:

How would you go about tracking down what specific change did this?  I would much rather be able to help and say, hey did commit xyz here is link break this?  I see it changed X to Y, etc.

'git blame' does just that, you have to checkout the repo from github. I wasn't sure exactly where that was, so from my git root for mainline I did:

grep -r route * |grep inet6

which found system.inc, then

git blame etc/inc/system.inc

shows all the lines and which commit last changed them (first column is the commit ID). 'git show xxxx' where xxxx is the commit ID will show the entire commit. Lots more info on git usage on github's help pages if you want to get in further depth. http://help.github.com/

Yep, indeed Hetzner. :)

I had tried that solution with a static route for the LAN segment via the Hetzner gateway before, but it failed because I added a route for the full LAN segment which was ignored / overridden by the LAN interface route. Stupid me. :)

After getting a hint in the Hetzner forum, I now added TWO static routes, one for the first and one for the second half of my LAN segment, and that worked nicely. Those routes were added correctly to the routing table, and since they are more specific (longer network mask) than the actual LAN route, they take precedence.

Ok this went BAD!!  I removed that line, no ipv6

I then put it back and rebooted, still no go.  Figured out my default gateway was missing?

Tried undo default he_net gateway and then reapply, still not working getting this error.

php: /system_gateways.php: The command '/sbin/route -inet6 default '2001:470:1f10:b85::1'' returned exit code '64', the output was 'route: illegal option – i usage: route [-dnqtv] command [[modifiers] args]'

Something changed on how default routes are added?  I had to manually add the route with this command

route -n add -inet6 default 2001:470:1f10:b85::1

Yeah somebody changed something, I have not rebooted in a while – but now just rebooted and getting this.

Jul 27 07:48:40 php: : The command '/sbin/route -inet6 default '2001:470:1f10:b85::1'' returned exit code '64', the output was 'route: illegal option -- i usage: route [-dnqtv] command [[modifiers] args]'
Jul 27 07:48:40 php: : ROUTING: setting IPv6 default route to 2001:470:1f10:b85::1

And I put that 1 line back, and what would that have to do with wrong command?  And even changed my mask to /64 vs the /128