poy : your proposal misses the possibility to link the 2 connections to 1 unique client i think.
There can be more then 1 same ip4 or ip6 in the hub already. Nore the CID gives a uniquenes @ the moment of connecting to the second address there can be already same CID (other client) in the hub who then get a support he should not have ... Thats exactly why the HBRI is there , there it gives the hub the original's client connection's SID and tolken so it is sure its that client that gets the support for the second ip version. -- You received this bug notification because you are a member of Dcplusplus-team, which is a bug assignee. https://bugs.launchpad.net/bugs/309402 Title: ipv6 support Status in ADCH++: In Progress Status in DC++: In Progress Status in Linux DC++: Confirmed Status in StrongDC++: Fix Committed Bug description: Support for ipv6 as data transport and for client <-> hub communication should be added. As it looks like the ADC protocol already has ipv6 support, that shouldn't require too much work. To manage notifications about this bug go to: https://bugs.launchpad.net/adchpp/+bug/309402/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~linuxdcpp-team Post to : linuxdcpp-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~linuxdcpp-team More help : https://help.launchpad.net/ListHelp
