11:17:19 I'm moving my first steps in IPv6 in general and with OmniOS in particular! :) I've been assigned a static IPv6 and a default router by by hosting provider. It got me a while to understand that I need to get a link-local address before I can configure the static IP over a NIC... it's right? 12:06:41 Yes, you always need the link-local. So if you're using ipadm you'll need to 12:07:04 ipadm create-addr -T addrconf ... 12:07:15 before setting up the main address with 12:07:26 ipadm create-addr -T static ... 12:08:46 I'm still waiting for my ISP to enter the IPv6 world, we had everything on IPv6 at one of my previous employers but that was about 10 years ago so I haven't used Ipv6 in a while 12:10:13 ok, thanks. Now there is a thing that I do not understand: my hosting provider assigned me a static address with a /128 prefix and the IPv6 address of the default router. But /128 is what web called /32 in IPv4... how the heck I can reach the default router with suck a netmask?! In fact as soon as I try to add a default inet6 route it returns me 12:10:13 that "network is unreachable" 12:22:25 I've queried via WHOIS my static IP and I read that it's allocation has been within a /44 subnet. So I configured this: 12:22:30 I would expect that the /128 refers to the size of the block of addresses they've allocated to you (ie, that there's only one) rather than the mask 12:22:57 Normally I've seen a /64 as the subnet mask 12:23:07 ipadm create-add -T static -a [myIPv6addr]/44 igb0/v6 12:23:42 and I found that an IPv6 default route has just been installed automatically in my inet6 routing table! 12:24:15 I tried using a /64 prefix, but the router'IPv6 address was still outside the subnet address range 12:27:56 sorry, my mistake, the route appeared because of a previous tentative to install it with "route -p add -inet6 default ..." 12:29:06 but with a /44 I was able to set the inet6 default route, and it looks like it works: I'm able to ping ipv6.google.com 21:09:16 warden: reading up a bit /44 sounds odd for an IPv6 allocation, the standard allocation for an organisation is a /48 which they would normally break up into /64 subnets 21:10:30 a /48 allocation gives 2^16 (65,536) subnets of /64 size 21:12:34 some features in IPv6 are designed for a /64 sized network (and in most cases there's not really a good reason to do anything different) 22:19:04 Here is the network block my assigned IPv6 address is within: https://search.arin.net/rdap/?query=2607%3A5300%3A60%3A78d0%3A%3A1 22:21:09 I deduced the /44 prefix from there, but my IPv6 knowledge is ehm, less than sub-optimal! :S 22:43:15 The /44 is the amount of address space allocated to OVH as a whole 22:46:12 If your ISP is allocating you a /128 that's... damn near criminal. 22:46:17 Most likely you got a /64. 22:46:59 Are the gateway and your assigned address w/in the same /64 block? 22:50:32 2607:5300:60:78d0:: would the the right length for a /64 22:52:56 nomad: if it's a VPS (likely because OVH is a cloud provider), a /128 to start off with would not be unreasonable. 22:53:42 nomad: actually, since my address is 2607:5300:60:78d0::1, a /64 prefix would not include the address of my assigned gateway, which is 2607:5300:0060:78ff:00ff:00ff:00ff:00ff. At least a /48 prefix would be needed, I guess 22:53:52 ah, hosting provider. I was thinking NSP 22:54:22 warden, I think you should contact them ask ask what the prefix is, pointing out the problem you're having. 22:55:40 Surely I’ll ask them, and I’ll post their reply. Thanks 22:56:27 there might be some stuff you can adapt from https://help.ovhcloud.com/csm/en-gb-vps-configuring-ipv6?id=kb_article_view&sysparm_article=KB0047569 22:58:14 that has (for linux) configuring the IP, setting a route for the default gateway on the if, then setting the default route to the gateway addr. 22:58:56 which I think is a valid setup, but slightly weird (especially if you've not seen that sort of thing before) 23:00:48 ohh, I don't like that setup at all. 23:01:00 "here, force your computer to think it's on the same block as the gateway" 23:01:39 Off-subnet gateways are regretably common in down-market hosting providers 23:01:47 so, as I read it, you have to set up your host with the /128 prefix then force a default route to point to the gateway that's in another block. 23:01:48 I'm somewhat surprised that they would be common in IPv6 though 23:02:02 (makes sense, sort of, for constrained IPv4 environments) 23:02:08 I'd prefer they used the link-local for the gateway if they're going to play those games. 23:02:14 right 23:04:01 I'm glad I've never encountered that in any form anywhere. 23:04:07 I hope that continues to be the case for me. 23:04:15 * nomad closes the tab before his eyes start bleeding 23:06:36 might as well us PPP at that point. 23:08:33 and if they've allocated ::1 as the system IP I suspect internally they've allowed for the whole /64 to be used by that vps (or maybe customer) so why not just do something sensible 23:11:04 so far I've only ever seen that sort of hack on IPv4 where a subnet has been allocated on the end of a ppp tunnel for DSL type services (I've had a few instances of having a /29 allocated as a customer and the default route is down an un-numbered PPPoA or PPPoE link) 23:11:41 point-to-point makes *some* sense for not wasting IPv4 addresses. 23:12:10 but AIUI IPv6 intended for /64 to be the smallest allocated block so people wouldn't have to mess with this kind of garbage config. 23:17:18 /64 is generally the smallest recommended allocation for a subnet, I think the only exception that's sometimes made is for something that's only ever going to be a P2P link between routers (but even then the argument is but why not just use a /64 - you have enoguh of them) 23:18:29 with the standard /48 allocation you've got as many subnets (of /64) as a site with an IPv4 class B (/16) has addresses. 23:47:44 having default point at a link-local address for the gateway would make more sense than what OVH is doing. 23:48:19 (oh, sorry, nomad already said that) 23:51:00 Yeah I feel like IPv6 link locals were invented, basically, exactly for this haha