anyone managed to get pfsense working with unifi ipv6? tried slaac & dhcp6 and it's not working.

if i do an ifconfig in the pfsense box, i get this

pppoe0: flags=88d1<UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST> metric 0 mtu 1492
inet6 fe80::20c:29ff:fee2:41b1%pppoe0 prefixlen 64 scopeid 0x8
inet6 2001:e68:5061:5cd7:20c:29ff:fee2:41b1 prefixlen 64 autoconf
inet 118.101.15.60 --> 118.101.15.254 netmask 0xffffffff
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>


does that mean i'm getting the ipv6 address?



EDIT: After visiting this page, it seems like the problem is with pfsense 2.1 Release.

https://forum.pfsense.org/index.php?topic=68364.0

If i add a route like what one of the fella said, i can ping google via ipv6 using the pfsense box.
Before i add the route, I can't ping it. IPv6 ip is shown but 100% loss.

This post has been edited by godhpf: Jan 23 2014, 08:02 PM

hmm.. I managed to get ipv6 running with pfsense 2.1.1

I think there are still some bugs with pfsense ipv6 because of the weird problems that I've encountered.


What I did was:

1. Use DHCP6 for the WAN interface with "Request a IPv6 prefix/information through the IPv4 connectivity link" checked. DHCPv6 Prefix Delegation size is 64.

2. Track interface at LAN & select the WAN interface to track.


The weird problems that I've faced:

Problem 1.
I did the exact same thing previously but it didn't work.
The default route of ipv6 was not set. I need to set it manually (but it resets everytime).
Also, pfsense was also unable to get an IPV6 address on the LAN interface.
Then what I did was did a clean install and setup the whole thing again. the LAN interface finally get an ipv6 address (2001:xxxx:blablalbaba). But the pcs are unable to get an address. After few reboots, miraculously the pcs did get an address. lol~

Problem 2:
Initially I couldn't do anything with the global ipv6 address. ping to google ipv6 dns fails, test-ipv6.com fails etc.
Then I looked at the firewall logs. Somehow it is blocked. This happens even though there's a rule that allows any traffic originating from the LAN. Then what I did was allow that blocked ping's traffic from my pc ip to the google dns (there's a shortcut). Then not surprisingly the ping goes through. Then I deleted that rule and reloaded the firewall. Amazingly, all ipv6 traffic is still going through. test-ipv6.com is successful. same goes to test-ipv6.com results from another pc.


Explanations?
I don't know why these problems happens. It baffles me. But then again, i'm not a pro with these stuffs. For the first problem, I really have no idea. For the second problem, maybe the added rule somehow woke up the pfsense firewall and made it correctly allow ipv6 traffic.

I've spent countless hours trying to do this using pfsense 2.1 and 2.1.1 (just released recently). Hope this saves some forumers' time in trying to get ipv6 working with pfsense.

And woot! ipv6 tag finally!


hmm, it it just me or some ipv6 sites are obscenely slow?

EDIT 1: upon restarting, the firewall is blocking ipv6 traffic again. lol. need to repeat step mentioned in problem 2 lol.

EDIT 2: hmm after a few restarts, while my LAN interface is still able to get the ipv6 address, the pcs in my network couldn't. bummer. It seems like radvd is the problem. since i'm getting these



If i kill the radvd process and start it again. I can get the global ipv6 address again without the same error. hmm.
facebook stil unaccessible with ipv6 though. No idea on what is wrong. MTU thingy didn't help. hmm

This post has been edited by godhpf: Apr 11 2014, 12:20 AM

btw, ontop of the radvd problem, vmware tools seems to interferes with pfsense LAN interface's ability to get IPv6 address (and subsequently other devices on the network).


anyone know whether tmnet will roll out static ipv6? Dynamic ipv6 sucks IMHO.

facebook and youtube is extremely slow for me to the extent that it is unusable. Some other sites too. I've turned off IPV6 because of this.