3 ms·

First of all, can you point me in the direction where I can get a static IPv6 block from AT&T easily so it will "just work"? Or maybe google fiber for IPv6? [1]

First of all, can you point me in the direction where I can get a static IPv6 block from AT&T easily so it will "just work"? Or maybe google fiber for IPv6? [1] There is currently more of a shortage of IPv6 (!!) in terms of getting a static block then there is with IPv4 in my experience. I'm really tired of hearing it will "Just work" - that's proven to be a lie over and over. But I would love to be shown where these major players do their static blocks for ipv6 (having fought this fight for a while). Are you using comcast? I think they only DYNAMICALLY assign you a 64 - so you can only create ONE subnet on your entire network. Again illustrating the shortage and difficulty in using IPv6. I'd thought /48 would be minimum PD, but that is not the case. Or even a /60? No go. There are workarounds I'm aware of, but this stuff absolutely DOES NOT "just work". [1] - https://support.google.com/fiber/answer/6136162?hl=en&ref_topic=9359263 https://support.google.com/fiber/answer/6136162?hl=en&ref_to...

simoncion 4y ago
Really hoping you come back and read this comment, but perhaps I am too late: > Are you using comcast? I think they only DYNAMICALLY assign you a 64... In my experience here in San Francisco with both IPv4 and IPv6 service (and IPv4 service elsewhere in the US years and years ago) Comcast will give you a v4 IP (or v6 subnet) for as long as the same edge device (or an edge device with the same MAC address (or DUID for v6)) continues to renew the lease. So, yeah, it's dynamic in theory, but static in practice. > Or even a /60 [via DHCPv6-PD]? Weird. Configuring my DHCPv6 server to do Prefix Delegation and request a /60 always worked just fine for me. I was disappointed that I couldn't get a /56 or /48, but was okay with the /60 that they gave me. Again, this was in San Francisco, so maybe other parts of the country are managed _way_ differently. Maybe. Alternatively, are you _sure_ that the DHCP-PD request was refused and that that you didn't -say- fail to configure your system to actually assign slices of the /60 to your LAN? ... Actually, now that I'm thinking about it, I seem to recall a problem like you're describing. If I'm not misremembering that I had this sort of problem, then, maybe, try configuring your edge device to ask for a /60, change the DUID that it will use to make the request, and then bounce the WAN interface (or reboot the device, or do whatever is required to apply the changes). My memory is absolute shit (and likes to hallucinate things that never happened), so this might not do anything useful. But it's usually a pretty easy thing to try.

simoncion 4y ago

Really hoping you come back and read this comment, but perhaps I am too late: > Are you using comcast? I think they only DYNAMICALLY assign you a 64... In my experience here in San Francisco with both IPv4 and IPv6 service (and IPv4 service elsewhere in the US years and years ago) Comcast will give you a v4 IP (or v6 subnet) for as long as the same edge device (or an edge device with the same MAC address (or DUID for v6)) continues to renew the lease. So, yeah, it's dynamic in theory, but static in practice. > Or even a /60 [via DHCPv6-PD]? Weird. Configuring my DHCPv6 server to do Prefix Delegation and request a /60 always worked just fine for me. I was disappointed that I couldn't get a /56 or /48, but was okay with the /60 that they gave me. Again, this was in San Francisco, so maybe other parts of the country are managed _way_ differently. Maybe. Alternatively, are you _sure_ that the DHCP-PD request was refused and that that you didn't -say- fail to configure your system to actually assign slices of the /60 to your LAN? ... Actually, now that I'm thinking about it, I seem to recall a problem like you're describing. If I'm not misremembering that I had this sort of problem, then, maybe, try configuring your edge device to ask for a /60, change the DUID that it will use to make the request, and then bounce the WAN interface (or reboot the device, or do whatever is required to apply the changes). My memory is absolute shit (and likes to hallucinate things that never happened), so this might not do anything useful. But it's usually a pretty easy thing to try.