ClearFoundation

I've had a number of customers experiencing IPv6 problems on sites like www.bing.com and docs.google.com, for example. The sites simply hang, they're resolving to IPv6 addresses, which I discovered by . (And yes, /etc/sysconfig/network did include the line: NETWORKING_IPV6=no.)

So far, I've gotten around the problem by disabling IPv6 as directed on the Centos Wiki. But this is surely a temporary solution, at the very best. What would be ideal is if ClearOS could support IPv6 websites and IPv4 LANs. Is this already possible but I'm missing something?

What are other people experiencing and how are you handling the problem? I've encountered it on Comcast & Centurylink DSL networks.

Am I really the only one experiencing these IPv6 problems? No one else has issues with Google Docs, etc simply not loading?



Contents of /etc/resolv.conf:



Other than disabling IPv6 altogether, how can this be resolved? COS devs, what's your game plan for the inevitable IPv6 transition now in progress?

Or, is there a configuration setting that I'm missing that allows IPv6 sites to resolve while maintaining IPv4 on the LAN?

Dave,

I've just started experimenting with IPv6 on ClearOS 6.x as my ISP issued me /56 and /64 blocks for internal/external IPv6 assignment. I've made some progress so far, but I need to put more time in to get everything working 100%.

From your post above, I see that isn't a DNS resolving issue. You can see the docs.google.com is resolving... Btw, you can't telnet to docs.google.com (defaults to port 23), but you can telnet to port 80:

# telnet docs.google.com 80

Now at the gateway level you need to also ensure IPv6 forwarding is enabled... This is what I have in my /etc/sysconfig/network file (NOTE: You may not need all of these turned on).

# IPv6 configuration
NETWORKING_IPV6=yes
IPV6FORWARDING="yes"
IPV6_AUTOCONF="yes"
IPV6_AUTOTUNNEL="no"

In your case, I think you only need the forwarding enabled. I'm new to IPv6, but unless you have IPv6 -> IPv4 enabled/configured, I don't think your LAN hosts will be able to connect to public IPv6 servers.

Once I have a fully functional IPv6 set-up I plan to look in to updating various ClearOS apps/libraries to make everything IPv6 compliant, which is not the case at the moment.

I use ClearOS 5.2 in an IPV6 enabled environment and use the following firewall script to set it up with basic in /out block etc. Might be of use

www.clearfoundation.com/component/option...view/id,41113/#41126

Does this bug apply to ClearOS 5.2?

bugzilla.redhat.com/show_bug.cgi?id=243739

Yes I believe so, when putting together the firewall script in the above thread I noticed the stateful rules where marked as not working for ipv6 in el5 kernels. The fudge is to accept high port range traffic....