&eche|on
&zzz
+R4SAS
+RN
+RN_
+StormyCloud
+acetone
+dr|z3d
+eche|off
+orignal
+postman
+snex
+wodencafe
Arch
BubbRubb
Danny
DeltaOreo
FreefallHeavens
Irc2PGuest16752
Irc2PGuest33667
Irc2PGuest33976
Irc2PGuest51880
Irc2PGuest97218
Onn4l7h
Sisyphus
Sleepy_
T3s|4_
Teeed
aargh2
ac9f_
b3t4f4c3__
b4dab00m
bak83_
duanin2
duck
john231
leopold
makoto
nilbog-
not_bob_afk
ntty
poriori_
profetik1
r00tobo_BNC
rapidash
shiver_
solidx66
u5657
uop23ip
vivid_reader56
w8rabbit
x74a6
obscuratus
eyedeekay: PeerSelector is a more involved issue than I first appreciated.
obscuratus
I was reviewing the FloodFillPeerSelector class, and I couldn't see anywhere where it understood how to use any other netDb except for the primary floodfill netdb.
obscuratus
On the plus side, things seem to work OK dispite this being somewhat borked.
obscuratus
We may need to pivot to something like relying on trip-wires for RI coming in the Inbound Message Distributor.
obscuratus
As a work-around, on my testing network, it wouldn't be difficult at all to make sure the subDbs are populated exhaustively with every FF RI.
obscuratus
Or, maybe begin testing the nested netdbs without any RI at all, and make sure nothing breaks when we run that way.
obscuratus
I'm almost running that way now, with only the minimum 3 FF in each subdb.
eyedeekay
Thanks for the update, my next move will probably be in the direction of no RI's in subDb's first