IPv6 Problems (Not sure if related to existing thread)
-
So, I've been using CentOS (prior to that, Fedora) for my Linux based router forever. I was beating my head against the wall trying to get IPv6 working (for the xbox one, not to require UPnP, which CentOS didn't easily support). From what I could tell, the kernel in centos 6.5 was too outdated to run it properly (found a number of posts indicating a number of fixes with a later kernel). I know IPv6 works because I can plug my Windows based laptop into the cable modem (Time Warner) and can run ping -6 www.google.com no problems.
So, I look around, find pfSense, sounds great. I create a LiveCD, and boot it in the machine. Bam, it has both an IPv4 and IPv6 address. Additionally, connected machines get an IPv6 address, and can ping -6 www.google.com.
I then choose the option to install pfSense to the HDD (having previously backed up important information off the CentOS installation). Everything comes up, but I notice no IPv6 address.
Play with the various options, read the thread that seemed somewhat similar to my issue (http://forum.pfsense.org/index.php/topic,65912.0.html). Did some additional configurations, still no dice. Tried rebooting the machine after changes, and never could get it to come up with an IPv6 address on boot.
Now, I can reboot and load from the LiveCD and get IPv6 each and every time. I believe I also decided that if I released and renewed the LAN interface, it lost the IPv6 address, but I'd have to try again to say for sure.
Anything anybody can suggest for me to look at?
By the way, I like the interface in general, looks to have everything I need out of the machine, without having to manually configure. (Hate dealing with SELinux to get OpenVPN running properly), and maintaining my iptables rules manually.
I'm running:
-
2.1-RELEASE (amd64)
-
built on Wed Sep 11 18:17:48 EDT 2013
-
FreeBSD 8.3-RELEASE-p11
-
You are on the latest version.
Mark
-
-
2 ways to get an IPv6 address automatically: DHCPv6 and stateless (SLAAC). Which one is your provider expecting you to use? Is it configured on the WAN interface?
Do they also route a /48 to you to assign to your internal LAN segment(s)?
-
-
Request a IPv6 prefix/information through the IPv4 connectivity link
- Tried this both on and off
-
Only request a IPv6 prefix, do not request a IPv6 address
- Tried this both on and off
-
The value in this field is the delegated prefix length provided by the DHCPv6 server. Normally specified by the ISP.
- Have tried 64 and 56
-
Send an IPv6 prefix hint to indicate the desired prefix size for delegation
- Again, tried on and off
The router never grabs an IPv6 address under any configuration, and connected PCs also cannot (I test both the router and the PC, as one mode causes the router not to request an IPv6 address.
Is there some logging I can gather from the LiveCD that I could compare to my actual installation?
2 ways to get an IPv6 address automatically: DHCPv6 and stateless (SLAAC). Which one is your provider expecting you to use? Is it configured on the WAN interface?
Do they also route a /48 to you to assign to your internal LAN segment(s)?
-
-
What does your provider say you should do?
-
As of this moment, I have called in twice, and have been unable to get any useful information. I have not been able to get tot he right tier of support I suppose. It is hard to get them to acknowledge IPv6 period.
When the LiveCD comes up, it says it retrieved the address over DHCPv6. I don't understand why it would be any different immediately after saving to the HDD. To me, it doesn't sound like a Time Warner problem. It worked 100% when launched from the CD, and all of the connected computers got routable IPv6 addresses straight up.
As a long ago tech support guy, I would have told me that it's my configuration, if I can get an address in 2/3 configurations (windows, pfSense LiveCD, but not pfSense installed).
-
Weird.
I take it you've examined every config option and made sure they're identical.
Take a config backup on a working LiveCD and restore it on Installed maybe? Compare the relevant sections in the XML files of working and non-working configs to be sure they're identical?
