NebuAD, Inc blocked every 4 minutes

[Santilli]

Source 192.168.1.51:9001
Destination 66.151.151.20:5062
Protocol UDP
Action Blocked
Peerblock 1.1

I guess it's blocked, but, I can't help but wonder why I'm getting this constant attack.

Any ideas?

 

[Santilli]

traceroute to 192.168.1.51 (192.168.1.51), 30 hops max, 40 byte packets
1 192.168.1.51 (192.168.1.51) 7.373 ms 0.989 ms 0.938 ms
Trace complete

PING 192.168.1.51 (192.168.1.51): 56 data bytes
64 bytes from 192.168.1.51: icmp_seq=0 ttl=128 time=5.8 ms
64 bytes from 192.168.1.51: icmp_seq=1 ttl=128 time=10.6 ms
64 bytes from 192.168.1.51: icmp_seq=2 ttl=128 time=1.0 ms
64 bytes from 192.168.1.51: icmp_seq=3 ttl=128 time=1.3 ms
64 bytes from 192.168.1.51: icmp_seq=4 ttl=128 time=1.0 ms
64 bytes from 192.168.1.51: icmp_seq=5 ttl=128 time=5.0 ms
64 bytes from 192.168.1.51: icmp_seq=6 ttl=128 time=1.3 ms
64 bytes from 192.168.1.51: icmp_seq=7 ttl=128 time=1.3 ms
64 bytes from 192.168.1.51: icmp_seq=8 ttl=128 time=1.4 ms
64 bytes from 192.168.1.51: icmp_seq=9 ttl=128 time=1.6 ms
--- 192.168.1.51 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 1.0/3.0/10.6 ms

PING 66.151.151.20 (66.151.151.20): 56 data bytes
64 bytes from 66.151.151.20: icmp_seq=0 ttl=52 time=16.2 ms
64 bytes from 66.151.151.20: icmp_seq=1 ttl=52 time=29.4 ms
64 bytes from 66.151.151.20: icmp_seq=2 ttl=52 time=18.1 ms
64 bytes from 66.151.151.20: icmp_seq=3 ttl=52 time=16.3 ms
64 bytes from 66.151.151.20: icmp_seq=4 ttl=52 time=15.8 ms
64 bytes from 66.151.151.20: icmp_seq=5 ttl=52 time=15.6 ms
64 bytes from 66.151.151.20: icmp_seq=6 ttl=52 time=34.9 ms
64 bytes from 66.151.151.20: icmp_seq=7 ttl=52 time=18.1 ms
64 bytes from 66.151.151.20: icmp_seq=8 ttl=52 time=15.8 ms
64 bytes from 66.151.151.20: icmp_seq=9 ttl=52 time=11.2 ms
--- 66.151.151.20 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 11.2/19.1/34.9 ms

 

[ddrueding]

http://gregwilde.com/notepress/?p=92

If you use PeerGuardian 2 (PG2) and Logitech Vid, you will notice that PG2 blocks NebuAd, Inc at 66.151.151.20:5062. It turns out that this IP address actually belongs to SightSpeed, Inc. Logitech bought SightSpeed on Oct 29, 2008. Because of the nature of the videoconferencing service provided by SightSpeed, one can see that it is necessary for the workstation to check in with a SightSpeed server on a regular basis in order to be able to answer in incoming video call. That’s because most firewalls are configured to block incoming protocols and ports except responses to outgoing http, https, ftp, etc requests.
So far I can’t see an advantage of Vid over Skype.
If anyone knows why PG2 would associate NebuAd (now defunct) with SightSpeed, please leave a comment.
Also, If you see any significant advantage of SightSpeed/”Logitech Vid” over Skype, please leave a comment.

 

[Santilli]

Thanks David. I did a bunch of research, and didn't find that answer. I just uninstalled
the Logitech program, and, the constant sending is over.

Thanks again.

GS

PS it really didn't make much sense, since if the NebuAD hardware was in place at Astound, it would have been hitting my server as well as The Beast, which it was not.

 

[ddrueding]

For the record, I found it by Googling the IP address (66.151.1.51)

 

[Santilli]

I tried the IP address, but, I thought it would be easier to find the port number, and block it. I was wrong.