Om stands for, "old man!"

OS Help
1

OK, ASL3 is good!!! EXCEPT for OM’s!!! I have created several nodes and have done the same thing… somehow… I just try to fix it or start over again and again! BULL! I am coming up on 50 years as a ham, which means. “I AM OLD.” OK, now, passwords:

-OK, “ROOT” to log in to in to linux. but not “root.” Created when I use pi imager… you know, your callsign and your callsignxxxx. Got it!

The the AMI password, created by ASL3 that is impossible to remember. So ASL came up with the –delete to create a different one and maybe put it where it belongs, maybe not.

Supermon/allscan- I create that myself!!!

Allstarlink password on Allstarlink site (nodes)- they create, I change.

Allmon3 password to log in to allmon3???

So, now for my issue (besides multiple passwords…)

Created a(nother node). Put Supermon on it, cuz I like it and am used to it… you know, “OM.” Also, generally put Allscan on it, if it is going to be a hub. An then I ignore ALLMON3! Except when it gives me a red message! ALMON3 says, “Allmon3 is not responding to requests for this node. Check server logs.” So, I check the server logs— “ERROR: (asl_allmon.allmon3_ws_status) No connection for 127.0.0.1:5038 on 16700 due to unreachable AMI - waiting 15 seconds.” (My response is usually, DOH!”)

Usually, I just go in to allmon3.ini and comment out the alphanumeric password and put in my allstar password from the nodes page. This time, NOPE!

Really? Ok, I know the younger people like all these passwords and those supersecret alphanumeric stuff… but isn’t this just going a little overboard! (Yes, I am switching over to ASL3 because I can’t get the firewall to work on HV) .

Someone please talk to me about the AMI password!!! WHY? WTH?

2

the password allmon3.ini needs is in /etc/asterisk/manager.conf it is not your “allstar password from the nodes page”

3

Have you read the manual on this topic?

The AMI password(s) are what are defined in /etc/asterisk/manager.conf. If you change the password there, you have to change the password in EVERY application that is using the AMI connection - Allmon3, Supermon, AllScan, etc. They all have to match and everything that is a service (asterisk, allmon3) must be restarted for the password to take effect.

AllStarLink v3 takes security seriously because many people put these directly on the Internet, which is reasonable. But we aren't going to make compromises that will turn ASL servers into easy targets for attackers. Watch the logs for the SSH port of a device connected to the Internet and you'll be shocked at how fast and furious the login attempts are.

4

I appreciate the security, which is why I am switching to ASL3…And yes, the linux log … check this one out… “Connection closed by authenticating user root 159.65.8.74 port 56616.” This is the usual type hitting my HV node… 115.135.235.61

5

You can also install and enable fail2ban on an ASL3 node to auto-deflect attacks. That's fully-supportable with ASL3's images too.

6

That sounds interesting!! Thanks! (I will probably lock myself out!)

7

Generically, I would do a few other checks and be sure that the manager.conf file

1- does not have the port or user/pass commented out.

2- That the port is correct and open in the firewall.

3- if you used bindaddress, make sure it covers the IP of that which is accessing.

or just use 0.0.0.0 for testing.

You can have multiple bindaddress for being multi specific.

127.0.0.1 is the local machine only.

Where it is loaded and where it is being accessed from not often the same.

8

Thank you for the help and suggestions!!! I have resolved the problem for the time being. Quickly, I could create an ASL node via the Ham Crusader way. Everything worked including Allmon3… the I added Supermon and it worked, BUT going back to allmon3, it didn’t work.. I could log in but no connections. So, for now, I ignore allmon3 and use my trusty Supermon!!! I will figure out the problem with the AMI password, probably by making ALL my passwords 12 characters, with a non-repeating cussword in there… Thanks everyone!! NH6FU

9

AMI- Asterisk Manager Interface Password

Created during the installation of ASL3. It is an alphanumeric password used to connect to the Asterisk interface!!! It is located in the manager.conf file. (in HV, the node password was in that file and position). The AMI can be changed, but I have not found ANY reason to change it, nor is it a password that is used by a USER, such as the Allmon3, Supermon or Allscan web interfaces logins. I am going to leave it alone as I do have a place in asl-menu to view the password. Correct???