Parallel logging


Bob
 

Now I see the problem. It appears that WinSock.LocalIP returns the first first Local IP it sees. In my case I have only a single adaptor, so I never noticed the discrepancy. I will remove the LocakIP menu item. SeventyThree(s).

On 06/05/2022 6:09 AM DamianM0BKV via groups.io <kammdp@...> wrote:


Hi Bob, 4 pictures from the 2 PCs. The top 2 are from my main PC with the Setup parallel logging IP Address I enter relating to the 2nd PC wireless LAN. In the lower row are pictures from my 2nd PC with the Set up Parallel logging window showing the main PC's wireless LAN that I enter. You can see that in both cases the TCP event viewers config window shows the PC's local IP address from its Ethernet Adapter and not the Wireless LAN that is being used.

Perhaps it's something I'm doing wrong. All is working correctly only the TCP event viewer showing the incorrect local IP address. I was asking if the correct wireless IP address could be shown. 73 Damian




DamianM0BKV
 

oops just noticed the Port number 52003 on my 2nd PC changed back to 52001 overnight. Can this happen without my intervention?
Again 73 Damian


DamianM0BKV
 

Hi Bob, 4 pictures from the 2 PCs. The top 2 are from my main PC with the Setup parallel logging IP Address I enter relating to the 2nd PC wireless LAN. In the lower row are pictures from my 2nd PC with the Set up Parallel logging window showing the main PC's wireless LAN that I enter. You can see that in both cases the TCP event viewers config window shows the PC's local IP address from its Ethernet Adapter and not the Wireless LAN that is being used.

Perhaps it's something I'm doing wrong. All is working correctly only the TCP event viewer showing the incorrect local IP address. I was asking if the correct wireless IP address could be shown. 73 Damian




Bob
 

The event viewer shows this (on my wireless LAN setup). What is you want, and why? SeventyThree(s).


On 06/04/2022 5:56 PM DamianM0BKV via groups.io <kammdp@...> wrote:



Hi thanks Bob, all understood about TCP and the loopback IP address. I'm still interested to know if the wireless local IP address, if in use, can be the local IP address in the TCP event viewer Config window.
Thanks again, 73, Damian


DamianM0BKV
 



Hi thanks Bob, all understood about TCP and the loopback IP address. I'm still interested to know if the wireless local IP address, if in use, can be the local IP address in the TCP event viewer Config window.
Thanks again, 73, Damian
 


Bob
 

The TCP server socket is bound to the localhost address 127.0.0.1. When parallel logging is enabled and a QSO is logged/modified/deleted, the socket is momentarily bound to the IP address of another PC. Then, when the parallel logging request is completed, the socket is again bound to the local host address. SeventyThree(s).

On 06/04/2022 6:40 AM DamianM0BKV via groups.io <kammdp@...> wrote:


Is it possible in the 'TCP event viewer' window to replace the Local IP Address from the Ethernet cable connection IP Address that both my PCs ALWAYS are showing with the wireless connection IP Addresses that are in use?  I use Wireless on both PCs (I couldn't get the Ethernet link for TCP to work for my main PC and only use wireless for the 2nd PC). Because I'm not using Ethernet connection cables to check out or change the IP Address in the 'Setup parallel logging' window it means going to 'search' on the Windows toolbar and doing a command prompt (CMD) followed by ipconfig to find it in a DOS window.

Also, it says in the manual p633 "Mouseover the TCP panel for an informational pop-up showing the IP address and TCP port number" but this IP address is the loopback address, 127.0.0.1, which I think is standard with windows. What would be helpful is to know the Local IP Address in use without going to the TCP event viewer window.
73 Damian


DamianM0BKV
 

Is it possible in the 'TCP event viewer' window to replace the Local IP Address from the Ethernet cable connection IP Address that both my PCs ALWAYS are showing with the wireless connection IP Addresses that are in use?  I use Wireless on both PCs (I couldn't get the Ethernet link for TCP to work for my main PC and only use wireless for the 2nd PC). Because I'm not using Ethernet connection cables to check out or change the IP Address in the 'Setup parallel logging' window it means going to 'search' on the Windows toolbar and doing a command prompt (CMD) followed by ipconfig to find it in a DOS window.

Also, it says in the manual p633 "Mouseover the TCP panel for an informational pop-up showing the IP address and TCP port number" but this IP address is the loopback address, 127.0.0.1, which I think is standard with windows. What would be helpful is to know the Local IP Address in use without going to the TCP event viewer window.
73 Damian


DamianM0BKV
 

Hi I managed to get the, very clever, Parallel logging module working after a few hours of struggling and it's working fine. There were a few problems the first being the IP address it showed me to use (I92.168.0.100) on my main home PC was for the Ethenet cable connection and on the remote laptop was for àn ethernet cable connection which wasn't plugged in. By doing a CMD and then ipconfig in the DOS window using the Search feature (both PCs Windows 10 platforms) I found the IP addresses for the wireless connections which worked ok. I've tried to use the ethernet cable connection since on my main PC but it doesn't work only a wireless network works. The window showing the IP address and Port (that can be changed) always shows the Ethenet IP addresss on both PCs which doesn't work so I have to do a CMD in the search box and then ipconfig to find the correct IP address to use each time I power up the PC. I should be able to change this from DHCP to a static IP address hopefully without problems. 
Another small problem is if the remote PC sends a logged qso to the main PC (all though it's not normally used for that) the main PC logged it then sends a copy back to the remote PC which puts it in the log a second time. Not sure if my settings cause this.
Apart from this there was a couple of things in the manual that confused me. The reference to the 127.0.0.1 IP address directed me the wrong way initially. It's prominence when checking the TCP tab on the bottom row also added to this confusion. Call me a donkey for this. Thanks for this great software extra. BTW version 294 in use on both PCs.
73 Damian