• IP address changes

    From Vk3jed@432:1/101 to All on Mon Feb 11 10:22:32 2019
    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.
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (432:1/101)
  • From Vk3jed@432:1/101 to All on Fri Feb 15 19:01:00 2019
    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.
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (432:1/101)
  • From James Groenke@432:1/101 to ref9550 on Fri Feb 15 02:05:51 2019
    --00000000000025b80e0581ebec11
    Content-Type: text/plain; charset="UTF-8"

    Rec'd

    On Fri, Feb 15, 2019, 2:01 AM Vk3jed <vk3jed@freeway.apana.org.au> 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&#39;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 &lt;<a href= =3D"mailto:vk3jed@freeway.apana.org.au">vk3jed@freeway.apana.org.au</a>&gt;=
    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>

    Reposting, because some didn&#39;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>

    =C2=A0&gt; Hi everyone,<br>
    =C2=A0&gt;<br>
    =C2=A0&gt; Just a heads up.=C2=A0 I am in the process of changing IP addres= ses for the<br>
    =C2=A0&gt; system, due to changes at the provider end.=C2=A0 As a result, t= here is likely to<br>
    =C2=A0&gt; be some level of temporary disruption for up to 24 hours on some=
    services,<br>
    =C2=A0&gt; which will be unavoidable, because some changes require coordina= tion across<br>
    =C2=A0&gt; multiple time zones and busy schedules, which is very tricky.<br=

    =C2=A0&gt;<br>
    =C2=A0&gt; At this stage, I anticipate the most affected services will be t=
    he IRLP<br>
    =C2=A0&gt; reflector (native IRLP connections) on shared IRLP/Echolink chan= nels.<br>
    =C2=A0&gt; Echolink connections won&#39;t be as affected, because they can =
    be reconfigured<br>
    =C2=A0&gt; locally.<br>
    =C2=A0&gt; The D-STAR reflectors are also likely to have some level of disr= uption.=C2=A0 If<br>
    =C2=A0&gt; I can get that all done by the one person, this would be minimal=
    , otherwise<br>
    =C2=A0&gt; the downtime could be as much as 24 hours.<br>
    =C2=A0&gt;<br>
    =C2=A0&gt; Many services will be moved to the server&#39;s 44.x block of ad= dresses, which<br>
    =C2=A0&gt; should mean future IP renumbering will be less likely, but may h= ave<br>
    =C2=A0&gt; implications for some people who use 44.x addressing (including = myself!) for<br>
    =C2=A0&gt; amateur packet radio or other non Internet purposes.=C2=A0 If yo=
    u have issues,<br>
    =C2=A0&gt; make sure you route 44.190.8/24 via your ISP&#39;s connection an=
    d everything<br>
    =C2=A0&gt; should work fine.<br>
    </blockquote></div>

    --00000000000025b80e0581ebec11--
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (432:1/101)