Unsupported device type 240 for "gif0"
Ain't that the tunnel interface? You are not supposed to configure any sort of dynamic addressing on the tunnel interface. You should only use dynamic addresses on the physical Ethernet interface.
Additionally, I would stick with just router advertisements and not use DHCPv6, unless there is a very specific need for features provided by DHCPv6.
Now let me explain IPv6 is very new to me, I am not a professional. I simply play around with networking stuff like pfSense & IPv6 for fun. yes gif0 is my tunnel interface. Not sure what you mean by "not suppose to configure any sort of dynamic addressing on the tunnel interface."
When you configure the tunnel interface, it only asks you for 3 items. Server IPv4 address, Server IPv6 address, & Client IPv6 address. Then you set the parent interface which is set to WAN. There is no way to set anything to dynamic under the gif interface. Please refer to this guide to see what the gif/tunnel interface setup page looks like. It's the picture with the arrows from one image to another.
http://xtropx.blogspot.cz/2012/07/pfsense.htmlSee if you can follow through that guide & find any problems? I've used this guide & multiple others which are all very similar in explaining how to setup IPv6. My WLAN interface is set to a static IPv6. For that static IPv6 the guide tells you to use your /64 routed. I'm actually trying to use my /48, because after I figure out my one subnet, I do need to setup IPv6 for 2 others. I did previously have IPv6 working on pfSense 2.1 dev & even wrote a guide, it was working with my /48. I updated a few months ago & it broke everything & i've been trying to fix it.
All the guides say to enable DHCPv6 & set a valid IP range. DHCPv6 did work previously under 2.1 dev when I had IPv6 running successfully. This is where i'm confused. If I was to shut off DHCPv6 how would clients get IPs? DHCP servers assign/hand out/serve IPs, correct? I'm thinking that router advertisements & link local addressing can somehow serve IPs to clients, is what your trying to tell me? But then wouldn't addressing be random?
I've tried playing with damn near every combination of settings to try & get it to work. I will try turning off DHCPv6 & playing around with that until I hear back. Thanks for the help so far.
ETA:Here is what I see from the packet capture function. I also tried this from another network JUST INCASE my wireless router may have caused problems, but nothing has changed on that wireless router since it previously worked. I also have a DMZ setup with a wired connection. Started packet capture & ran "ipconfig /renew6" on that pc (Win 08 Server). ipconfig /renew6 fails. Packet cap data looks same even with DHCPv6 running. This cap was done with DHCPv6 disabled.
Of note, the ":d0a8" address is the link local ipv6 on the server trying to request an ipv6. Looks like no reply back mabye? It's talking to the router advertisement link local it appears & port 547. Possible problem with that port? Because that error message seems to hint at that as well. I did check. No programs or port forwarding is setup for that port, so nothing should be using it.
09:59:02.395087 IP6 fe80::b5e8:eb2c:47d1:d0a8 > ff02::2: ICMP6, router solicitation, length 16
09:59:02.395296 IP6 fe80::20e:4ff:feb7:6c77 > ff02::1: ICMP6, router advertisement, length 120
09:59:02.414326 IP6 fe80::b5e8:eb2c:47d1:d0a8.546 > ff02::1:2.547: UDP, length 86
09:59:03.413791 IP6 fe80::b5e8:eb2c:47d1:d0a8.546 > ff02::1:2.547: UDP, length 86
09:59:05.413737 IP6 fe80::b5e8:eb2c:47d1:d0a8.546 > ff02::1:2.547: UDP, length 86
09:59:09.030341 IP6 fe80::20e:4ff:feb7:6c77 > ff02::1: ICMP6, router advertisement, length 120
09:59:09.413743 IP6 fe80::b5e8:eb2c:47d1:d0a8.546 > ff02::1:2.547: UDP, length 86
09:59:14.740678 IP6 fe80::20e:4ff:feb7:6c77 > ff02::1: ICMP6, router advertisement, length 120
09:59:17.419506 IP6 fe80::b5e8:eb2c:47d1:d0a8.546 > ff02::1:2.547: UDP, length 86
09:59:23.399642 IP6 fe80::20e:4ff:feb7:6c77 > ff02::1: ICMP6, router advertisement, length 120
09:59:33.423158 IP6 fe80::b5e8:eb2c:47d1:d0a8.546 > ff02::1:2.547: UDP, length 86
09:59:35.516024 IP6 fe80::20e:4ff:feb7:6c77 > ff02::1: ICMP6, router advertisement, length 120
09:59:45.561251 IP6 fe80::20e:4ff:feb7:6c77 > ff02::1: ICMP6, router advertisement, length 120
10:00:05.152375 IP6 fe80::20e:4ff:feb7:6c77 > ff02::1: ICMP6, router advertisement, length 120
10:00:05.422338 IP6 fe80::b5e8:eb2c:47d1:d0a8.546 > ff02::1:2.547: UDP, length 86
10:00:20.486835 IP6 fe80::20e:4ff:feb7:6c77 > ff02::1: ICMP6, router advertisement, length 120
10:00:36.010342 IP6 fe80::20e:4ff:feb7:6c77 > ff02::1: ICMP6, router advertisement, length 120
10:00:48.593356 IP6 fe80::20e:4ff:feb7:6c77 > ff02::1: ICMP6, router advertisement, length 120
10:01:00.057210 IP6 fe80::20e:4ff:feb7:6c77 > ff02::1: ICMP6, router advertisement, length 120
ETA2:Well crap. Double checked a packet cap of my WLAN network. It is doing router advertisements but no responses from my clients link local like I can see on the server packet cap. The server does have a IPv6 default gateway of fe80, which is link local. The WLAN client does not have the link local IPv6 default gateway. Any idea why WLAN client isn't able to get as far. All settings are identical that I can tell other than the physical setup. Server is connected to switch then to pfsense nic. Wireless router is connected to powerline networking adapter. powerline networking input is connected to pfsense nic.
Going to chock this part up to equipment. I THINK that both the wireless router & powerline networking were hooked up when I had IPv6 working. But it's possible mabye the powerline networking wasn't. I plugged laptop directly into a switch & could get the link local gateway. So it must have something to do with the router or powerline networking. I will try to use just the router & not the powerline networking adapter & see if that fixes the WLAN but issue still stands with the server machine not being able to pull IPv6 for some reason.
Yup, just pulled up past purchases off of newegg. Started reading reviews & these are a TPlink TL-PA210KIT. These are known not to support IPv6 correctly. TPlink says to upgrade to TP-LINK TL-PA2010KIT. Notice the extra zero. 2010 instead of 210.
So that fixes one issue. Now still need to know why my wired server isn't getting IPv6.
I did read one person state, not about my particular switches, but his switch wouldn't pass any IPv6 traffic. Now I do know for 100% fact the same switches now used were used when IPv6 worked previously. However pfSense could have changed something & some reason my switches aren't doing IPv6 like they should. I don't have a crossover cable to use to test nic to nic from pfsense router to sever right now. Everything looks correct, that's the only thing I could think of, because I haven't tested that. Or would talking of link local address from pfSense to server be proof that IPv6 is working fine on the switches?