• Re: NET 4 Changes

    From Avon@21:1/101 to All on Saturday, March 30, 2024 21:23:04
    On 28 Mar 2024 at 10:40a, Avon pondered and said...

    On 17 Mar 2024 at 02:13p, Avon pondered and said...

    Please ensure you are polling net4.fsxnet.nz:24560

    another reminder if you are a NET 4 node please ensure you have the above domain name and port set up to poll the 21:4/100 HUB.

    When we cut over to the new NET 4 HUB instance I will update the DNS records to point to the new HUB.

    I plan to do this on 31 March (my time in New Zealand, or likely to b 30 March elsewhere in the world)... and when I do we will ensure the file and echomail links to the 'old' HUB will be closed down. I'll th ask Dan to shutdown that server.

    this is coming the in the next few days.

    I'm picking if some sysops who run their BBS on 'auto' then login to find no new traffic on fsxNet they may come calling to me then. We'll that's the thinking..

    I am also aware that there are a number of inactive nodes in NET 4 an plan to prune them in early April once the cut over is done. In the meantime I have taken over NET 4 nodelist segment duties and marked a number of nodes a 'Down' that appear to be long inactive based on sta Dan's system is posting each day to the Stats echo.

    ..as is this :)

    Final call, all NET 4 nodes.. ding ding...

    OK folks I'm starting the change over process now, so this will mean some niggles for active NET 4 nodes over the coming 24 hours.

    Shortly I will be de-linking NET 1 from the 'old' NET 4 HUB and updating the DNS records for net4.fsxnet.nz to point to the new of NET 4 instance I will be running. I'll also link NET 1 to this new version of the NET 4 HUB.

    If you're a NET 4 node and have net4.fsxnet.nz:24560 set up then over the coming 24 hours as DNS records change over you should start to hit the new version of the HUB and (hopefully) have no issues polling in to collect/send packets etc.

    If you're a NET 4 node and continue to poll and/or send packets to the 'old' NET 4 HUB you're traffic is only going to go to those nodes in NET 4 who remain linked to the old HUB. All the other HUBs will / already are shortly to be delinked from that 'old' HUB.

    If you're a NET 4 node and having issues getting hooked up to the new instance of the NET 4 HUB please email me avon@bbs.nz and I'll work with you to get hooked up.

    In the coming 2 weeks once the cut over has occurred I plan to revisit the NET 4 nodelist segment and prune it where necessary.

    I'll also work to start posting some stats from the NET 4 system I have spun up but that's a secondary priority at the moment.

    x-posting this to FSX_NET and FSX_GEN

    Best, Paul

    Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

    --- Mystic BBS v1.12 A48 (Linux/64)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to All on Saturday, March 30, 2024 22:52:56
    On 30 Mar 2024 at 09:23p, Avon pondered and said...

    OK folks I'm starting the change over process now, so this will mean some niggles for active NET 4 nodes over the coming 24 hours.

    Shortly I will be de-linking NET 1 from the 'old' NET 4 HUB and updating the DNS records for net4.fsxnet.nz to point to the new of NET 4 instance
    I will be running. I'll also link NET 1 to this new version of the NET 4 HUB.

    now underway, changing from 72.24.172.12 to now pointed to 103.193.138.76

    NET 4 nodes need to point to port 24560 on this new IP address, so

    net4.fsxnet.nz:24560

    Shortly I will be de-linking NET 1 from the 'old' NET 4 HUB and updating

    This has been done, in the process I may have accidentally deleted FSX_GEN and FSX_DAT from the now retired HUB. Turns out my delink commands were being taken as a 'delete' command - eek! But the rest of the echos have been paused on the old HUB so no further traffic is flowing into the NET 1 HUB from that old system now.

    The new NET 4 HUB has been started up and nodes that were linked to their chosen echos in NET 4 are being fed by this system now.

    If you're a NET 4 node and having issues getting hooked up to the new instance of the NET 4 HUB please email me avon@bbs.nz and I'll work with you to get hooked up.

    In the coming 2 weeks once the cut over has occurred I plan to revisit
    the NET 4 nodelist segment and prune it where necessary.

    I'll also work to start posting some stats from the NET 4 system I have spun up but that's a secondary priority at the moment.

    still to do.

    Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

    --- Mystic BBS v1.12 A48 (Linux/64)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)