@eyedeekay
&zzz
+R4SAS
+RN
+RN_
+Stormycloud
+T3s|4
+acetone
+dr|z3d
+eche|off
+hagen
+hk
+lance074
+mareki2p
+orignal
+postman
+qend-irc2p
+snex
Arch
BubbRubb1
Danny
DeltaOreo
FreefallHeavens
HowardPlayzOfAdmin
Irc2PGuest22497
Irc2PGuest89334
Onn4l7h
Onn4|7h
SigSegv
Sisyphus
Sleepy
SlippyJoe
T3s|4_
Teeed
ardu
b3t4f4c3__
carried6590
cumlord
dr4wd3_
eyedeekay_bnc
f00b4r_
idontpee
nnm
not_bob_afk
ohThuku1
poriori_
profetik1
r00tobo_BNC
rapidash
rascal
shiver_
solidx66
thetia
u5657
uop23ip
w8rabbit
weko_
wew
wodencafe2
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