New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Need help with ipv6
ErawanArifNugroho
Member
I'm asking for the /64 from a provider, and get this answer :
Assignet subnet is : 2607:F130:0000:001B::/64 Gateway 2607:F130:0000:001B::1/64
So, if I want to apply for example 2 or 4 ipv6 in the vps, what should I do in the interfaces?
I've tried this :
iface eth0 inet6 static address 2607:f130:0:1b::2 netmask 64 gateway 2607:f130:0:1b::1 up /sbin/ifconfig eth0 inet6 add 2607:f130:0000:001b::3/64
It can show the following ipv6 when I give the command ifconfig :
- 2607:f130:0000:001b::2
- 2607:f130:0000:001b::3
I can ping6 ipv6.google.com, but the ipv6 itself can't be pinged from the outside. It's always unreachable.
Comments
What does your ifcfg-eth0 look like?
Assuming he's using CentOS. I think he uses Debian, and he's posted the part of his interfaces file.
Check IP6Tables
csf running, blocking ICMPv6?
also post output of
curl -6 http://ipv6.whatismyipv6.com
last time I had this problem, provider had set up routing wrong...
edit: actually don't post the whole thing, its a mess - but see what ipv6 you get from it. I'm just off to write a clean whatismyipv6 script.
Sorry, forgot to mentions I'm using Debian 6 32bit in a XEN.
The ip6tables is empty, and I don't running any csf/firewall yet becase I'm still testing this vps.
If I'm using the following configuration, the only IPv6 can be pinged from the outside is 2607:f130:0:1b::2 , the others IPv6 can't be pinged :
If I'm doing curl -6 http://ipv6.whatismyipv6.com, the results is 2607:f130:0:1b::2.
So, from the assigned IPv6 range, what is the IPv6 I can use? Am I only allowed to use 1 IPv6?
Your /etc/network/interfaces seems ok however try with:
netmask 48
(restart and report if that solved issue)
Thank you again @Spirit
I will try it now. Your tutorial in the OpenITC have been worked great
Still this IPv6 is pingable 2607:f130:0:1b::2. The others is unreachable
What happens if you manually add them from shell?
@George_Fusioned : I can see the IPv6 in the ifconfig, but still can't be pinged
Can you paste the output of
ip addr
andip -6 route
?well never try debian, but with centos i use this manual
http://chandro.mx/2011/10/red-hat-centos-add-ipv6-network-alias-multiple-ipv6-ip-to-same-nic/
Try nmap -PN ipaddr to see if anything is responding (not sure if nmap has ipv6 support though)
Nmap results to IPv6 address is all port closed
ip -6 route add ::/0 via 2607:f130:0:1b::1 eth0
?
valid_lft forever preferred_lft forever
inet6 2607:f130:0:1b::2/48 scope global
valid_lft forever preferred_lft forever
What if you try:
up /sbin/ifconfig eth0 inet6 add 2607:f130:0:1b::3/48
@Spirit as I understand it all the IP's are visible via ifconfig so adding them is not the issue, its just not routing the additional addresses.
@AnthonySmith yes, exactly - they are visible. But the working one is visible as /48 and those non-working are visible as /64. With some hosts (edis as example) is required to add IPs with /48 mask, so lets try it also here in case your solution suggestion don't work - just to be sure.
oh sorry i missed the /48 /64 difference
If I use the
The working IPv6 would be :
I believe this is called Cargo cult. You keep doing (and advising) something, without any understanding why it was done in the first place. Adding an IP as a /48 would be required if your gateway was not in your /64, but in a different one, because as a side effect this would add a /48 route via eth0 (so then you can reach the gateway). In this case the supplied gateway is in the same /64, so using /48 is not needed. You can, but it will make no difference at all. (If anything, will probably make you unable to reach other VPSes on the same provider).
@ErawanArifNugroho As for the actual problem, I'd say your host has things misconfigured and/or broken with regards to IPv6. Did you try contacting them with this problem?
This will result in:
Because in case you did not know, ::/0 is fully equal to "default", and there's already such a line in the pasted "ip -6 route" output.
Maybe the vps provider have a problem with IPv6 or maybe didn't allocated it well.
I only sent them a Ticket asking the /64 IPv6 ( August 2012 ), and after trying the tutorials from EvoRack and some other place about IPv6 I still failed. Then I keep the vps for several months, just hoping they had another report about IPv6 problem from another users and fix the problem.
November 2012, I ask about IPv6 alocation, and told them that it still failed to work properly. At that time, I even give them a tutorial to be added in the knowledgebase, but still, only working with one IPv6 only
And I try it again last night, because I'm curious about the allocated IPv6.
With the allocation and tutorial from EvoRack, I can add about hundreds of IPv6 in EvoRack vps without problem, and all of them working nicely. But since I don't need much, I just enabling about 20 IPv6 on my EvoRack vps I want to try the same way in this vps, but again, having problem like the start.
Now, the only option for me is just let it expire. Altough it's the best vps connection from my place ( in Los Angeles )
So, thanks for all people which is helping me here