Best to leave everything the defaults. I2P knows you are IPv4 firewalled, and you can still use it for outbound, and with SSU2 relay you can still get peer-assisted inbound connections.

We plan to release 2.8.2 on Saturday March 29 to fix SHA256 errors reported by several users.

Translation and checkin deadline is Friday March 28 Noon UTC.

Thanks for the kudos. Of course, we try to make things better every release. You didn't say what release you upgraded _from_, but if it had been a while, perhaps the cumulative effect of many releases gave you the "wow". One thing we've been battling for over two years is a set of botnet/a...

fixed in 2.8.1-1-rc, please test, we will be releasing a 2.8.2, schedule TBD

We are investigating reports of errors in 2.8.1 that look like:

java.lang.ArrayIndexOutOfBoundsException: arraycopy: length -25 is negative

The frequency appears to be higher on high-traffic routers, and are quite rare on low-traffic routers.

We will provide updates when we know more.

Hi OP, I remember you.

Don't know much about fragmentation attacks or how it would affect Java I2P or i2pd. I doubt anything in particular in 2.8.1 would make it better. If you gain any further insights, let us know.

All upcoming reviews moved to 7 PM UTC for North American Daylight Savings

Second reviews scheduled:

167 svc records Tue. Apr. 1, 7 PM UTC #ls2
163 DG2 Tue. Apr. 15, 7 PM UTC #ls2

Interesting. I don't have any ideas, although we do have some other related fixes since 2.8.0.

Can you try building the latest from source and see if it fixes your issue? We're doing our 2.8.1 release in a week so if there's more to be done it would be good to know.

There's no fix that takes less than 15 minutes, at least for me. I have to reproduce it, find it, fix it, retest, verify, check it in, update the history and roadmap, and reply.