Hi Guys, This is probably a Centos issue - but I'm new to IPV6 and just trying to get up to where ping6 works. Running Centos 6.6 and did the stuff various web sites suggested. Yet pinging Google is not reachable. In /etc/sysconfig/network I added: # IPV6 IPV6_DEFAULTGW=2001:470:1:2fe::1 NETWORKING_IPV6=yes IPV6_AUTOCONF=no In ifcfg-eth0 I added: IPV6INIT=YES IPV6ADDR=2001:470:1:2fe::18/64 IPV6_AUTOCONF=NO IPV6FORWARDING=YES IPV6_DEFAULTGW=2001:470:1:2fe::1 In /etc/sysctl.conf I added: # IPV6 net.ipv6.conf.all.autoconf = 0 net.ipv6.conf.default.autoconf = 0 net.ipv6.conf.eth0.autoconf = 0 net.ipv6.conf.all.accept_ra = 0 net.ipv6.conf.default.accept_ra = 0 net.ipv6.conf.eth0.accept_ra = 0 net.ipv6.conf.default.forwarding = 1 net.ipv6.conf.all.forwarding = 1 net.ipv6.conf.all.proxy_ndp = 1 net.ipv6.bindv6only = 1 Restarted the network - tried to ping google ping6 ipv6.google.com connect: Network is unreachable ran ifconfig eth0 Link encap:Ethernet HWaddr E0:CB:4E:CF:4B:BE inet addr:184.105.182.18 Bcast:184.105.182.255 Mask:255.255.255.0 inet6 addr: fe80::e2cb:4eff:fecf:4bbe/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:21283662 errors:0 dropped:0 overruns:0 frame:0 TX packets:19638030 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2792719190 (2.6 GiB) TX bytes:2867321807 (2.6 GiB) No Scope:Global IP what am I missing? Thanks in advance ...
Hello, The most likely culprit is that CentOS 6.6 is a bit too new. You should not use a version of CentOS newer than 6.4 - the reason is that openVZ uses an old kernel (2.6) so using any linux distro with a newer kernel opents the doors for major problems because their yum/apt-get/package repositories assume a newer kernel. I currently would never recommend installing openVZ on any linux distro that is newer than CentOS 6.4 Regards, Matt
mmcfarland wrote on Tue, 04 November 2014 19:45 ... CentOS 6.6 is a bit too new ... openVZ uses an old kernel (2.6) so using any linux distro with a newer kernel ... I'd really appreciate people giving advice only if they have a slightest clue as to what they are talking about. Not that I'm afraid mperkel would actually listen to such nonsense, but some newbie could get mislead.
This isn't misinformation! Software made for a newer kernel is not going to work as well on openvz. Sure maybe if you're a Unix genius you can get by with your hacks and workarounds. BUT straight out of the box?? Use centos 6.4 nothing newer and openvz runs like a champ. If you have a newer kernel you must be careful.
Going back to Centos 6.4 isn't in the plan.
Of course not. He's just spreading FUD. Current OpenVZ kernel is based on a recent RHEL 6.5 kernel, 2.6.32-431.29.2.el6, it isn't old at all.
'isnt old at all' yea its old. maybe its not as old as the dinosaurs, but it is certainly older than over a dozen or so linux releases. So 'isn't old at all' is not an accurate statement. Look, my point is simple - openvz assumes kernel 2.6 - software that runs as a service, application, server, etc on a linux system that uses a later release of the linux kernel assumes that kernel! Maybe the 2.x family is safe, ok, so maybe 6.6 centos should work (I wouldnt bet my money on it!) CentOS 6.6 runs on 2.6.32-504, openVZ is assumes a slightly older release, so maybe the IPV6 could work. Personally, I'd try to get it working on a server with no other changes. Just start up a basic server with NOTHING installed, CentOS 6.6 then add ipv6 and openvz, see what happens. if it works - then obviously its not openvz that's the problem. At any rate, I would refrain from saying 'isnt old at all' - I tell you it is, and if you look at the latest linux version and how much different it is under the hood and how its architecture / api has changed so much then I'd say its a LITTLE old.
Wow, such rant... On the topic of an "old" kernel, you might consider: www.lmgtfy.com/?q=RHEL+old+kernel&l=1 We've run a sizable OpenVZ hosting facility for over half a decade, and have yet to encounter a single customer citing issues with the OpenVZ-patched and RHEL-based stable kernel revs. Although we're always interested in hearing of specific issues that could be encountered in a production hosting environment. Please, could you consider cutting the FUD, and citing specific issues you're encountering, which can be directly attributed to said "outdated" kernels. Please?
IPv6 is working splendidly on our CentOS 6.6 / 2.6.32-042stab094.7 OpenVZ host server builds, so I can't imagine it being that... You said you configured an IPv6 address and restarted networking: Quote: In ifcfg-eth0 I added: IPV6INIT=YES IPV6ADDR=2001:470:1:2fe::18/64 IPV6_AUTOCONF=NO IPV6FORWARDING=YES IPV6_DEFAULTGW=2001:470:1:2fe::1 Although, I don't see it listed: Quote: ran ifconfig eth0 Link encap:Ethernet HWaddr E0:CB:4E:CF:4B:BE inet addr:184.105.182.18 Bcast:184.105.182.255 Mask:255.255.255.0 inet6 addr: fe80::e2cb:4eff:fecf:4bbe/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:21283662 errors:0 dropped:0 overruns:0 frame:0 TX packets:19638030 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2792719190 (2.6 GiB) TX bytes:2867321807 (2.6 GiB) What output do you see after running this command: sudo sysctl net.ipv6.conf.all.disable_ipv6 net.ipv6.conf.default.disable_ipv6