Hub_NA Status
The following stations in North America are connected to Hub_NA:
N2NOV (1s) #1 [0 | 0.0% | jnos2.0.6.uro] va2om (1s) #1 [0 | 0.0% | jnos2.0m.curo] jtnet (1s) #1 [0 | 0.0% | jnos2.0m] SaltLk_US (1s) #1 [0 | 0.0% | saupp1.62a] - RpiJnos (2s) #2 [0 | 0.0% | jnos2.0m] Aurora_CAN (1s) #1 [0 | 0.0% | jnos2.0n.beta]
There is plenty of room for your station to join the rest of us.
On 2/9/2020 9:22 AM, Charles J. Hargrove via 44Net wrote:
After some hiccups, Hub_NA is reachable to non-44Net addresses (but only if you email me the address first for inclusion in the access list). The 44Net addresses were always able to connect.
On 1/28/2020 4:01 PM, Charles J. Hargrove via 44Net wrote:
I had thought of making this available to the 44Net community, but if anyone is not able to connect via 44Net and would rather use a static IP, then send me a private email with the particulars at n2nov@n2nov.net
On 1/28/2020 12:54 PM, Bill Vodall via 44Net wrote:
Is this for 44 net only or could a JNOS/Linux box with static IP participate?
On Tue, Jan 28, 2020, 7:56 AM David Ranch via 44Net 44net@mailman.ampr.org wrote:
Thank you for taking this service over! I'll give it try!
--David KI6ZHD
On 01/27/2020 08:07 PM, Charles J. Hargrove via 44Net wrote:
With the shutdown of the WA7V system after a long and dedicated stretch, Hub_NA of the WWconvers needed a new home. With the help of WA7V and testing with KD6OAT, Hub_NA is still functioning but with a new IP address of 44.68.41.2 (gw.n2nov.ampr.org) on port 3600. The software also has the capability to make use of IRC clients that we might get included in a future version of JNOS. All bbs sysops in North America are welcome to connect their chat clients and servers to Hub_NA and join the rest of the WWconvers network. There is plenty of room for specialized convers channels. For the 44Net allocations in NY State (44.68/16) I suggest a common channel of #4468 to chat among ourselves.