Subj : Re: IP address changes
To : ref9550
From : James Groenke
Date : Fri Feb 15 2019 02:05 am
--00000000000025b80e0581ebec11
Content-Type: text/plain; charset="UTF-8"
Rec'd
On Fri, Feb 15, 2019, 2:01 AM Vk3jed <
[email protected]> wrote:
> Re: IP address changes
> By: Vk3jed to All on Mon Feb 11 2019 10:22 am
>
> Reposting, because some didn't receive this message. And additional
> information - the IRLP side of the reflector is now on 44.190.8.2.
>
> > Hi everyone,
> >
> > Just a heads up. I am in the process of changing IP addresses for the
> > system, due to changes at the provider end. As a result, there is
> likely to
> > be some level of temporary disruption for up to 24 hours on some
> services,
> > which will be unavoidable, because some changes require coordination
> across
> > multiple time zones and busy schedules, which is very tricky.
> >
> > At this stage, I anticipate the most affected services will be the IRLP
> > reflector (native IRLP connections) on shared IRLP/Echolink channels.
> > Echolink connections won't be as affected, because they can be
> reconfigured
> > locally.
> > The D-STAR reflectors are also likely to have some level of
> disruption. If
> > I can get that all done by the one person, this would be minimal,
> otherwise
> > the downtime could be as much as 24 hours.
> >
> > Many services will be moved to the server's 44.x block of addresses,
> which
> > should mean future IP renumbering will be less likely, but may have
> > implications for some people who use 44.x addressing (including
> myself!) for
> > amateur packet radio or other non Internet purposes. If you have
> issues,
> > make sure you route 44.190.8/24 via your ISP's connection and everything
> > should work fine.
>
--00000000000025b80e0581ebec11
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"auto">Rec'd</div><br><div class=3D"gmail_quote"><div dir=3D=
"ltr" class=3D"gmail_attr">On Fri, Feb 15, 2019, 2:01 AM Vk3jed <<a href=
=3D"mailto:
[email protected]">
[email protected]</a>>=
wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">=C2=A0 Re: IP address chang=
es<br>
=C2=A0 By: Vk3jed to All on Mon Feb 11 2019 10:22 am<br>
<br>
Reposting, because some didn't receive this message.=C2=A0 And addition=
al<br>
information - the IRLP side of the reflector is now on 44.190.8.2.<br>
<br>
=C2=A0> Hi everyone,<br>
=C2=A0><br>
=C2=A0> Just a heads up.=C2=A0 I am in the process of changing IP addres=
ses for the<br>
=C2=A0> system, due to changes at the provider end.=C2=A0 As a result, t=
here is likely to<br>
=C2=A0> be some level of temporary disruption for up to 24 hours on some=
services,<br>
=C2=A0> which will be unavoidable, because some changes require coordina=
tion across<br>
=C2=A0> multiple time zones and busy schedules, which is very tricky.<br=
>
=C2=A0><br>
=C2=A0> At this stage, I anticipate the most affected services will be t=
he IRLP<br>
=C2=A0> reflector (native IRLP connections) on shared IRLP/Echolink chan=
nels.<br>
=C2=A0> Echolink connections won't be as affected, because they can =
be reconfigured<br>
=C2=A0> locally.<br>
=C2=A0> The D-STAR reflectors are also likely to have some level of disr=
uption.=C2=A0 If<br>
=C2=A0> I can get that all done by the one person, this would be minimal=
, otherwise<br>
=C2=A0> the downtime could be as much as 24 hours.<br>
=C2=A0><br>
=C2=A0> Many services will be moved to the server's 44.x block of ad=
dresses, which<br>
=C2=A0> should mean future IP renumbering will be less likely, but may h=
ave<br>
=C2=A0> implications for some people who use 44.x addressing (including =
myself!) for<br>
=C2=A0> amateur packet radio or other non Internet purposes.=C2=A0 If yo=
u have issues,<br>
=C2=A0> make sure you route 44.190.8/24 via your ISP's connection an=
d everything<br>
=C2=A0> should work fine.<br>
</blockquote></div>
--00000000000025b80e0581ebec11--
