@eyedeekay
&eche|on
&kytv
&zzz
+R4SAS
+RN
+StormyCloud
+T3s|4
+dr|z3d
+goose2_
+hagen
+orignal
+postman
+weko
Afkaid
An0nm0n
Arch
Danny
DeltaOreo
DiCEy1904
FreefallHeavens
Irc2PGuest11229
Irc2PGuest48909
Irc2PGuest71250
Nausicaa
Onn4l7h
PenguinDriver_
SoniEx2
T3s|4_
Teeed
acetone_
anon2
b3t4f4c3__
bak83
boonst
cumlord
dr4wd3
eyedeekay_bnc
goose2
hk
itsjustme
j6
numberwang
onon_1
poriori
profetikla
qend-irc2p
rapidash
shiver_
tr
u5657
user
veiledwizard
w8rabbit
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.