And so it starts. I will be shutting down my VMS, RSRS, RSX, RT11 and VAXeln systems. Up after the weekend, I hope

On Jun 25, 2025, at 12:36 PM, Wilm Boerhout &lt;wboerhout(a)gmail.com&gt; wrote: So, the move has completed and in the process I also took the challenge with a new internet provider. My IP address has changed to: 95.98.255.226 odsw48.mywire.org <http://odsw48.mywire.org/> should resolve to that address. It does on my side. My area router ONAPI4 (29.206) is on the air and the two outgoing circuits I have from that node are up and running. I welcome your feedback on trying the incoming (for me) circuits. Other priorities may interfere, but the end nodes I shut down may come up in the upcoming days/weeks. For now, it is only ONAPI4 and SERIAL, the latter runs on the same host and is lucky enough to be up. That’s all for now, Wilm From: Wilm Boerhout &lt;wboerhout(a)gmail.com&gt; Sent: Thursday, June 12, 2025 12:01 PM To: hecnet(a)lists.dfupdate.se Subject: Advance outage notice Hello friends, I will be moving house on June 20th. Therefore, I will be shutting down my HECnet-related infrastructure a few days before that date; I plan to connect them again a few days (or maybe a week) later. Also, my public IP address will change. “odsw48.mywire.org” will point to the new address, and for my incoming circuits that use the raw IPV4 address, you will have to take that into account. You know who you are 😊 It concerns the following nodes: 29.200 PIVAX0 29.201 PIVAX1 29.202 PIVAX2 29.203 PIVAX3 29.204 PIVAX4 29.205 PIRSTS 29.206 ONAPI4 29.207 VMS046 29.208 PIRTVX 29.209 PIVAXN 29.210 VSIAXP (*) 29.211 PCSAPI (*) 29.212 VAXM8 (*) 29.214 PIZRZV (*) 29.215 PIRSX9 29.221 SERIAL (*) currently not in use Thanks for your understanding, Wilm # supratim(a)riseup.net <mailto:supratim@riseup.net> # tomas(a)prybil.se <mailto:tomas@prybil.se> # bob(a)jfcl.com <mailto:bob@jfcl.com> # Keith.Halewood(a)pitbulluk.org <mailto:Keith.Halewood@pitbulluk.org> # johd(a)zeelandnet.nl <mailto:johd@zeelandnet.nl> # mark.curtis(a)aardvarks-and-platypus.com <mailto:mark.curtis@aardvarks-and-platypus.com> # bqt(a)softjar.se <mailto:bqt@softjar.se> # mark(a)theberrymans.com <mailto:mark@theberrymans.com> # mark(a)matlockfamily.com <mailto:mark@matlockfamily.com>_______________________________________________ HECnet mailing list -- hecnet(a)lists.dfupdate.se <mailto:hecnet@lists.dfupdate.se> To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se <mailto:hecnet-leave@lists.dfupdate.se>

Thanks Mark, looking good! Groet, Wilm (Verstuurd vanaf mijn telefoon, dus wat korter dan gewoonlijk.) (Sent from my phone, so a bit more compact than usual) Op 25 jun 2025 om 21:43 heeft Mark Matlock &lt;mark(a)matlockfamily.com&gt; het volgende geschreven: Wilm, Everything seems to be working for my connection to you. I had to restart the HECnet circuit so MNC would look up your new TCP/IP address connected to http://odsw48.mywire.org/ Let me know if you see any issues from my side. Thanks and Best Regards,’ Mark On Jun 25, 2025, at 12:36 PM, Wilm Boerhout &lt;wboerhout(a)gmail.com&gt; wrote: So, the move has completed and in the process I also took the challenge with a new internet provider. My IP address has changed to: 95.98.255.226 odsw48.mywire.org should resolve to that address. It does on my side. My area router ONAPI4 (29.206) is on the air and the two outgoing circuits I have from that node are up and running. I welcome your feedback on trying the incoming (for me) circuits. Other priorities may interfere, but the end nodes I shut down may come up in the upcoming days/weeks. For now, it is only ONAPI4 and SERIAL, the latter runs on the same host and is lucky enough to be up. That’s all for now, *Wilm* *From:* Wilm Boerhout &lt;wboerhout(a)gmail.com&gt; *Sent:* Thursday, June 12, 2025 12:01 PM *To:* hecnet(a)lists.dfupdate.se *Subject:* Advance outage notice Hello friends, I will be moving house on June 20th. Therefore, I will be shutting down my HECnet-related infrastructure a few days before that date; I plan to connect them again a few days (or maybe a week) later. Also, my public IP address will change. “odsw48.mywire.org” will point to the new address, and for my incoming circuits that use the raw IPV4 address, you will have to take that into account. You know who you are 😊 It concerns the following nodes: 29.200 PIVAX0 29.201 PIVAX1 29.202 PIVAX2 29.203 PIVAX3 29.204 PIVAX4 29.205 PIRSTS 29.206 ONAPI4 29.207 VMS046 29.208 PIRTVX 29.209 PIVAXN 29.210 VSIAXP (*) 29.211 PCSAPI (*) 29.212 VAXM8 (*) 29.214 PIZRZV (*) 29.215 PIRSX9 29.221 SERIAL (*) currently not in use Thanks for your understanding, *Wilm* *# supratim(a)riseup.net &lt;supratim(a)riseup.net&gt;* *# tomas(a)prybil.se &lt;tomas(a)prybil.se&gt;* *# bob(a)jfcl.com &lt;bob(a)jfcl.com&gt;* *# Keith.Halewood(a)pitbulluk.org &lt;Keith.Halewood(a)pitbulluk.org&gt;* *# johd(a)zeelandnet.nl &lt;johd(a)zeelandnet.nl&gt;* *# mark.curtis(a)aardvarks-and-platypus.com &lt;mark.curtis(a)aardvarks-and-platypus.com&gt;* *# bqt(a)softjar.se &lt;bqt(a)softjar.se&gt;* *# mark(a)theberrymans.com &lt;mark(a)theberrymans.com&gt;* *# mark(a)matlockfamily.com &lt;mark(a)matlockfamily.com&gt;* _______________________________________________ HECnet mailing list -- hecnet(a)lists.dfupdate.se To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se _______________________________________________ HECnet mailing list -- hecnet(a)lists.dfupdate.se To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se _______________________________________________ HECnet mailing list -- hecnet(a)lists.dfupdate.se To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se