@eyedeekay
&zzz
+R4SAS
+RN
+RN_
+T3s|4
+acetone
+dr|z3d
+eche|off
+hagen
+hk
+mareki2p
+postman
+qend-irc2p
+snex
+wodencafe
Arch
BubbRubb
Daddy
Daddy_1
Danny
DeltaOreo
FreeRider
FreefallHeavens
HowardPlayzOfAdmin
Irc2PGuest44301
Irc2PGuest56179__
Irc2PGuest73758
Irc2PGuest92548
Leopold
Onn4l7h
Onn4|7h
Sisyphus_
Sleepy
SlippyJoe_
T3s|4__
Teeed
ardu
b3t4f4c3__
bak83
boonst
cumlord
dr4wd3_
eyedeekay_bnc
guest7621
not_bob_afk
not_human
poriori_
profetikla
r00tobo
rapidash
shiver_
solidx66
thetia
u5657
uop23ip
w8rabbit
weko_
x74a6
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.