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

Yeah, I think that's where I screwed up. The dates on the repo changes seemed pretty close to me, so I did a gitsync on the "mainline" repo, and just updated the url for the smos repo. Somehow it made me lose my IPv6 settings.

I went though the how-to again, using your settings, and all my IPv6 settings are back. So thank you!

should be http://files.pfsense.org/jimp/ipv6/

My plan is to stay on the on this verion until the release of 2.0 is finalized.  I happy with where I am and it is running well.

My next issue is DHCP6 is not handing out address.  What I did was I found a web site that I could do translation from 4 to 6.  I converted my internal range(4) to a ip 6 range.  Now I can ping the firewall with IP 6.  I still learning.  This is the hardest thing I have worked on a while.

2.0 has a huge learning curve, I been reading the pfsense book and putting it use.
RC

Decided to install PFsense with ipv6 support and try and do things properly

Thanks for your responses, I will try to follow instructions in the link provided by tebeve  :)

Edit:  I gitsynced using https://github.com/smos/pfsense-ipv6.git and it worked beautifully.

Thanks Wagonza, very nice and useful!

after rebooting my pfsense its working fine sorry 4 the trouble

Not a problem - glad its working for you.  I learned a bit more about teredo myself, since have not played with it quite some time.  What I learned is Im glad Im running a tunnel ;) hehehe

Have fun!

It will be merged immediately after 2_0 is branched, for 2.1 release.

So it turned out that it wasnt pfsense or the switches that were causing the problem one of the computer on the netword had a rouge DHCP server running which was trying to assign the LAN of pfsense an IP which screwed everything up. So it took alot of trial and error to find which computer. I found the computer but I have not had chance to look into the DHCP server that it is running.

Thanx everyone for their help

It would be a mess for sure. You have to do the sync before the reboot or it would really freak out with a v6 config loaded on a normal system.

Now that I think on it more, I'm not sure if the gitsync-on-update code accounts for having to install the files on the second NanoBSD slice either, so that wouldn't work at all either way.

You might be better off waiting for databeestje to make new nanobsd snapshots, and then just gitsync from one of those manually after installing/upgrading using them.