Hi everyone,--- SBBSecho 3.03-Linux
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.
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 islikely to
be some level of temporary disruption for up to 24 hours on someservices,
which will be unavoidable, because some changes require coordinationacross
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 bereconfigured
locally.disruption. If
The D-STAR reflectors are also likely to have some level of
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 (includingmyself!) for
amateur packet radio or other non Internet purposes. If you haveissues,
make sure you route 44.190.8/24 via your ISP's connection and everything should work fine.
Sysop: | Chris Crash |
---|---|
Location: | Huntington Beach, CA. |
Users: | 585 |
Nodes: | 8 (0 / 8) |
Uptime: | 27:04:02 |
Calls: | 10,757 |
Files: | 5 |
Messages: | 452,126 |