@eyedeekay
&zzz
+R4SAS
+RN
+RN_
+T3s|4
+acetone
+dr|z3d
+hk
+mareki2p
+orignal
+postman
+qend-irc2p
+snex
Arch
BubbRubb
Chrono
Daddy
Danny
DeltaOreo
FreefallHeavens_
Irc2PGuest21522
Irc2PGuest23831
Irc2PGuest34005
Irc2PGuest34363
Irc2PGuest58424
Leopold_xmpp_
Over
SigSegv
Sisyphus
Sleepy
T3s|4_
Teeed
aargh
ardu
b3t4f4c3__
bak83_
cumlord
death
dr4wd3_
duanin2
eyedeekay_bnc
hagen_
lazygravy
nilbog-
nnm--
not_bob_afk
ohThuku1
poriori_
pory
profetikla
r00tobo
rapidash
shiver_
solidx66
thetia
u5657_
uop23ip
w8rabbit
wew
wodencafe2
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.