Howdy, Stranger!

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


IPV6 /64 subnet on vps.. HELP
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.

IPV6 /64 subnet on vps.. HELP

golden419golden419 Member
edited March 2016 in Help

The story is that I requested for ipv6 on one of my vps and got a /64 subnet sent to me through customer service chat. My problem is this..
1. How can I configure this to be used on my VPS?
2, I have 2 vps services from same provider.
3. My CP shows ipv6 0.
Any help will be appreciated..

N/B the vps are openvz

Comments

  • You need to add addresses from the subnet in SolusVM, click Network when viewing your VPS. You can't add all the IP's from the subnet, the more you add the longer it takes to boot your container...

  • elgselgs Member

    If you cannot configure it from a web control panel, try this command:

    # /sbin/ip -6 addr add 2001:0db8:0:f101::1/64 dev eth0

  • @elgs said:
    If you cannot configure it from a web control panel, try this command:

    # /sbin/ip -6 addr add 2001:0db8:0:f101::1/64 dev eth0

    Its openvz. With the command it says Cannot find device "eth0"

  • @linuxthefish said:
    You need to add addresses from the subnet in SolusVM, click Network when viewing your VPS. You can't add all the IP's from the subnet, the more you add the longer it takes to boot your container...

    The network area only shows my ipv4

  • @elgs said:
    If you cannot configure it from a web control panel, try this command:

    # /sbin/ip -6 addr add 2001:0db8:0:f101::1/64 dev eth0

    Unless you are using veth device don't even try to touch the networking config from inside the container!

  • golden419 said: The network area only shows my ipv4

    Then your provider messed up, get them to fix it!

  • golden419golden419 Member
    edited March 2016

    Been trying but they think that its my fault....

  • @golden419 said:
    Been trying but they think that its my fault....

    If it's not showing any IPv6 in the network tab of SolusVM (if that's what you're using) then your provider messed up, get them to add a subnet properly.

  • Will keep trying. This is the third day....

  • elgselgs Member
    edited March 2016

    @golden419 said:
    Its openvz. With the command it says Cannot find device "eth0"

    Try change eth0 to venet0 or venet0:0.

  • elgselgs Member

    @DamianWasHisName said:
    am i dumb or is a /64 on ipv6 1 address?

    If OP is sure she/he is assigned with a whole /64, the ipv6 address could be any of the 2^64.

  • @elgs said:
    If OP is sure she/he is assigned with a whole /64, the ipv6 address could be any of the 2^64.

    OpenVZ doesn't work like that unless it's a virtual ethernet device bridged on the host side. With venet the IPv6 address needs to be added to the container config, and that can only be done from SolusVM on the client side not from inside the VPS.

    All assigning a subnet in SolusVM does it allow the user to add individual addresses from their subnet to the VPS, and does not route the /64 as with full virtualisation.

Sign In or Register to comment.