You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 15, 2021. It is now read-only.
Jon Udell edited this page Oct 2, 2014
·
1 revision
Thali needs to work even in completely locked down network environments. We are seeing more and more situations where firewalls don't allow UDP at all. That basically the only communication is outgoing (not ingoing), only TCP and only on port 80 or 443. In fact more and more networks won't even let people on the same network access point talk to each other! So the firewalling is both internal and external.
These requirements cause a few issues for I2P currently:
I2P's introduction mechanism only runs in UDP
I2P doesn't run on 'privileged' ports (e.g. those below 1024)
Both of these issues are resolvable. They just haven't been yet.
Thanks to STR4D for the great conversations on I2P and Thali.