Just an update to let everyone know how things are progressing.

Of the allocation of 44.190.8.0/24 that I was allocated a while back, I have allocated a block of 150 IPs for Echolink proxies, which have been operational for around a month.  The server that the proxies run on had some pre-existing Echolink proxies and conference servers.  I migrated the existing (private) proxies to the new binary, which was seamless.

I wasn't sure whether the proxy binary could coexist with the existing conferences, because the proxy binds UDP ports 0.0.0.0:5198 and 0.0.0.0:5199, but in practice, this works fine.

On the weekend, I added a new Echolink conference to the server.  This conference is the first to use one of the new 44net IP addresses (outside the range the proxies use).  Again, everything is working well.  The new allocation is getting a bit of use here.  And I can confirm that running proxies with the binary alongside conference servers works well.  You just have to ensure you use different IP addresses for each in their configs.  :)  I have allocated a block of 10 IPs for the integrated IRLP/Echolink conferences.  Any new conferences will be using these IPs, while legacy ones will remain where they are, unless I need to renumber for some reason, in which case, they will simply be moved to their reserved 44net address.  There's a couple of extra items that will be allocated new IPs in this instance.  Also, the IRLP side may end up on 44net, in the instance of a renumber.  I may simply drop the /28 altogether.

And I'm now very happy, the old juggling to find IPs (I was fully utilising a /28 and starting to bump proxies that weren't getting used) is no longer necessary. :)