Callsign locator

User avatar
KD0ZV
Log4OM Alpha Team
Posts: 733
Joined: 04 Mar 2015, 13:42
Location: Ankeny, Iowa
Contact:

Re: Callsign locator

Post by KD0ZV »

OK good info Juergen

I just had not ran across that before.

Rich
73,
Rich
KD0ZV
Log4OM Alpha Team
User avatar
KD0ZV
Log4OM Alpha Team
Posts: 733
Joined: 04 Mar 2015, 13:42
Location: Ankeny, Iowa
Contact:

Re: Callsign locator

Post by KD0ZV »

Just noticed all US spots are EM19 in cluster
73,
Rich
KD0ZV
Log4OM Alpha Team
User avatar
HB9VQQ
Old Man
Posts: 237
Joined: 16 Jan 2020, 21:19
Location: Switzerland
Contact:

Re: Callsign locator

Post by HB9VQQ »

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 ?
Flex 6600 - Spiderbeam
User avatar
KD0ZV
Log4OM Alpha Team
Posts: 733
Joined: 04 Mar 2015, 13:42
Location: Ankeny, Iowa
Contact:

Re: Callsign locator

Post by KD0ZV »

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.
Attachments
2020-02-02_11-47-41.jpg
2020-02-02_11-47-41.jpg (161.45 KiB) Viewed 4072 times
73,
Rich
KD0ZV
Log4OM Alpha Team
User avatar
HB9VQQ
Old Man
Posts: 237
Joined: 16 Jan 2020, 21:19
Location: Switzerland
Contact:

Re: Callsign locator

Post by HB9VQQ »

I mean you said you could duplicate the issue as well?
Yes same issue
Flex 6600 - Spiderbeam
User avatar
KD0ZV
Log4OM Alpha Team
Posts: 733
Joined: 04 Mar 2015, 13:42
Location: Ankeny, Iowa
Contact:

Re: Callsign locator

Post by KD0ZV »

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
73,
Rich
KD0ZV
Log4OM Alpha Team
User avatar
HB9VQQ
Old Man
Posts: 237
Joined: 16 Jan 2020, 21:19
Location: Switzerland
Contact:

Re: Callsign locator

Post by HB9VQQ »

OK well hopefully the powers to be will check into this.
I am pretty sure it is resolved locally.

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.

Unbenannt.JPG
Unbenannt.JPG (32 KiB) Viewed 4055 times

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
User avatar
NN7D
Log4OM Alpha Team
Posts: 816
Joined: 19 Feb 2014, 19:44

Re: Callsign locator

Post by NN7D »

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 - NN7D
Gig Harbor, WA, USA
User avatar
HB9VQQ
Old Man
Posts: 237
Joined: 16 Jan 2020, 21:19
Location: Switzerland
Contact:

Re: Callsign locator

Post by HB9VQQ »

Could it be the grid is the center of the country, default sort of thing, when no grid for external lookup is found?
Good point, but locator is the same no matter if off- or online. For my callsign it reports JN46 instead of JN47.
Flex 6600 - Spiderbeam
User avatar
NN7D
Log4OM Alpha Team
Posts: 816
Joined: 19 Feb 2014, 19:44

Re: Callsign locator

Post by NN7D »

Good one!

I can replicate this. I'll ask Danielle the source of the Cluster "Callsign Locator" data.

Doug - W7DRM
Doug - NN7D
Gig Harbor, WA, USA
Post Reply