Please help config Proxychains-ng for Yi Home 17CN

[voquangminh]

Hi,
I have Yi home 720p 17CN and success working with yi hack v3 by using proxychains-ng tool for a long time.

Now i had change a new router, and i can not config proxychains-ng anymore because old server are dying.

After i reset camera and intsall new yi hack v5 but cannot use it "This camera may be not use outside china"

I search so much web to config proxychains but can not find how to use China proxy
this is proxychains config file i use.

random_chain

chain_len = 1

tcp_read_time_out 15000
tcp_connect_time_out 8000

[ProxyList]
socks4 61.171.50.169 6688
socks4 218.78.65.202 6688

Please help me to use camera again. I had succeed connect it but always show offline and said check your internet connection.

[alienatedsec]

@voquangminh Have you tried changing this from no to yes in the system.conf file?

yi-hack-v5/src/static/static/home/yi-hack-v5/etc/system.conf

Line 19 in 4407928

PROXYCHAINSNG=no

[voquangminh]

Hi, this is string I use
socks4 61.171.50.169 6688;socks4 218.78.65.202 6688;socks5 1.180.0.242 7302;socks5 60.190.195.146 10800

[alienatedsec]

It works - at least partially - so far it shows results for Test without proxy:

I need to fix the proxychain execution as it feels like the final compilation is wrong - leave it with me, but you should see something after pressing save and test configuration button

[alienatedsec]

@voquangminh I fixed the execution bit, but it shows the following

/tmp/sd/yi-hack-v5/bin #  proxychains4 wget -O- -q http://ipinfo.io
[proxychains] config file found: /tmp/sd/yi-hack-v5/etc/proxychains.conf
[proxychains] preloading /tmp/sd/yi-hack-v5/lib/libproxychains4.so
[proxychains] DLL init: proxychains-ng 4.16
error: no valid proxy found in config
/tmp/sd/yi-hack-v5/bin # cat  /tmp/sd/yi-hack-v5/etc/proxychains.conf
socks4 61.171.50.169 6688
socks4 218.78.65.202 6688
socks5 1.180.0.242 7302
socks5 60.190.195.146 10800
/tmp/sd/yi-hack-v5/bin #

I will attach a separate package for you to test

[alienatedsec]

@voquangminh fixed - at least for me

Try and follow #278 or wait for 0.4.0b