NAV blocked Port Scan, But No IP Info Provided

Archive
1

I received a notice from NAV that it had blocked an incoming portscan to my MAC computer (on 3 separate occassions).  Each time, the More Info dialogue box failed to show the IP address from which the attack occurred (it was blank).  How is this possible, even if the source used a third party intermediate?  All my previous attacks contained an IP address (either alpha or numerical).  What's going on?  Should I be concerned?

2

There's no cause for alarm. This issue is a bug that is caused when the IP address resolves to a hostname, but the hostname is too long to display, causing Mac OS X to truncate the entire string. Sorry for the problem.

3

Thank you for the timely and informative response.  This issue sounds like an easy fix for a future version of NAV.  Thanks.

4

I received a notice from NAV that it had blocked an incoming portscan to my MAC computer (on 3 separate occassions).  Each time, the More Info dialogue box failed to show the IP address from which the attack occurred (it was blank).  How is this possible, even if the source used a third party intermediate?  All my previous attacks contained an IP address (either alpha or numerical).  What's going on?  Should I be concerned?