@eyedeekay
&Irc2PGuest88200
&zzz
+R4SAS
+RN
+StormyCloud
+acetone
+dr|z3d
+eche|off
+hagen
+orignal
+postman
+radakayot
+segfault
+snex
Arch2
Danny
DeltaOreo
FreeB
FreefallHeavens
Irc2PGuest53192
Irc2PGuest59134
Irc2PGuest59581
Irc2PGuest64993
Irc2PGuest96449
Onn4l7h
Onn4|7h
Sisyphus
Sleepy
T3s|4
T3s|4_
aeiou
ardu
b3t4f4c3__
bak83_
boonst
carried6590
cumlord
death
dr4wd3
duck
elthommy
eyedeekay_bnc
ka2
mareki2p_
not_bob_afk
onon_1
phobos_
pisslord
poriori
profetikla
qend-irc2p
rapidash
shiver_1
solidx66
thetia
u5657
uop23ip
w8rabbit
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.