| commit | c5d4a9b008b84009ba24ff42624896b01876ecef | |
| author | upstream svn <svn@amule.org> | |
| Fri, 10 Sep 2010 21:27:11 +0000 (10 21:27 +0000) | ||
| committer | Dévai Tamás <gonosztopi@amule.org> | |
| Fri, 10 Sep 2010 21:37:02 +0000 (10 21:37 +0000) | ||
| tree | 49e33873e15008ec048b5d5f2c6db1d6b98b27da | treesnapshot (tar.gz zip) |
| parent | 31298f2bdc6f5e8f7dc88ec71b91370b31d52989 | commitdiff |
Change Kad to work better in small LANs
If Kad detects it is running on a LAN (only LAN IPs in the routing table), it
will assume being open and not behind a NAT/Router without trying to verify
(which would fail in a small LAN), and also doesn't enforce several security
features like flood detection for LAN IPs. Now even a small Kad LAN of 2 nodes
works well without any setup issues.
To create such a Kad LAN, make sure all clients have Preferences->Security->
"Always filter LAN IPs" disabled, delete the existing nodes.dat if necessary,
go to the Kad dialog and enter the IP+Port of one other client (which is either
connected or in connecting mode for Kad) to the bootstrap box.
If Kad detects it is running on a LAN (only LAN IPs in the routing table), it
will assume being open and not behind a NAT/Router without trying to verify
(which would fail in a small LAN), and also doesn't enforce several security
features like flood detection for LAN IPs. Now even a small Kad LAN of 2 nodes
works well without any setup issues.
To create such a Kad LAN, make sure all clients have Preferences->Security->
"Always filter LAN IPs" disabled, delete the existing nodes.dat if necessary,
go to the Kad dialog and enter the IP+Port of one other client (which is either
connected or in connecting mode for Kad) to the bootstrap box.
22 files changed: