+R4SAS
+RN_
+T3s|4
+acetone
+mareki2p
+nyaa2pguy
+orignal
+postman
+qend-irc2p
+wodencafe
Irc2PGuest16019
Irc2PGuest35412
NiceBoat
Onn4l7h
Over
Sisyphus
T3s|4_
Teeed
aargh4
ahiru
ananas
b3t4f4c3___
dr|z3d
duanin2
marek
n2_
not_bob_afk2
o3d3
poriori
profetikla
r00tobo
sahil
solidx66
uop23ip
urist_
x74a6
zelgomer
zlatinb
interesting thought: reddit.com/r/i2p/comments/ued46f/inproxy_or_connecting_to_i2p_proxy_from_a_remote ( ACLs for tunnels & console )
eche|on
i2p does not need inbound tunnels, it works better, but does not ultimately needs them
zzz
what does ACL mean in this context? IP/port restrictions?
zlatinb
yes I think so
zzz
as opposed to OS-level firewall rules then?
zlatinb
I guess
mesh
yeah you're better off with ssh port forwarding
mesh
you should never expose such an important web app to non-localhost interfaces
mesh
but I understand where the poster is coming from. the i2p router should essentially have ssh port forwarding capability built in
mesh
though in reality what you'd want is something like a ssp/vpn-type solution.