On 12/8/21 1:29 am, Dave Gingrich via 44Net wrote:
Tony,
IRLP will be no problem, all we need to know is when a new IP is available and working. There is no reason you couldn’t run with both the old and new IP simultaneously for a short time. Folks will connect to whatever the database says is the IP. Worst case it should take only a few hours for the new IP to circulate through the IRLP network.
That may work in the case of a simple, standard IRLP reflector running sfreflect, it's a lot more complex with mine, because of the specific IP bindings, hence the need of coordination. Every tbd or tlb instance I run has a SFBind2IP set to the reflector's IP. I started doing that when I had address selection issues, which caused the wrong IP to be used from reflector to client. And I may have had port conflicts without specific bindings as well in the past. I haven't audited the system for those conflicts lately, as there has been no need.