| 1 |
On Wednesday, 29 July 2020 16:55:27 BST antlists wrote: |
| 2 |
|
| 3 |
> I think there's static, and there's effectively static. |
| 4 |
> |
| 5 |
> If your router is running 24/7, then the IP won't change even if it's |
| 6 |
> DHCP. But your router only needs to be switched off or otherwise off the |
| 7 |
> network for the TTL (time to live), and DHCP will assign you a different |
| 8 |
> IP when it comes back. |
| 9 |
|
| 10 |
My ISP confirms that my addresses are static. Both IPv4 and IPv6. I don't pay |
| 11 |
extra for static addresses, though I did have to request a v4 one some years |
| 12 |
ago to avoid being blocked from this mail list. |
| 13 |
|
| 14 |
> That's server-side configuration, so if the ISP doesn't elicitly |
| 15 |
> allocate you an address in their DHCP setup, what you've got is |
| 16 |
> effectively static not really static. |
| 17 |
> |
| 18 |
> But it really should be so damn simple - take the ISP's network address, |
| 19 |
> add the last three octets of the customer's router or something like |
| 20 |
> that, and there's the customer's network v6 assigned to the customer's |
| 21 |
> router. One fixed address that won't change unless the customer changes |
| 22 |
> router or ISP. |
| 23 |
|
| 24 |
I don't recognise anything like that pattern in my addresses. |
| 25 |
|
| 26 |
> I need to learn how v6 works ... :-) |
| 27 |
|
| 28 |
Me too. I thought I was set up right, but I now doubt it. |
| 29 |
|
| 30 |
-- |
| 31 |
Regards, |
| 32 |
Peter. |
Archives