05-21-2016, 12:16 PM
Win10 Pro 64 bit. System info:
Java 1.8.0_51 (64 bit)
Oracle Corporation
SWT v4508, win32
Windows 8.1 v6.3, amd64
V5.7.2.0/4 az3
I suspect there is a bug/issue with IPv6 DHT banning all or most nodes. I always see a very high number of banned nodes. Every banned address I see is IPv6. This has been going on for months (including previous Vuze versions) so it isn't a new or temporary thing.
If I'm reading the statistics page correctly, there are 10 live IPv6 contacts ... and 48 banned addresses. It seems likely that something bad is going on with it being too quick to ban. Maybe because there are few IPv6 nodes, an individual pair of nodes tends to talk to each other more often, triggering the flood protection?
Example:
[18.05.2016 17:18:17] [DHT: Sender stored excessive entries at this node (global flood)] 2601:681:4000:3e36:540f:8d93:b3d7:e260 has been banned
[21.05.2016 02:38:29] [DHT: Sender stored excessive entries at this node (global flood)] 2a00:a580:10b2:e000:6dec:470d:dc27:30c5 has been banned
[16.05.2016 17:44:18] [DHT: Sender stored excessive entries at this node (global flood)] 2a01:240:fe00:8277:0:0:0:100 has been banned
[17.05.2016 07:03:00] [DHT: Sender stored excessive entries at this node (global flood)] 2001:980:1f31:1:ecb7:7f02:d8e1:b1bb has been banned
[15.05.2016 02:30:58] [DHT: Sender stored excessive entries at this node (global flood)] 2001:5c0:1400:b:0:0:0:312f has been banned
[15.05.2016 19:58:55] [DHT: Sender stored excessive entries at this node (global flood)] 2604:6000:1403:15e:7c0b:8925:e2d4:1785 has been banned
[20.05.2016 03:21:27] [DHT: Sender stored excessive entries at this node (global flood)] 2601:2c5:1:7ff2:718b:b2da:ac80:82cf has been banned
[21.05.2016 13:17:38] [DHT: Sender stored excessive entries at this node (global flood)] 2602:306:8b12:f560:593e:3c2f:dec1:1f07 has been banned
Java 1.8.0_51 (64 bit)
Oracle Corporation
SWT v4508, win32
Windows 8.1 v6.3, amd64
V5.7.2.0/4 az3
I suspect there is a bug/issue with IPv6 DHT banning all or most nodes. I always see a very high number of banned nodes. Every banned address I see is IPv6. This has been going on for months (including previous Vuze versions) so it isn't a new or temporary thing.
If I'm reading the statistics page correctly, there are 10 live IPv6 contacts ... and 48 banned addresses. It seems likely that something bad is going on with it being too quick to ban. Maybe because there are few IPv6 nodes, an individual pair of nodes tends to talk to each other more often, triggering the flood protection?
Example:
[18.05.2016 17:18:17] [DHT: Sender stored excessive entries at this node (global flood)] 2601:681:4000:3e36:540f:8d93:b3d7:e260 has been banned
[21.05.2016 02:38:29] [DHT: Sender stored excessive entries at this node (global flood)] 2a00:a580:10b2:e000:6dec:470d:dc27:30c5 has been banned
[16.05.2016 17:44:18] [DHT: Sender stored excessive entries at this node (global flood)] 2a01:240:fe00:8277:0:0:0:100 has been banned
[17.05.2016 07:03:00] [DHT: Sender stored excessive entries at this node (global flood)] 2001:980:1f31:1:ecb7:7f02:d8e1:b1bb has been banned
[15.05.2016 02:30:58] [DHT: Sender stored excessive entries at this node (global flood)] 2001:5c0:1400:b:0:0:0:312f has been banned
[15.05.2016 19:58:55] [DHT: Sender stored excessive entries at this node (global flood)] 2604:6000:1403:15e:7c0b:8925:e2d4:1785 has been banned
[20.05.2016 03:21:27] [DHT: Sender stored excessive entries at this node (global flood)] 2601:2c5:1:7ff2:718b:b2da:ac80:82cf has been banned
[21.05.2016 13:17:38] [DHT: Sender stored excessive entries at this node (global flood)] 2602:306:8b12:f560:593e:3c2f:dec1:1f07 has been banned