OK good info Juergen
I just had not ran across that before.
Rich
Callsign locator
Re: Callsign locator
73,
Rich
KD0ZV
Log4OM Alpha Team
Rich
KD0ZV
Log4OM Alpha Team
Re: Callsign locator
I was firing up my network analyzer (wireshark) to trace the destination for the grid lookups, since I could not find any network activity during a new spot entry I started another debugging tool where I can capture network traffic from a specific windows process (L4ONG.exe) on my local computer. Again no network traces at all during an entrance of a new cluster spot.
Can it be that the grid info (Callsign Locator) in cluster window is locally resolved ?
Can it be that the grid info (Callsign Locator) in cluster window is locally resolved ?
Flex 6600 - Spiderbeam
Re: Callsign locator
Cant think of anything that could resolve it locally.
I mean you said you could duplicate the issue as well?
Your grid is close (Spot Sim) but not right.
I mean you said you could duplicate the issue as well?
Your grid is close (Spot Sim) but not right.
- Attachments
-
- 2020-02-02_11-47-41.jpg (161.45 KiB) Viewed 4072 times
73,
Rich
KD0ZV
Log4OM Alpha Team
Rich
KD0ZV
Log4OM Alpha Team
Re: Callsign locator
Yes same issueI mean you said you could duplicate the issue as well?
Flex 6600 - Spiderbeam
Re: Callsign locator
OK well hopefully the powers to be will check into this.
On another note, modem showed up and I now have the ability to use port 23 again. So all good there
Thanks for your help.
Rich
On another note, modem showed up and I now have the ability to use port 23 again. So all good there
Thanks for your help.
Rich
73,
Rich
KD0ZV
Log4OM Alpha Team
Rich
KD0ZV
Log4OM Alpha Team
Re: Callsign locator
I am pretty sure it is resolved locally.OK well hopefully the powers to be will check into this.
For a test I reconfigured my Internet Firewall to drop all traffic except port 23. Then I simulated a spot and I am still seeing wrong Callsign Locators in the cluster window. I captured Cluster traffic (Port 23) with wireshark to make sure there is no locator information in the Cluster data.
So the PC running Log4OM without any Internet connection (except port 23/VE7CC) still showing Callsign Locators leads to the conclusion that grid information for Callsign Locators must resolve locally in cluster window.
Flex 6600 - Spiderbeam
Re: Callsign locator
Could it be the grid is the center of the country, default sort of thing, when no grid for external lookup is found?
Doug - W7DRM
Doug - W7DRM
Doug - NN7D
Gig Harbor, WA, USA
Gig Harbor, WA, USA
Re: Callsign locator
Good point, but locator is the same no matter if off- or online. For my callsign it reports JN46 instead of JN47.Could it be the grid is the center of the country, default sort of thing, when no grid for external lookup is found?
Flex 6600 - Spiderbeam
Re: Callsign locator
Good one!
I can replicate this. I'll ask Danielle the source of the Cluster "Callsign Locator" data.
Doug - W7DRM
I can replicate this. I'll ask Danielle the source of the Cluster "Callsign Locator" data.
Doug - W7DRM
Doug - NN7D
Gig Harbor, WA, USA
Gig Harbor, WA, USA