We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
We wish to block all UDP fragments from entering our network.
We wish to block all UDP fragments from entering our network. Dropbox LAN sync uses UDP port 17500 for discovery but I need to know the IP address that Dropbox is using so I can add it to an excepti...
hanky wrote:We wish to block all UDP fragments from entering our network. ... but I need to know the IP address that Dropbox is using so I can add it to an exception list to allow UDP fragments through.
Hi hanky,
There is no need to handle in any special way Dropbox UDP packets. 🙂 You may block all of them since they never get in or out of your LAN (that's why LAN Sync); just don't prevent them to flow locally. The IP address in use is the same any other discovery service uses - your local broadcast address. 😉 That's it.
Hope this helps.
PS: local broadcast address: Let's say your machine IP address is 192.168.0.10/24 (e.g. IP mask 255.255.255.0). In such a case your discovery/broadcast IP address is 192.168.0.255 if you need it at all. Simple, right?! 😜
hanky wrote:We wish to block all UDP fragments from entering our network. ... but I need to know the IP address that Dropbox is using so I can add it to an exception list to allow UDP fragments through.
Hi hanky,
There is no need to handle in any special way Dropbox UDP packets. 🙂 You may block all of them since they never get in or out of your LAN (that's why LAN Sync); just don't prevent them to flow locally. The IP address in use is the same any other discovery service uses - your local broadcast address. 😉 That's it.
Hope this helps.
PS: local broadcast address: Let's say your machine IP address is 192.168.0.10/24 (e.g. IP mask 255.255.255.0). In such a case your discovery/broadcast IP address is 192.168.0.255 if you need it at all. Simple, right?! 😜
