I think you may be right.  Antivirus might also be interfering.  

It's also possible that this is a bug in LogViewPlus.  Binding to the loopback for the UDP port is strange.

My PC; AD joined Windows 10 Pro Build 1909 18363.778
I have now made sure LVP and packet sender are in firewall allowed apps
I have succesfully sent UDP packets from packet sender to packet sender ( 2 running instances) on my PC using both loop back and my local IPv4 addresses
I have now got LVP to respond when receiving a packet on 127.0.0.1
I have tested sending to my local IPv4 address. LVP does not respond as expected. 

How is LogViewPlus not behaving as expected?  Is it just not receiving the data when listening on the IPv4 address?

LVP is only bound to the loopback adapter - Can't be used for remote logging
Need to make sure that the LVP installer correctly adds itself to the Windows Firewall allowed  apps list

Ok - let me take closer look on my end and get back to you.

I don't think adding LogViewPlus to the list of allowed apps is something that we will do on install.  We are a small company and trust is an issue.  Also, this feature will not be needed by everyone.  However, we will highlight this issue in the application settings and documentation.  

Thanks Richard - I really appreciate you taking the time to investigate this one.  Sorry for the inconvenience.

Toby

No problem, Toby. Happy to help. I have been using LVP for a while now to help debug our ERP customisations and it has proved very useful.

Also can i add a feature request to also support a simple http listener with GET and POST support??

HTTP support a really good idea.  I will try and get this into the next release.

Thanks again Richard.  I will post back here when we have a beta release available.

Toby

Hi Richard,

We have just released LogViewPlus v2.4.41 as a BETA release available here: https://www.logviewplus.com/download.html

The problem seems to be that we were doing a poor job of selecting which network to listen on.  In v2.4.41, we solve this problem by listening across all available networks on the UDP port provided.  I believe that this is the correct thing to do in most situations and has the advantage of keeping the configuration simple.

Note however, that when I netstat on the process, the service was showing up as listing on the loopback address.  This is true, but it was also listening on for data from remote machines.  Just FYI.

Also, this release includes support for accessing log files via HTTP/S.  No configuration is necessary - just paste the URL into the 'Open File'  settings as the target file.  If your web page requires authentication, you can provided network credentials for the web request by configuring the HTTPS service.  You will find this in Settings -> Data Access -> Remote Servers.  This workflow is very similar to how SCP works.

If you have any questions or issues regarding the HTTPS feature, can you please start a new forum thread?  This thread is getting a bit long and I would like to keep the two issues separate if possible.

Hope that helps,

Toby