@eyedeekay
&eche|on
&kytv
&zzz
+R4SAS
+RN
+StormyCloud
+T3s|4
+dr|z3d
+hagen
+orignal
+postman
+weko
An0nm0n
Arch
Danny
DeltaOreo
FreefallHeavens
Irc2PGuest48909
Irc2PGuest57403
Irc2PGuest60331
Irc2PGuest9720
Nausicaa
Onn4l7h
SoniEx2
T3s|4_
Teeed
acetone_
anon1
b3t4f4c3__
bak83
boonst
dr4wd3
eyedeekay_bnc
goose2__
hk
itsjustme_
j6
not_bob_afk
numberwang
onon_1
pisslord
poriori_
profetikla
qend-irc2p
r3med1tz-
rapidash
shiver_
u5657
uop23ip
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