@eyedeekay
&zzz
+R4SAS
+RN
+StormyCloud
+T3s|4
+acetone
+altonen
+dr|z3d
+hk
+lbt
+orignal
+postman
+radakayot
+snex
+weko
+wodencafe
Arch
BravoOreo
Dann
FreeB
FreefallHeavens_
Irc2PGuest11045
Irc2PGuest27999
Irc2PGuest28584
Irc2PGuest3338
Irc2PGuest59134
Irc2PGuest82579
Onn4l7h
Onn4|7h
Sleepy_
Soni
T3s|4_
Teeed_
aeiou_
aisle1
ardu
b3t4f4c3__
bak83
dickless
dr4wd3
enoxa
eyedeekay_bnc
hagen_
not_bob_afk
phil
plap
poriori_
profetikla
qend-irc2p
rapidash
solidx66_
u5657
uop23ip
w8rabbit
x74a6h
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.