@eyedeekay
&zzz
+R4SAS
+RN
+RN_
+StormyCloud
+T3s|4
+dr|z3d
+eche|off
+hagen
+hk
+mareki2p
+orignal
+postman
+qend-irc2p
+wodencafe
Arch
BubbRubb
C341
Chrono
Danny
DeltaOreo
FreeRider
FreefallHeavens
HowardPlayzOfAdmin
Irc2PGuest47568
Irc2PGuest49555
Irc2PGuest51963
Irc2PGuest64414
Irc2PGuest74708
Irc2PGuest80753
Onn4l7h
Onn4|7h
Over1
Rogueone
Sleepy
T3s|4_
Teeed
aargh
acetone_
aisle
ardu
b3t4f4c3___
b4dab00m
cumlord
dr4wd3_
duanin2
eyedeekay_bnc
nilbog
nnm--
not_bob_afk
ohThuku1
poriori_
pory
profetikla
r00tobo
rapidash
shiver_
solidx66
thetia
uop23ip
w8rabbit
weko_
wew-
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