Echolink node blocking

1

I need to jump in on this - I have tried the blacklist with an Echolink node number (tried both with and without the 3 leading integer) but this doesn’t blacklist/block connections from the Echolink node in question.
So… Is there another method I need to use to blacklist an Echolink node connection?
Alan

1 Like
2

Actually the documentation at this url:
https://wiki.allstarlink.org/wiki/Blacklist_or_whitelist
has context=radio-secure commented out.
Surely you need to remove the comment to enable the radio-secure stanza?
Or are you replacing radio-secure with either black or whitelist?
In which case, Why do you eliminate the exten => line in radio-secure?
Alan

3

I am pretty sure ASL blacklist will not work with echolink.
Echolink has it’s own thats config’d in it’s asl config file.

Using ‘permit’ and ‘deny’
https://wiki.allstarlink.org/wiki/Echolink.conf_-_Echolink_Channel_Driver

4

Thanks Mike - found it and all good now - thanks for replying
Alan

1 Like
5

I took the liberty as marking this as solved for future discussion searches on the topic.
The issue comes around from time to time. It may help in not repeating the same info for some of us.

And for the record for all, the ASL White/Black-lists do only handle ASL network numbers.

6

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.