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.

Hello,

Just FYI: I now not a /64 for routing purposes and can use the whole /48 as expected.
Everything works fine now.

Thanks again and Greetings,
Jens

i`m doing something like this but only with OpenVPN, not GIF on my pfsense.

The difference is that i run OpenBGP package on pfSense and Quagga on the others Linux box.

In Advanced config i have..

mode p2p;
tun-ipv6;
ifconfig-ipv6 2001:ffff::1 2001:ffff::2;

fixed endpoint sixxs tunnels work just the same as with HE. There is no issue configuring those.

I've looked at aiccu but combined with the awkward registration and kredit system I've decided not to invest time in it. If others are willing to code it, that's fine, submit patches or pull requests on github.com.

roger that, thanks for the update!

I have found the problem! I accidentally added the fe80::/16 range to the EasyRuleBlockHostsLAN alias to avoid my pfSense logs being swamped with local traffic. This caused these packets to be blocked thus the errors to be generated. I have removed the fe80::/16 range from the alias and the problem went away. DHCPv6 and static mappings are working smoothly now :D

Hi guys,

Hmmmm….does the auto-updater check 32 vs. 64 bit when it runs?

I've changed over from 32 to 64 and I bet I still have the i386 update url set in my config!

Now that I think about it that would explain a lot..I would have sworn I was running 64 bit which is why I updated last night.

-Will

If you read the sticky when entering the board there is a nice tutorial linked from there on how to get your tunnel working.

Google might find it too, yep, it does

OpenVPN with IPv6 is now supported.

Configure the IPv6 networks on the OpenVPN Server settings page. Create IPv6 firewall rules on the Firewall Rules OpenVPN server interface tab.

Install the openvpn installer with IPv6 support.
http://www.greenie.net/ipv6/openvpn.html
http://www.greenie.net/ipv6/openvpn-2.2.0-ipv6-savepasswd-20110522-install.exe

That should be enough. Client support is limited to windows with the modified installer and any other that has the IPv6 payload patches integrated.

I've contacted the Viscosity folks but it's not in the pipeline yet. They are aware of the patches though.