You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if this is expected to work, but I tried with "-i eth1" and I get "Failed to parse the acceptor's internet address". It would be convenient if it could resolve iface name -> ip address.
Currently local address is set in bt.runtime.Config#acceptorAddress. It's used for:
binding an incoming connections acceptor
establishing outgoing peer connections
http tracker requests
udp tracker requests
binding DHT agent
Maybe we could provide a more sophisticated configuration, that would allow to specify a list of rules: internet addresses, address + network mask pairs, interface names, plus optionally the preferred address family.
Regarding the address selection algorithm, there are two possible implementations:
Compile the list of rules to a java.function.Predicate<InetAddress> and use it to filter and select one appropriate address from those, that are available on the host. See DHTConfiguration in mldht and the corresponding issue for inspiration.
Use the list of rules to traverse available addresses and select the first match. I personally prefer this one, despite it being O(mn) instead of O(n).
The text was updated successfully, but these errors were encountered:
From #20:
Currently local address is set in
bt.runtime.Config#acceptorAddress
. It's used for:Maybe we could provide a more sophisticated configuration, that would allow to specify a list of rules: internet addresses, address + network mask pairs, interface names, plus optionally the preferred address family.
Regarding the address selection algorithm, there are two possible implementations:
java.function.Predicate<InetAddress>
and use it to filter and select one appropriate address from those, that are available on the host. See DHTConfiguration in mldht and the corresponding issue for inspiration.The text was updated successfully, but these errors were encountered: