Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Need help with ipv6
New on LowEndTalk? Please Register and read our Community Rules.

Need help with ipv6

edited January 2013 in Help

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?

    AboveClouds • UK Company • UK Datacentre • UK Customer Support

    High Performance Pure SSD Cloud Hosting with a personal touch

  • InfinityInfinity Member, Provider

    @Jacob said: 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.

  • csf running, blocking ICMPv6?

    Fusioned | KVM SSD VPS | LSI RAID10 | Netherlands 1Gbps | Acronis Cloud Backups | IPv4 & IPv6 | SolusVM
  • tehdantehdan Member
    edited January 2013

    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 :

    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:0:1b::3/64
        up /sbin/ifconfig eth0 inet6 add 2607:f130:0:1b::4/64
        up /sbin/ifconfig eth0 inet6 add 2607:f130:0:1b::5/64
        up /sbin/ifconfig eth0 inet6 add 2607:f130:0:1b::6/64
        up /sbin/ifconfig eth0 inet6 add 2607:f130:0:1b::7/64
        up /sbin/ifconfig eth0 inet6 add 2607:f130:0:1b::8/64
        up /sbin/ifconfig eth0 inet6 add 2607:f130:0:1b::9/64
        up /sbin/ifconfig eth0 inet6 add 2607:f130:0:1b::10/64
    
    [email protected]:~# ping6 -c 6 2607:f130:0:1b::2
    PING 2607:f130:0:1b::2(2607:f130:0:1b::2) 56 data bytes
    64 bytes from 2607:f130:0:1b::2: icmp_seq=1 ttl=57 time=68.2 ms
    64 bytes from 2607:f130:0:1b::2: icmp_seq=2 ttl=57 time=68.4 ms
    64 bytes from 2607:f130:0:1b::2: icmp_seq=3 ttl=57 time=68.7 ms
    64 bytes from 2607:f130:0:1b::2: icmp_seq=4 ttl=57 time=68.9 ms
    64 bytes from 2607:f130:0:1b::2: icmp_seq=5 ttl=57 time=68.2 ms
    64 bytes from 2607:f130:0:1b::2: icmp_seq=6 ttl=57 time=68.8 ms
    
    --- 2607:f130:0:1b::2 ping statistics ---
    6 packets transmitted, 6 received, 0% packet loss, time 5004ms
    rtt min/avg/max/mdev = 68.212/68.578/68.951/0.356 ms
    [email protected]:~# ping6 -c 6 2607:f130:0:1b::3
    PING 2607:f130:0:1b::3(2607:f130:0:1b::3) 56 data bytes
    From 2607:f130::5 icmp_seq=1 Destination unreachable: Address unreachable
    
    --- 2607:f130:0:1b::3 ping statistics ---
    6 packets transmitted, 0 received, +1 errors, 100% packet loss, time 5000ms
    

    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?

  • SpiritSpirit Member
    edited January 2013

    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

  • edited January 2013

    What happens if you manually add them from shell?

    ip -6 addr add 2607:f130:0:1b::3/64 dev eth0
    ip -6 addr add 2607:f130:0:1b::4/64 dev eth0
    ip -6 addr add 2607:f130:0:1b::5/64 dev eth0
    [...]
    Fusioned | KVM SSD VPS | LSI RAID10 | Netherlands 1Gbps | Acronis Cloud Backups | IPv4 & IPv6 | SolusVM
  • @George_Fusioned : I can see the IPv6 in the ifconfig, but still can't be pinged

  • Can you paste the output of ip addr and ip -6 route?

    Fusioned | KVM SSD VPS | LSI RAID10 | Netherlands 1Gbps | Acronis Cloud Backups | IPv4 & IPv6 | SolusVM
  • Nothing for the moment

  • Try nmap -PN ipaddr to see if anything is responding (not sure if nmap has ipv6 support though)

  • # ip addr
    1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN
        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
        inet 127.0.0.1/8 scope host lo
        inet6 ::1/128 scope host
           valid_lft forever preferred_lft forever
    2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP ql
    en 1000
        link/ether 00:16:3e:75:5c:7d brd ff:ff:ff:ff:ff:ff
        inet 108.166.200.135/24 brd 108.166.200.255 scope global eth0
        inet6 2607:f130:0:1b::3/64 scope global
           valid_lft forever preferred_lft forever
        inet6 2607:f130:0:1b::2/48 scope global
           valid_lft forever preferred_lft forever
        inet6 fe80::216:3eff:fe75:5c7d/64 scope link
           valid_lft forever preferred_lft forever
    3: tun0: POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP mtu 1500 qdisc pfifo_fast sta
    te UNKNOWN qlen 100
        link/none
        inet 10.8.0.1 peer 10.8.0.2/32 scope global tun0
    
    # ip -6 route
    2607:f130:0:1b::/64 dev eth0  proto kernel  metric 256  mtu 1500 advmss 1440 hop
    limit 0
    2607:f130::/48 dev eth0  proto kernel  metric 256  mtu 1500 advmss 1440 hoplimit
     0
    fe80::/64 dev eth0  proto kernel  metric 256  mtu 1500 advmss 1440 hoplimit 0
    default via 2607:f130:0:1b::1 dev eth0  metric 1  mtu 1500 advmss 1440 hoplimit
    0
    

    Nmap results to IPv6 address is all port closed

  • ip -6 route add ::/0 via 2607:f130:0:1b::1 eth0
    ?

    I am no longer active here, find me at https://talk.lowendspirit.com

  • SpiritSpirit Member
    edited January 2013
    inet6 2607:f130:0:1b::3/64 scope global
    

    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.

    I am no longer active here, find me at https://talk.lowendspirit.com

  • SpiritSpirit Member
    edited January 2013

    @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

    I am no longer active here, find me at https://talk.lowendspirit.com

  • If I use the

    up /sbin/ifconfig eth0 inet6 add 2607:f130:0:1b::3/48

    The working IPv6 would be :

    2607:f130:0:1b::2
    2607:f130:0:1b::3
    2607:f130:0:1b::4 - 100% packet loss
    2607:f130:0:1b::5 - 100% packet loss
    2607:f130:0:1b::6 - 100% packet loss
    2607:f130:0:1b::7 - 100% packet loss
    2607:f130:0:1b::8 - 100% packet loss
    2607:f130:0:1b::9 - 100% packet loss
    2607:f130:0:1b::10
    2607:f130:0:1b::11 - 100% packet loss
    2607:f130:0:1b::12 - 100% packet loss
    2607:f130:0:1b::... 100% packet loss since this IPv6
    
    2607:f130:0:1b::10:1
    2607:f130:0:1b::10:2 - 100% packet loss
    ... 100% packet loss since this IPv6
    
    
  • rm_rm_ Member
    edited January 2013

    @Spirit said: With some hosts (edis as example) is required to add IPs with /48 mask,

    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?

  • rm_rm_ Member

    @AnthonySmith said: ip -6 route add ::/0 via 2607:f130:0:1b::1 eth0

    This will result in:

    RTNETLINK answers: File exists

    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.

    @rm_ said: Did you try contacting them with this problem?

    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 :)

Sign In or Register to comment.