2.0: Connection alert network IP address is always local router IP address

[nhojb]

In Lulu 2.0 the network IP address reported in the connection alert is always my local router (192.168.86.1). It's the same for all processes.

In Lulu 1.x the network IP address was the final destination IP address for the request.

[nhojb]

Note: this appears to apply to UDP connections only. I may be betraying my network protocol ignorance here...

[objective-see]

Is this just for DNS requests? (UDP, port 53)? Or

If you have a screenshot of the alert next time this happens, that'd be great!

thanks!

[nhojb]

Yes, UDP, port 53. That makes sense now, thanks :-)

[Autre31415]

I'm also seeing this issue specifically in 2.0. Here's an example:

In 1.x it would show the resolved domain.

[ctwise]

Can the message be improved then? DNS lookup for x.com. Allowing this gives the application access to the Internet.

[MacInTheNet]

If you select the remote endpoint with the first DNS request, the second time it shows the real IP :)

[alexcom]

Does LuLu really have to report DNS lookups? Why not just report real connection attempts and ignore preliminary actions? Maybe it makes sense to add a checkbox "Always allow DNS lookups" or to be little more restrictive and add a configurable list of DNS servers connections to which LuLu should not report?