Had a weird situation come up on a friend's node. He's blind so either I or another friend take care of his node. The problem is that he keeps getting a connection from another station but not a node number, a callsign. Same as with repeaterphone but I know there are variations on that. I turned webtransceiver in the node settings at allstarlink.org, rebooted his Pi, this other station is immediately reconnected. So I am assuming the connect is inbound. How do I stop this other from connecting? In the past when someone connected our little network to some node with like 100 connections (east coast reflector???) I made a rpt.conf [nodes] entry pointing the offending node to 127.0.0.1 but in this case there is no node number.
GeorgeC W2DB 2360, 28599, 2428, 490891
In asl-menu, change the node to restricted access, then add the call sign (upper case, I don't remember if it converts lowercase to uppercase automatically or not to the disallow list.
73 from another Blind guy. I managed my own nodes and everything!
In the portal for that node's configuration disable WebTransceiver and Phone Portal. That will stop all app-based connections. That's why they come in as a Callsign and not a node number.
well that's exactly what I did, then restart asterisk but it still connects
GC
What is "it" in this case? It does take a few minutes for the setting change to propagate.
There are some clients that will connect anyway, in my experience, even with that switch disabled in the portal. M1KE I believe is one of those.
If M1KE is using WebTransceiver auth, it shouldn't be able to about 5 minutes or so after you uncheck that for the node. I think M1KE has a "node mode" which also uses a node number I don't think that'd appear as a callsign. It's not coming in as an Echolink node is it? But there isn't any other magical bypass unless you have something setup like a generic iaxrpt connection with a password.
It's been a while. I'll have to try it again, but I certainly remember being able to still connect to some of my own servers with M1KE in WT auth mode days after turning off that switch, which, as you say, shouldn't be possible.
Yes, M1KE also has the ability to connect as a node or a direct IAX connection. The problem with Node Mode on M1KE is that, when you switch profiles or modes, the node has to register again. Generally, it will try to connect as soon as you switch to a profile with a node registration, meaning depending on what node you are connecting to, it will sit there and attempt to connect, failing to do so for several minutes, until the remote node figures out that you are registered. WT doesn't have that problem, so most people use it by default, and Node Mode to connect to places where WT won't work.
"it" is/was the offending connection. Another person sent an email to this station and that must have done the trick, the connection went away. But I did find the restricted access enable and added that callsign. Still we are not sure what he connected with. But it appears resolved. and general info, the guy I'm helping likes to check into blind/handicapped nets, and one wasn't allowing him to connect because he had another connection (the guy we blacklisted)
So all appears to be working now
GeorgeC W2DB
The issue was our inability to make the connection go away. Restart asterisk and it would come back quickly
no, was not coming in on the echolink side, that would have shown a 3xxxxx node number, this just had a callsign