@eyedeekay
&eche|on
&zzz
+FreefallHeavens
+R4SAS
+RN_
+Romster
+T3s|4
+acetone
+cims
+eche|off
+hagen
+mareki2p
+mesh
+nilbog
+nyaa2pguy
+orignal
+postman
+qend-irc2p
+red
+snex
+wodencafe
Arch
Danny
Holmes
Irc2PGuest28384
Irc2PGuest84270
Irc2PGuest92627
NiceBoat_
OfficialCIA_
Onn4l7h
Onn4|7h
Over1
SilentWave
Sleepy
T3s|4_
U1F642
Wikk_0
Zapek
aargh4
ac9f
ahiru
anontor
dr4wd3
duanin2
eyedeekay_
eyedeekay_bnc
ice_juice
leopold
mahlay
makoto
n2
not_bob_afk2
poriori
profetikla
r00tobo
rapidash
test3847473
thetia
uop23ip
urist_
utp
vivid_reader56
x74a6
zelgomer
cims
Okay, did more research today
cims
Seems the issue lies here:
cims
1. If we only support ratchet, and peer to lookup is not in our netDB, then we use expl. tunnel to receive our responses
cims
2. We receive a reply from expl. tunnel, and lease set goes into main netDB
cims
3. There seems to be no mechanism to migrate this result to client netDB
cims
4. Client netDB query fails
cims
Maybe we should make ratchet and ElG maintain the same behavior, which uses client tunnel to receive responses even if we have no peer RI available
cims
Or try peers with RI first
cims
Any ideas?
zzz
thanks for the info cims, it's on my list