I had been looking into some weird behavior of my own (in certain cases, sites being browsed are appearing in http://localhost:7657/netdb?l=1 and not http://localhost:7657/netdb?l=7 - whenever that happens, the site will not load), and there may be an oversight in IterativeSearchJob when looking up ...

I noticed a large spike of nodes on the stats.i2p graph on 8 Feb, roughly half the size of the initial attack. They report API 0.9.67.

My system is also tracking 2.5x the normal amount of floodfills (even compared to during-attack numbers).

The ssh command works a bit differently from that. Here's what you run on your client to access your server via I2P: Essentially, you use the client tunnel as your "server address".