<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title></title>
</head>
<body>
<div name="messageBodySection">
<div dir="auto"><span style="font-size: 16px">I can confirm that with 562, I can now search for spots generated locally and they appear. </span><span style="font-size: 16px"><br /></span><span style="font-size: 16px"><br /></span><span style="font-size: 16px">I’ve not tested announcements.</span><span style="font-size: 16px"><br /></span><span style="font-size: 16px"><br /></span><span style="font-size: 16px">Thanks Dirk.</span><span style="font-size: 16px"><br /></span><span style="font-size: 16px"><br /></span><span style="font-size: 16px">73 Keith G6NHU</span><span style="font-size: 16px"><br /></span><span style="font-size: 16px"><br /></span></div>
</div>
<div name="messageReplySection">On 31 Jan 2025 at 14:17 +0000, Dirk Koopman via Dxspider-support <dxspider-support@tobit.co.uk>, wrote:<br />
<blockquote type="cite" style="border-left-color: grey; border-left-width: thin; border-left-style: solid; margin: 5px 5px;padding-left: 10px;"><font size="4">Normal service is a bit tardy as I had a late night rescuing my other half from a broken down car and did not get to bed until 3am.<br />
<br />
I have looked a number of versions from 536 to 561. And I remain confused.<br />
<br />
Firstly 536 stores the spot and also sends it back to a telnet console:<br />
<br />
<font face="monospace">dx 3505 g1brn test 4<br />
DX de G1TLH: 3505.0 G1BRN test 4 1248Z<br /></font><br />
On 561 the same is true<br />
<br />
<font face="monospace">dx 7013 g1brn test 5<br />
DX de G1TLH: 7013.0 G1BRN test 5 1252Z<br />
G1TLH de GB7TLH 31-Jan-2025 1252Z dxspider ><br />
<br /></font> These spots have also been sent out to other nodes and should be searchable with a <font face="monospace">sh/dx 2 g1brn</font>.<br />
<br />
The line that sent the spot back to the user in user format had been removed and has now been put back again, but will be moved slightly in the next release (soon today). But it clearly was a bodge that was not necessary in (waves hand randomly) earlier versions. This will be fixed after this weekend.<br />
<br />
As for announcements - as well a few other things - this was a consequence of me not thinking through (mainly because it seemed too difficult to test) the defences I added to prevent nodes that had not fully initialised (e.g. the ungodly attempting fraud but also CC Cluster instances [nominally godly]) passing traffic. This is now fixed. <br />
<br />
I cannot reproduce errors viz: CCCluster connection on the 'links' command:<br />
<br />
<font face="monospace">link<br />
Ave Obs Ping Next Filters<br />
Callsign Type Started Uptime RTT Count Int. Ping Iso? In Out PC92? Address<br />
GB7DJK DXSP 31-Jan-2025 1347Z 6m 1s 0.03 2 300 92 Y 163.172.11.79<br />
VE7CC-1 CCCL 31-Jan-2025 1353Z 3s 999.00 2 300 296 Y 207.216.236.158<br /></font><br />
I have added an extra field to the 'who' command to indicate the 'state' of that connection.<br />
<br />
<font face="monospace">who<br />
Callsign Type State Started Name Ave RTT Link<br />
G1TLH-2 USER LOCL prompt 31-Jan-2025 1346Z Dirk 127.0.0.1<br />
GB7DJK NODE DXSP normal 31-Jan-2025 1347Z Dirk 0.03 163.172.11.79<br />
GB7TLH NODE DXSP indiffer 31-Jan-2025 1346Z Dirk<br />
VE7CC-1 NODE CCCL normal 31-Jan-2025 1353Z Node 0.16 207.216.236.158<br />
<br /></font> This version is now available from git.<br />
<br />
You will need to do a restart.<br />
<br />
73 Dirk G1TLH<br />
<font face="monospace"><br /></font></font>_______________________________________________<br />
Dxspider-support mailing list<br />
Dxspider-support@tobit.co.uk<br />
https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support<br /></blockquote>
</div>
</body>
</html>