@eyedeekay
&eche|on
&zzz
+FreefallHeavens
+R4SAS
+RN
+Romster
+acetone
+cims
+dr|z3d
+hagen
+nilbog
+orignal
+postman
+qend-irc2p
+snex
+wodencafe
Arch
Dann
Holmes
Irc2PGuest12976
Irc2PGuest1526
Irc2PGuest28234
Irc2PGuest3143
Irc2PGuest32287
Irc2PGuest51098
Irc2PGuest57041
NiceBoat
OfficialCIA
Onn4l7h
Onn4|7h
Over
SilentWave
Sisyphus
Sleepy
T3s|4_
Wikk__
Zapek
aargh4
ac9f
ahiru
ananas_
aqua
calamares_
dr4wd3
duanin2
fa
leopold
mahlay
makoto
n2_
not_bob_afk2
poriori
pory
profetikla
r00tobo_BNC
rapidash
test3847473
thetia
uop23ip
user1
vivid_reader56
x74a6
zelgomer
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.