@Xeha
@orignal
Arch
CIVINULL
Dann
GucciferZ
Irc2PGuest43186
Irc2PGuest61987
Irc2PGuest99418
Leopold
Meow
Napsterbater_
Over1
R4SAS
RN
RN_
acetone
anon
aside
b3t4f4c3__
eyedeekay
hk
poriori_
qend-irc2p_
r3med1tz-
rapidash
semantica
shiver_
syncthing2
thetia
u5657
uis
weko
woodwose
x74a6
yeti
PacManArch
``
orignal
SSU2 doesn't work trought the Tor. Period.
orignal
I will check what happens if asscoiation fails
PacManArch
@orignal
PacManArch
Can SSU2 use a Socks5 proxy generated by WireGuard as a front-end proxy?
PacManArch1
Can [ntcp2] use Tor Socks5 as a front-end proxy?
PacManArch1
[ntcp2]
PacManArch1
proxy = socks://10.0.6.1:10020 <wireGuard-Socks5>
PacManArch1
## Enable NTCP2 transport (default = true)
PacManArch1
enabled = true
PacManArch1
## Publish address in RouterInfo (default = true)
PacManArch1
published = true
PacManArch1
## Port for incoming connections (default is global port option value)
PacManArch1
# port = 4567
PacManArch
Hi Orignal, I have a question about i2pd. Due to my poor network environment, I deployed i2pd on a VPS in Sweden and am using Wireguard to convert a Socks5 proxy for SSU2 and NTCP2. However, when checking the Web interface, I only see the following information: NTCP2 supported, NTCP2v6 supported, SSU2 0.0.0.0:2423, and SSU2v6 [0.0.0.0]:2423. I'm not sure if this is correct, as I am paranoid about privacy
PacManArch
offer? Should I enable additional options in the default configuration? Also, I should mention that my VPS does not have IPv6.
orignal
the problem is not SSU2
orignal
the problem is Tor
orignal
it doesn't supprt UDP
orignal
if you see 0.0.0.0 it means that your UDP prioxy doesn';t work
orignal
try shadowsocks
R4SAS
privoxy didn't support UDP either
orignal
only 3proxy and dante