Good Afternoon group, Just curious if there is a log file I can look at to see who is connecting to my node?
Someone keeps connecting the Canada Hub 51730 to my node and Leaving it connected to my node and not disconnecting it after they are done. I tired to black list Node 51730 but it did not seem to work, I found the information on the WiKi page to be very vague on how to black list. I thought I did it correctly but since the node was still able to connect I guess something is not right.
OK finally figured out the blacklist part, as I said earlier WiKi is very vague on itâs explanation on how to implement it.
Still need to know if there is a log file that shows who is connecting this node to my node though, is there a log file that shows connecting stations?
You can log QSO activity on the node by enabling the archivedir=/path/to/some/location argument within specific node(s) within your rpt.conf file. This will log activity to a daily file of node activity in TXT form, but it also dumps WAVs for each node keydown⊠which fills up and will eventually kill your SD CardâŠ
Disclaimer: This fills up disks fast and will KILL SD CARDS.
Donât use this unless you have a need/want to, and donât leave it turned on long if youâre running the sequences on a Pi node.
If you have a hardware/virtual machine Hub node with a bigger normal disk, try running there and staying âlinkedâ to the Pi node experiencing trouble.
It is possible to make a ram disk to receive those file and then run a bash script every minute the rm .wav from that ram disk. that way you are left with only the txt file that wont take much place.
You can log QSO activity on the node by enabling the archivedir=/path/to/some/location argument within specific node(s) within your rpt.conf file. This will log activity to a daily file of node activity in TXT form, but it also dumps WAVs for each node keydown⊠which fills up and will eventually kill your SD CardâŠ
Disclaimer: This fills up disks fast and will KILL SD CARDS.
Donât use this unless you have a need/want to, and donât leave it turned on long if youâre running the sequences on a Pi node.
If you have a hardware/virtual machine Hub node with a bigger normal disk, try running there and staying âlinkedâ to the Pi node experiencing trouble.
It is possible to make a ram disk to receive those file and then run a bash script every minute the rm .wav from that ram disk. that way you are left with only the txt file that wont take much place.
Just a thought⊠You can log QSO activity on the node by enabling the archivedir=/path/to/some/location argument within specific node(s) within your rpt.conf file. This will log activity to a daily file of node activity in TXT form, but it also dumps WAVs for each node keydown⊠which fills up and wâŠ
Both are good points. I wouldnât be surprised if the mere overhead of logging/writing the WAVs adds some skipping to node audio. I only log QSOs on beefier Hub nodes, so wouldnât know or notice it.
Any chance there is a way to log TXT without writing the soundfiles at all? The two rpt config arguments (archivedir=/path/ and archiveaudio=x) seem to hint there is way to not have to log both at once? When I last tried to only log TXT with =/path/ on archivedir and =0 on archiveaudio, seems I could only get ASL to both log txt and wav, or nothing at all.
When I was looking at the Wiki instructions it never clicked in about managing via Asterisk CLI commands.
Maybe just add a line in there that refers to logging in to node and log in as âsudo -sâ and running the command âasterisk -rvvvâ to get to the CLI prompt.
I know it may seem like too much but I am no expert in linix but I am learning and I never thought about that even though I use it quite often for troubleshooting. Like Dahhhh
Thank You all for the comments, I will give some of those a try and Using an external USB drive for storage sounds good as I am using a pi 3B+.
Question though, what would happen if the thumb drive filled up? Hmmmm, would the system still crash?
I personally have not had an issue with audio dropouts recording to usb mounted drive. As for the drive filling up? Iâd recommend a large 256Gb drive and a cron job to delete files older than X days
I setup the Canada Hub (node 51730) a couple of weeks ago so though I would help answer your question as best I can. I set it up so Canadian ham operators had a place to meet and talk about things of common interest, similar to hubs in the UK, US, and Australia.
Like much of AllStar, I canât control who connects to whom, but like you, I believe I can block inbound requests from certain nodes and I set that up this morning for a couple of repeaters that are not configured well for AllStar and send IDs and hangtimes etc over the WAN. I found your post as a result of looking up how to do it this morning!
I will let some of our more active users know that you donât want to be part of the network and encourage them to remember not to connect to you because they may do that from their local node which may be connected to the Canada Hub.
From my monitoring of the system it seems several hams are connecting nodes they find in the public database and leaving them connected in hopes of hearing some activity and striking up a QSO. It seems the repeaters in Canada are very quiet for the most part as sometimes we have over 100 repeaters connected and no activity for an hour or more!
What I believe you need to do is block node 51730 which appears to be where the connections are mostly coming from into your node (by the way, consider setting up Allmon, it will tell you this and is very easy to setup and fun to watch).
BTW - I just initiated a connect to your node from 51730 and it connected, so I think you arenât quite there yet.
Feel free to call me on node 450521 and we can test together or send an email to my callsign @ arrl.net and we can connect on the phone after that.
Otherwise, I do hope you will consider connecting once in a while and saying hello. I worked in the maritimes in telecommunications for quite a while and always enjoy talking with VE1s and VO1s whenever possible. We have operators from Newfoundland to BC and are trying to also get the Yukon and Northwest Territories on the network so we can talk from coast to coast to coast.
| 
ve1jcs:
| 
| 