How to connect DXSpider to RBN: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 22: | Line 22: | ||
* * * * * start_connect('sk0mmr') unless connected('sk0mmr') | * * * * * start_connect('sk0mmr') unless connected('sk0mmr') | ||
* * * * * start_connect('sk1mmr') unless connected('sk1mmr') | * * * * * start_connect('sk1mmr') unless connected('sk1mmr') | ||
You can also startup the connections manually in the normal way: | |||
connect sk0mmr | |||
connect sk1mmr | |||
and of course drop the connections: | |||
disconnect sk0mmr | |||
disconnect sk1mmr | |||
Although bear in mind if you added the crontab entries, disconnecting them will only work until the crontab fire the next connect command, so you would need to remove or comment out the two lines in the crontab file to permanently disconnect. | |||
Revision as of 19:22, 19 February 2025
Configuring your DXSpider node receive skimmer spots from the RBN (Reverse Beacon Network) is very straight forward:
Create two connect scripts:
/spider/connect/sk0mmr
which contains:
connect telnet telnet.reversebeacon.net 7000 'call:' 'sk0mmr'
and:
/spider/connect/sk1mmr
which contains:
connect telnet telnet.reversebeacon.net 7001 'call:' 'sk1mmr'
Then in your crontab file:
/spider/local_cmd/crontab
Add these two lines:
* * * * * start_connect('sk0mmr') unless connected('sk0mmr')
* * * * * start_connect('sk1mmr') unless connected('sk1mmr')
You can also startup the connections manually in the normal way:
connect sk0mmr connect sk1mmr
and of course drop the connections:
disconnect sk0mmr disconnect sk1mmr
Although bear in mind if you added the crontab entries, disconnecting them will only work until the crontab fire the next connect command, so you would need to remove or comment out the two lines in the crontab file to permanently disconnect.