In the networking selection>eth0, you can change your ip address to a static ip... while changing the address to a 44net address, I failed a few times, showing "Reconnecting." Messed up my new card, so had to write a new one and try the ham44 address again.... failed! There's got to be a system to do this... When do I connect the ethernet cable to the new router that hosts the ham44 ip addresses????
I'm not sure I'm understanding your question. Where are you trying to set an IP address? Do you have a local network with a 44Net IP allocation assigned to it?
Yes, I have a Mikrotik router with 44 ip addresses on it.. been using these for years...
I did get it to connect this morning... after it fails to connect to the new ip, it gives a popup to keep settings, selected that, changed ethernet cables to Mikrotik and rebooted...back on with 44 address. The benefit of these 44 addresses are: bypasses CGNAT in your router using Wireguard and no ports are blocked. The benefit of ASL3 is that it has an active firewall that is only set to allow ports you need. Dammm, took me a week!
Back to the drawing board! Using these methods, I get the ASL3 Pi to connect to the router. I can connect to the ASL3 node dashboard and can SSH into it to make changes. But, it is not being registered to allstarlink... I can use allmon3 to connect to a node and it says, "OK," but no connection occurs.... I have a Hamvoip node connected to the same Mikrotik router for years.
Can you provide the real information on what you're trying to do? That screenshot from Cockpit can't be valid so I'm assuming you masked your information.
44.62.14.115 if you want the password, email me
No, I don't need the password. Looking at the AMPR registry, you're assigned 44.62.14.0/24 and you're advertising out of Vultr? If that's correct I'm assuming then that you're tunneling some smaller portion back to your home or some other location? There's nothing special about the ASL3 Pi Appliance that wouldn't work with 44Net - many are. As long as you have your address, netmask, and gateway set in the ASL3 Pi Appliance then your network should be doing the rest. I've run many devices on a 44Net tunneled address space with no issues and, coincidentally, also using Mikrotik RouterOS.
When you keep talking about "Reconnecting" what are you meaning?
I knew your call sounded familiar! When you go to "Networking" in ASL3 to change IP addresses, after the change it will test the ip address. If it fails to find the new ip address, it will attempt to go back to the original (DHCP) address. That is where you get the "Reconnecting" message.
I just set up an HV node on the same router and it connects to Allstar, so it's not the router or the ip address .Something tells me that allmon3 is the issue. I cannot get into the allmon3.ini file, so will install Supermon and see what is going on. Thank you for the brainwaves!!!
Allmon3 nor Supermon will do anything for networking nor will let you see anything about the interfaces. Do you have a screen and monitor to login locally to see what happens when you're changing it? How are you connecting to Cockpit after changing the IP? I'll never reconnect on its own because the host has moved.
I just go to the 44 address to connect. The node dropped off my 44 address. Taking a long break!!! Thank you...
Understanding asking your not what. 
you’re not clearly articulating the issue you’re experiencing.
Write it up in ChatGPT and ask it to clearly articulate the message.
OK, still working on this... the 44.62.14.x addresses are on a Mikrotik router that uses wireguard to connect through a tunnel to the vultr hosting service. Not mine, but I get the routers configured by them for my house.
They do not use DHCP to connect to the 44 addresses. The addresses are programmed in the router and to use them you have to set the device (ASL3) to one of the 44 ip addresses. I have a couple of ASL3 nodes setup on the mikrotik.... but it is a hit or miss effort to get them to connect to the mikrotik.
What I have to do is go into eth0 and set the 44 address in there and apply. I then have to rush over to the home router, pull the cable and quickly put that into the mikrotik. Sometimes works....
I have a node I just did that to and it doesn't connect to mikrotik and when I put it back on home router, it fails there also. (it was a good node, too!) Anyway, there has got to be a better way to do this AND if I can find where ip addresses are stored (file), change it back. I can bring the good node back to life! de NH6FU
Why not use DHCP with MAC address reservation on the available 44net subnet? Then the client never needs to be set statick, the node will always get the correct IP address, and it will be portable if it needs to move to another network. That's what I'd do, anyway.
I'd probably have all the 44net stuff on a VLAN such that at least one port on the Mikrotik is outside of 44net.
Aside from that, do you have a USB Ethernet dongle? Plug that in and stick it on your normal router. Should get an IP address from DHCP, because it is not ETH0.
Also, you may find interesting stuff in /etc/network/interfaces.d
but be careful editing stuff manually. Or, plug in a keyboard and monitor for direct console access if you can, and fix things that way. Probably safer.
The USB ethernet trick did it. Thanks!
The mikrotik (an L009) is locked tight so no mods to it and it does not have DHCP.. And I have never been able to get a mikrotik router on 44... GL-Inet's yes... a bunch!
Now, at least I have a way to get my ASL3 nodes on 44!
You should make your own AI! Patrick AI, how do I do it?
Sure it does. A Mikrotik L009UiGS-RM is a full-featured router with RouterOS v7 Level 5. I use a similar RB5009UG+S+ and it works perfectly. Your having to switch around between your home router and the Mikrotik makes it sound like you have something else squirrely going one like your cable model isn't detecting a change in CPE without restarting the cable modem.
Ok, the L009 is perfectly capable of doing DHCP, but in this case, DHCP has been disabled, for reasons I have no idea.... My gl-inet routers issue 44 addresses using DHCP or I can set the device to static... both ethernet and wifi. I was told of a method to put a USB to ethernet adapter in and use that to program the ASL3 node to a static address... simple and worked GREAT!