Routed IPv6 subnets at Strike

Comments

• mans_xd Member

  January 18

  @tentor the smart guy is everywhere
  Congratulations!

  Have a nice day

  Thanked by 33K33 tentor oloke
• oloke Member, Host Rep

  January 18

  Really happy this being available!
  Also thanks for sharing virtualizor script for others.

  cc: @yoursunny

  Thanked by 13K33
• ascicode Member

  January 18

  KYC, no?

  Thanked by 1oloke
• kait Member

  January 18

  @ascicode said:
  KYC, no?

  No sir
• 3K33 Member, Host Rep

  January 18 edited January 18

  @ascicode said:
  KYC, no?

  I'm not participating in that bullshit, no KYC guaranteed.

  Thanked by 6oloke Nekopara lukast__ zGato fluffernutter forest
• yoursunny Member, IPv6 Advocate

  January 18 edited January 18

  @3K33 said:
  To make this easier, we’ve published a script on GitHub. If you’re using Virtualizor, this script allows you to seamlessly add routed subnets to your setup. Repo is available here.

  We checked this script and it seems correct.

  Its behavior is: when a customer VM is assigned one or more IPv6 address with associated subnet size, each main address is attached as on-link and the expanded subnet is routed to the main address.
  For example, suppose the VM is assigned 2001:db8:90c9:9a66::1/56, it means the VM is given 2001:db8:90c9:9a00::/56 routed subnet with an on-link address 2001:db8:90c9:9a66::1 that must be assigned inside the VM.

  A pitfall in current code is that, if the VM is assigned more than one address in the same subnet, the script will suffer an error trying to insert duplicate routes.
  For example, if the above VM is also assigned 2001:db8:90c9:9a66::2/56, the script would try to insert another route for 2001:db8:90c9:9a00::/56 subnet and iproute2 won't allow that.
  To make the script more robust, change ip route add to ip route replace, so that the last on-link address becomes the next hop of the route.

  We can deduce these requirements on the router at the previous hop:

  • If you do not need live migration, the large subnet that contains all customer subnets shall be routed to the on-link address of the physical server.
  • If you want live migration, each customer VM subnet must be individually routed to the VM's on-link address.
  • It will not work at all, if the physical machine itself only receives on-link subnet.

  Thanked by 43K33 oloke zGato JohnnySac
• Nekopara Member

  January 18 edited January 18

  happy about this! another big PLUS for the service

  Thanked by 23K33 oloke
• 3K33 Member, Host Rep

  January 18

  @yoursunny said:

  @3K33 said:
  To make this easier, we’ve published a script on GitHub. If you’re using Virtualizor, this script allows you to seamlessly add routed subnets to your setup. Repo is available here.

  We checked this script and it seems correct.

  It's behavior is: when a customer VM is assigned one or more IPv6 address with associated subnet size, each main address is attached as on-link and the expanded subnet is routed to the main address.
  For example, suppose the VM is assigned 2001:db8:90c9:9a66::1/56, it means the VM is given 2001:db8:90c9:9a00::/56 routed subnet with an on-link address 2001:db8:90c9:9a66::1 that must be assigned inside the VM.

  A pitfall in current code is that, if the VM is assigned more than one address in the same subnet, the script will suffer an error trying to insert duplicate routes.
  For example, if the above VM is also assigned 2001:db8:90c9:9a66::2/56, the script would try to insert another route for 2001:db8:90c9:9a00::/56 subnet and iproute2 won't allow that.
  To make the script more robust, change ip route add to ip route replace, so that the last on-link address becomes the next hop of the route.

  We can deduce these requirements on the router at the previous hop:

  • If you do not need live migration, the large subnet that contains all customer subnets shall be routed to the on-link address of the physical server.
  • If you want live migration, each customer VM subnet must be individually routed to the VM's on-link address.
  • It will not work at all, if the physical machine itself only receives on-link subnet.

  Thanks for the information. Afaik when you generate subnets in Virtualizor, it only assigns first IP to VPS, you can't specify more onlink IPs in that generated subnets (eg. you can't assign ::2 of on-link subnet), but we will check this and change the code if neccessary.

  Thanked by 1oloke
• zGato Member

  January 18

  one more reason to use @3K33 and @tentor services

  huge W

  to all my ipv6 haters
  

  Thanked by 6tentor lukast__ oloke sh97 3K33 fluffernutter