28-Dec-2015, 13:23
Easiest solution is to disable the firewall.
Unless you need it enabled (and you would know if you do), it doesn't actually protect you from anything, and just adds an extra layer of faulty software that adds latency and provides another attack surface, especially if you're using NAT (which most modern home internet connections do).
So, disable firewall and see if that helps.
If there's any setting to do with "broadcast domain" in "LAN setting", disable any "broadcast protection". Phantoms as well as many UPNP/DLNA appliances use local-network broadcast addresses to broadcast their messages (basically sending UDP packets to x.x.x.255 address, which is supposed to be seen by all hosts on same local network. In corporate networks with hundreds of hosts you break up broadcast domains to limit amount of (idle) traffic, but at home the main reason is to save power on wireless devices (which have to receive an process these broadcast messages). So many home routers do not forward broadcast packets to wifi endpoints. There is normally a setting to control that, though. This issue affects Phantoms, UPNP/DLNA, Apple AirPlay/Bonjour, SMB and other services, so enabling broadcast on wifi might solve some older problems you did not think had a solution
(not having to do with any phantom issues: if you're having any issues with p2p voice apps - whatsapp,skype,viber,googlevoice,facetime,hangouts etc - in router NAT settings, see if you can choose between "full-cone" and "symmetric/open" NAT, then choose "symmetric/open")
Unless you need it enabled (and you would know if you do), it doesn't actually protect you from anything, and just adds an extra layer of faulty software that adds latency and provides another attack surface, especially if you're using NAT (which most modern home internet connections do).
So, disable firewall and see if that helps.
If there's any setting to do with "broadcast domain" in "LAN setting", disable any "broadcast protection". Phantoms as well as many UPNP/DLNA appliances use local-network broadcast addresses to broadcast their messages (basically sending UDP packets to x.x.x.255 address, which is supposed to be seen by all hosts on same local network. In corporate networks with hundreds of hosts you break up broadcast domains to limit amount of (idle) traffic, but at home the main reason is to save power on wireless devices (which have to receive an process these broadcast messages). So many home routers do not forward broadcast packets to wifi endpoints. There is normally a setting to control that, though. This issue affects Phantoms, UPNP/DLNA, Apple AirPlay/Bonjour, SMB and other services, so enabling broadcast on wifi might solve some older problems you did not think had a solution
(not having to do with any phantom issues: if you're having any issues with p2p voice apps - whatsapp,skype,viber,googlevoice,facetime,hangouts etc - in router NAT settings, see if you can choose between "full-cone" and "symmetric/open" NAT, then choose "symmetric/open")
