The received packet sizes as reported in the stats should include the
encryption that is decrypted by the client. Note that this does not
include the sphinx encryption, which is already removed by the exit
gateway. This is also the reason for the relatively large discrepancy of
the reported sent and received packets.
* WIP: put in some packet counters
* ws packet counters
* wip
* Add static counters to client traffic stream
* Tweak status log message
* Add packet statistics control
* fixup! Add static counters to client traffic stream
* tweak log
* Move the packet statistics control one level up
* Redo packet stats control to collect locally
* Switch loop cover traffic report over to new channel mechanism
* Switch packet stats in real message stream to channel report
* Finished switching over to channel reporting
* Fix handle stats event
* Log packets received
* Tidy up
* rustfmt
* Add strongly typed stats reporter
* Count cover packets as well
* Log packet sizes sent
* Also log recieved sizes
globally updated sqlx to 0.6.3
wip
basic processing loop
wip
starting on modules
all of the requesting logic, catching up, etc
remaining work includes persisting the data
wip
persisting block data
initial and extremely basic nyxd block scraper
* Try passing mix_hops all the way down the call chain
* Set zero mix_hops manually
* fix
* also set zero mix hops in tun listener
* fix
* mix hops for surbs
* Another case covered
* Remove mix_hops config from Traffic
* clippy
* Add comment about why we added new functions
* Update comment
* Add surb_mix_hops to wasm config
* Remove temporary added mix_hops = 0
* Remove another temporary added mix_hops = 0
* Add comment about the limitation of num_mix_hops
* Add wireguard_mode flag to SDK
* Add to builder in sdk too
* Move hardcoded IP in a lighter crate
* Put in network defaults
* Fix linux
* Move wireguard mode swap before init
* Use the updated gateway hosts
* Set wireguard IP even for pre-inited mix client
* Fix typo
Jędrzej Stuczyński