@eyedeekay
&zzz
+FreefallHeavens
+R4SAS
+RN_
+Romster
+acetone
+cims
+hagen
+nilbog
+nyaa2pguy
+orignal
+postman
+snex
Arch
Danny
Holmes
Irc2PGuest17692
Irc2PGuest28384
Irc2PGuest78852
Irc2PGuest85111
Onn4l7h
Onn4|7h
Over1
Sleepy
T3s|4_
U1F642
Wikk_0
Zapek
aargh4
ac9f
ahiru
anontor
b3t4f4c3__
dr4wd3_
duanin2
eyedeekay_bnc
leopold
mahlay
makoto
marek
mareki2p_
n2
not_bob_afk2
phil1
poriori
profetik1
qend-irc2p_
r00tobo_BNC
rapidash
rednode
sahil
test7363673
uop23ip
urist_
wodencafe2
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.