1.7 KiB
Opened 7 years ago
Last modified 5 years ago
#1188openenhancement
Check for OBEP/IBGW transport compatibility
Reported by:zzzOwned by: Priority: minor Milestone: eventually Component: router/general Version: 0.9.10 Keywords: performance peer-selection Cc: orignal Parent Tickets:
Sensitive: no
Description
orignal@freenode I notice one thing. When you pick you outbound tunnel and party's inbound tunnel do you check if endpoint and gateway are able to talk each other?
no, we do not check for compatibility, that's a great idea, I will enter a trac ticket for that!
A compatibility check would look for common transports and common address types IPv4/v6.
In OCMOSJ. Also when storing our RI to ffs in StoreJob?. Anyplace else? Probably need a common compatibility-check class/method. But for the outbound direction, this isn't straightforward as we have two degrees of freedom, OBEP and IBGW.
Note that lack of advertisement of an address does not necessarily mean lack of support for outbound, but we can't make assumptions (e.g. i2pcpp and i2pd).
Not so easy.