5067 Commits (4c1f6112a7adf9ce85280a36ef9052904263d0f0)

Author	SHA1	Message	Date
Jason Rhinelander	4c1f6112a7	REVERT ME: debug incoming dict data	7 months ago
dr7ana	f725c07f2d	dont bomb with bootstrap reqs	7 months ago
dr7ana	e0c1069790	kiiiiiick	7 months ago
dr7ana	efe5fd3b5b	try queueing	7 months ago
dr7ana	0bf3a3323a	kick	7 months ago
dr7ana	238cc3d0da	kick	7 months ago
dr7ana	5f430a392b	kick	7 months ago
dr7ana	63644d3d84	Bootstrap seed ... - nodes now send their RC to the bootstrap seed on making a request - allows the bootstrap seed to distribute RCs	7 months ago
dr7ana	f2feea74ee	Crit logging ... - TODO: discuss authentication for nodes connecting to bootstrap seed - crit log num connected/RC's, conn open/closed, etc	7 months ago
Jason Rhinelander	412ce44139	Update libquic	7 months ago
Jason Rhinelander	daeff3ee7e	Remove duplicate connection closing method ... `deregister_peer` does the exact same thing as `close_connection` so just remove it. Also removes an unnecessary loop dispatch call (because we *have* to be in the logic thread already to be able to touch the variables we are touching before the dispatch).	7 months ago
Jason Rhinelander	b3dc23e1bf	Remove release motto ... This doesn't really have a purpose.	7 months ago
dr7ana	9084d39e5a	Squashed misc testnet fixes	7 months ago
Jason Rhinelander	bc2cb46d9c	testnet: don't give oxend and error when testing is disabled	7 months ago
dr7ana	8af38d3d44	TELL ME WHEN IT WORKS	7 months ago
dr7ana	d00257b9f0	address parsing ... - straightened out setting of public addr and public port in config vs listen ("bind") addr - fixed small bug in router contact writing and saving	7 months ago
dr7ana	cef2ff7782	Local router mode ... - Up and running locally, no connections yet - Next: flip testnet and do the gosh dang thing	7 months ago
dr7ana	ed6bd28a35	testnet prep ... - redoing link_manager functions again to implement previously ignored review comments on several PRs - conceptually merging "whitelist_routers" and new "known_{rids,rcs}", s.t. we can completely eliminate white/red/gray/green/etc lists in favor of something that isn't dumb	7 months ago
dr7ana	c9268dceba	trust model edge case handling ... - Once we have our set of returned rc's and accepted rid's (ones that were found locally), the remainder are placed in an "unconfirmed" state - Once there, they have five subsequent successful fetches to be found in request response, at which point their verification counter is incremented and their attempt counter is reset - If they appear three times, they are "promoted" and moved to our "known_{rid,rc}" list	7 months ago
dr7ana	62c37825b0	testnet prep ... - disable reachability testing with config option; required to be done on testnet - reachability testing pipeline through link_manager executes pings similar to storage server. connection established hook reports successful reachability, while connection closed callback (with non-default error code) reports unsuccessful testing	7 months ago
dr7ana	70e9c1ae25	trust model fetch fails ... - bootstrap cooldown implemented with 1min timer in case all bootstraps fail - set comparison implemented in non-initial and non-bootstrap rc fetching; set comparison in rid fetching is done every fetch - nodedb get_random functions refactored into conditional/non-conditional methods. Conditional search implements reservoir sampling for one-pass accumulation of n random rcs	7 months ago
dr7ana	3508dee8d8	trust model ... - greedy evaluation of returned rid's, simplifying post-processing logic to simple frequency comparison per rid against a constant threshold - tidied up link_manager request/response handling - TODO: - review and decide thresholds - evaluate necessity and potential implementation of rc comparison	7 months ago
dr7ana	91121ea22b	pull yourself up by your bootstraps sonny ... - initial/subsequent fetching combined for RouterContacts and RouterIDs - bootstraps fallback implemented and looped into fetch logic	7 months ago
dr7ana	f6e651caea	move from vectors to unordered_sets ... - When receiving a request to fetch RouterID's, the remote endpoint fulfilling the request stores them in an unordered set. When the request caller receives that payload, it is loaded into a vector in the same order. However, we should just load it directly into an unordered set to enforce both the order and that none appear twice - The trust model will have to operate on multiple large lists of RouterID's and RC's efficiently, and maintaining a sort order ensures the values are workable immediately after deserialization	7 months ago
dr7ana	ba3fffb765	housekeeping pre-trust model	7 months ago
dr7ana	b6cc86e25b	fetch RID result handler logic	7 months ago
dr7ana	3fc7980691	less synchronous for the subsequent fetches	7 months ago
dr7ana	6559617816	RC/RID fetching logic implemented	7 months ago
dr7ana	5fa3c2be87	housekeeping and groundwork, initial commit	7 months ago
Thomas Winget	2b2d8c51a1	rework rotate_rc_source function, just for 'normal operation' now	7 months ago
Thomas Winget	70d2052cd4	minor fixups	7 months ago
Thomas Winget	dab1e06892	FindRouterMessage is gone, also clang-format	7 months ago
Thomas Winget	14b9aa20ee	(client) periodically fetch RouterIDs from peers	7 months ago
Thomas Winget	b353fd4095	Minor RC load/store/prune fixups	7 months ago
Thomas Winget	c30a4dd44a	Implement fetch RouterIDs method and usage ... Periodically clients will fetch the set of RouterIDs for all relays on the network. It will request this list from a number (12, currently) of relays, but as we are likely to be requesting from more relays than we want to have edge connections, this request will itself be relayed to the target source via one of our edges. As we can't trust our edge to do this honestly, the responses are signed by the source relay. TODO: the responses from all (12) relays are collected, then processed together. The reconciliation of their responses is not yet implemented. TODO: the source selection for this method obviously requires sources to begin with, but this is the method by which we learn of those...bootstrapping is still a bit in-progress, and will need to be finished for this. TODO: make Router call this periodically, as with RC fetching.	7 months ago
Thomas Winget	6952e8f705	Add command to fetch RCs from remote node ... This command will be called periodically by clients to maintain a list of RCs of active relay nodes. It will require another command (future commit) to fetch the RouterIDs from many nodes and reconcile those so we have some notion of good-ness of the RCs we're getting; if we get what seems to be a bad set of RCs (this concept not yet implemented), we will choose a different relay to fetch RCs from. These are left as TODOs for now.	7 months ago
Thomas Winget	5bf520d0f1	minor style/naming changes	7 months ago
Thomas Winget	76d45ec802	remove explicit arg that mirrors default	7 months ago
Thomas Winget	b044622a21	implement new rc gossip logic ... Relays will now re-sign and gossip their RCs every 6 hours (minus a couple random minutes) using the new gossip_rc message. Removes the old RCGossiper concept	7 months ago
Thomas Winget	2425652696	NodeDB RCs don't need insertion time ... We will want some notion of "when did we receive it" for RCs (or RouterIDs, details tbd), but that will be per-source as a means to form some metric of consensus/trust on which relays are *actually* on the network. Clients don't have a blockchain daemon to pull this from, so they have to ask many relays for the full list of relays and form a trust model on that (bootstrapping problem notwithstanding).	7 months ago
Thomas Winget	29ec72f0da	implement and use "gossip_rc" command ... TODO: refactor or remove RCGossiper and revisit RC regen and when-to-gossip logic.	7 months ago
Thomas Winget	27aea62994	Remove find/lookup router ... We're removing the notion of find/lookup a singular RC, so this gets rid of all functions which did that and replaces their usages with something sensible.	7 months ago
Thomas Winget	ad9d0b19c1	remove rc_lookup_handler, relocating useful parts ... RC "lookup" is being replaced with "gimme all recently updated RCs". As such, doing a lookup on a specific RC is going away, as is network exploration, so a lot of what RCLookupHandler was doing will no longer be relevant. Functionality from it which was kept has moved to NodeDB, as it makes sense for that functionality to live where the RCs live.	7 months ago
dr7ana	28047ae72f	Merge pull request #2223 from tewinget/path-build-correctly ... onion encrypt path build frames	7 months ago
dr7ana	e58e8473f8	Merge pull request #2216 from tewinget/path-messages ... Path build and onioned messages	7 months ago
Thomas Winget	feaf0b9193	fix some copy/paste derping ... also deserialize to unsigned string where possible/useful so to not have unnecessary reinterpret_casts all over the place.	7 months ago
Thomas Winget	2e5c856cf3	onion encrypt path build frames ... path build frames should be onioned at each hop to avoid a bad actor controlling two nodes in a path being able to know (with certainty, temporal correlation is hard to avoid) that they're hops on the same path. This is desirable as in the worst case someone could be your edge hop and terminal hop on a path, and now the terminal hop knows your IP making the path basically pointless.	7 months ago
Thomas Winget	d7e2e52ee4	messages::status -> messages	7 months ago
dr7ana	826ef2bbe6	libquic bump	8 months ago
Thomas Winget	e6eeda0f15	remove some unused "path build"-related functions	8 months ago