[BALUG-Admin] IPv4 IP changes coming!

[Michael Paoli]

Al, yes thanks for the catch.

My bad, labeled incorrectly 8-O
That should've read:
"new"         "old"
96.86.170.224 198.144.194.232 network
96.86.170.225 198.144.194.234
96.86.170.226 198.144.194.235
96.86.170.227 198.144.194.236
96.86.170.228 198.144.194.237
96.86.170.229 198.144.194.238 balug.org./[L]UGs
96.86.170.230 198.144.194.233 gateway
96.86.170.231 198.144.194.239 broadcast

Also note that they're not quite in sequence
(as one has gateway at start of "usable" range,
and the other has gateway at end of "usable" range).

I'll also be updating:
https://www.balug.org/wiki/doku.php?id=system:ip_addresses
it's grossly out-of-date.
Likewise:
http://www.balug.org/dns/ and https://www.balug.org/dns/
... which I'll probably just have redirect to:
https://www.balug.org/wiki/doku.php?id=system:ip_addresses
... at least when I get around to it.

> From: Al <awbalug@sunnyside.com>
> Subject: Re: [BALUG-Admin] IPv4 IP changes coming!
> Date: Wed, 11 Dec 2019 09:38:55 -0800

> Michael,
> I think you switched old and new.
> Since I am set up to slave 5 domains at the 198.144.194.238 address,  
> I suggest just adding 96.86.170.229 to the definition now, and then  
> removing the .238 address when the .229 address is working well.  
> This is in addition to the three IPv6 addresses for various domains.
>
> I don't use any of the other addresses.
> I'll put that up this morning.
> If for some reason the 96.xxx addresses have to get changed, it's easy.
> Al
>
> On 12/11/2019 08:54, Michael Paoli wrote:
>> It's anticipated/hoped, that the IPv4 changes will go approximately as
>> follows:
>> "old"         "new"
>> 96.86.170.224 198.144.194.232 network
>> 96.86.170.225 198.144.194.234
>> 96.86.170.226 198.144.194.235
>> 96.86.170.227 198.144.194.236
>> 96.86.170.228 198.144.194.237
>> 96.86.170.229 198.144.194.238 balug.org./[L]UGs
>> 96.86.170.230 198.144.194.233 gateway
>> 96.86.170.231 198.144.194.239 broadcast
>> The "old" IPv4 IPs will go away >~=2019-12-19, most notably of interest
>> to BALUG/[L]UGs (,SF-LUG, BerkeleyLUG), the IPs noted as:
>> balug.org./[L]UGs
>> Not guaranteed until operational, but expecting likely the "new" IPv4
>> IPs will start to become operational on or slightly after 2019-12-12,
>> and will be transitioned to and made fully operational as quickly as
>> feasible.  It's anticipated there will be some overlap period
>> where both are operational.
>>
>> Both operational(?) ... for a bit?  Yes, at least that's the plan/theory,
>> roughly like this:
>> o new IPs added to hosts
>> o conditional (from) routing added to hosts (from new to use new gateway)
>> o DNS slaves updated on status once masters available on new IPs
>> o new IPs added to DNS (some may go in phases)
>> o "reverse" DNS updates
>> o SMTP "tests" / warm-up
>> o "new" default route; conditional (froms): add "old"; drop "new"  
>> (superseded)
>> o DNS notify IPv4 source updated
>> o "old" IPv4s removed from DNS in advance (>=TTLs) of old IPv4  
>> decommissionings
>>
>>> From: "Michael Paoli" <Michael.Paoli@cal.berkeley.edu>
>>> Subject: IPv4 IP changes coming!
>>> Date: Wed, 13 Nov 2019 05:05:23 -0800
>>
>>> So, I'll be changing ISP (at least for IPv4) ...
>>> that'll mean new IPs for IPv4 ... most notably for these [L]UG domains
>>> (and in general subdomains thereof):
>>> balug.org
>>> sf-lug.org sflug.org sflug.com sflug.net sf-lug.net sf-lug.com
>>> berkeleylug.com berkeleylug.org
>>>
>>> A bit more generally:
>>>
>>> By not later than end of 2019-12-19, these IPv4 IPs (range) will be
>>> "going away"/changing:
>>> 198.144.194.232/29 198.144.194.232 - 198.144.194.239
>>> 198.144.194.232
>>> 198.144.194.233
>>> 198.144.194.234
>>> 198.144.194.235
>>> 198.144.194.236
>>> 198.144.194.237
>>> 198.144.194.238
>>> 198.144.194.239
>>>
>>> At present, my IPv6 is provided from another ISP (tunneled via IPv4),
>>> so I'm expecting the IPv6 IPs will remain the same (at least through
>>> this transition anyway).
>>>
>>> Anyway, hopefully all these changes will happen rather to quite smoothly
>>> ... but a bit early to say.  E.g., as I transition ISPs, there may be
>>> brief(ish) period between, when temporarily neither is available.
>>> We shall see.  I'll update relevant contatct(s)/lists as/when
>>> relevant and appropriate and I'm reasonably able to do so.
>>> Hopefully I can minimize any "user facing" impact ... if I'm
>>> reasonably lucky, may be able to do it quite seamlessly, with
>>> essentially no impact to "users" ... we shall see.
>>>
>>> references/excerpts:
>>> http://linuxmafia.com/pipermail/conspire/2019-November/009966.html