an alternative to HBRI that doesn't require a separate extension: 1) hubs send I6 and I4 fields in their hub INF to indicates the IP addresses they are listening on. this step may not even be required if the "alternate" IP of the hub is available by other means (DNS record, hub list...).
2) upon receiving the initial hub INF, clients that wish to be available on both IPv6 & IPv4 networks can then connect to either the hub's I6 or the hub's I4 (obviously they would pick the one they are not already connected to). the client then goes through the regular login process in order for the hub to associate the client's IPv6 address to its IPv4 address. the additional connection is then cut. 3) after a successful verification of a client's "alternate" IP, the hub adds that information to the client's INF and updates it so other users are notified of it. 4) when a user wants to connect to another user, it can: - connect only to its IPv6 address if an I6 is present in that user's INF. - connect only to its IPv4 address if an I4 is present in that user's INF. - connect to both if both are present, then discard the one that didn't connect first. -- 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
