&zzz
+FreefallHeavens
+R4SAS
+RN
+ReturningNovice
+StormyCloud
+T3s|4
+acetone
+cims
+eche|off
+fa
+mareki2p
+nilbog
+orignal
+postman
+psychopuck
+qend-irc2p
+rednode
+snex
+wodencafe
Arch
Danny
Irc2PGuest28384
Irc2PGuest66257
Irc2PGuest75631
Irc2PGuest81267
Onn4l7h
Onn4|7h
Over
Sisyphus_
Sleepy
T3s|4_
U1F642
Watson
Zapek
aargh4
ahiru
ananas
anontor
calamares
dr4wd3
duanin2
i2potus
ice_juice
justaperson
luvme
mahlay
makoto
marek22k
n2_
not_bob_afk
onon_
pinotto
poriori
profetikla
r00tobo
rapidash
test7363673
uop23ip
w8rabbit
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