Good morning Tor Project.
I have been active in this community for a long time.First ,when I was a 
beginner, I only donated bitcoins and ran a snowflake-proxy from browser.Then 
switched to a standalone proxy (compiled from source when I used windows).After 
that, I switched to Linux (first Mint, than Trisquel because it's fully free as 
in freedom, FSF supported).
The problem with both distros is that snowflake-proxy (using apt package) 
doesn't work on those distros. It can't connect to a certain host/ website from 
Tor. I don't remember the output but you could test them in a virtual machine. 
And a HUGE problem is that /var/log/syslog (or syslog1) is continously filled 
with those errors, after certain days, I have seen my disk space reduced with 
50 GB and I coulnd't figure out why. After many trying, I found out that those 
files were filled with errors from tor snowflake. PLEASE, post it on debugging 
in snowflake.
After learning to use CLI distros (without GUI), I installed snowflake (with 
apt) in a debian virtual machine (Qemu-KVM with Virtual Machine Manager). It 
works as expected, it shows me how much data was sent/received.
After that, I decided to delete the snowflake and run a middle/guard relay 
(again, debian, qemu-kvm). The choice for using qemu-kvm over vitualbox is that 
virtualbox now depends on the non-free open watcom compiler. This is how I 
installed qemu-kvm: https://trisquel.info/en/wiki/virtualization-using-kvm. And 
it was a nightmare to set the tor relay up because port forwarding didn't work 
(I never tested on virtualbox). My port was not reachable from outside, 
although I set port forwarding in my router settings. It took me almost 20 
hours and 35 tryings to make it work.
After so many tryings, I managed to find a solution. Please, post it on 
middle/relay guard installation tutorial or in debugging section, because 
almost nobody will be willing to do the work I did to fix the error. I will 
write it here.
And another thing, my ip 95.76.41.164 has 3 relays on 
https://metrics.torproject.org/rs.html#search/myCuteRelay . Please delete the 
first and second, because they will never work again, I deleted those VM's. 
Only the last one will be good.
Sorry for my english, I am not a native speaker.
So as conlusions:
1) Snowflake proxy doesn't work, at least, on Mint and Trisquel, although they 
are both based on Ubuntu. And the HUGE problem is that /var/log/syslog (or 
syslog1) is continously filled with those errors. It can be solved with sudo 
truncate -s 0 /var/log/syslog.
2) For someone who is using QEMU-KVM to run a middle/guard relay (at least on 
trisquel), the solution to make the relay work is to execute the following 
commands on HOST computer (not VM) EVERY TIME THE SYSTEM REBOOTS (or shuts 
down) BEFORE starting the VM:
sudo iptables -t nat -F
sudo iptables -Fsudo sysctl -w net.ipv4.ip_forward=1sudo iptables -t nat -A 
POSTROUTING -s aaa.aaa.aaa.a/aa -o zzz00z0 -j MASQUERADEsudo iptables -t nat -A 
PREROUTING -i zzz00z0 -p tcp --dport ppp -j DNAT --to-destination 
bbb.bbb.bbb.bbb:pppsudo iptables -A FORWARD -p tcp -d bbb.bbb.bbb.bbb --dport 
ppp -m state --state NEW,ESTABLISHED,RELATED -j ACCEPT
I wrote with with Italic the commands and with Bold the parameters that MUST be 
changed, based on each person computer. The command that must be used in order 
to change them, both on host and vm is ip -c addr show
aaa.aaa.aaa.a/aa - (host) the inet address of virbr0 (qemu-kvm) (e.g. 
192.168.123.1/24)zzz00z0 - (host) the connection name of local inet address of 
host (e.g. enp27s0)ppp - (VM) the port chosen in torrc file (e.g. 
443)bbb.bbb.bbb.bbb:ppp - (VM) the local inet address of vm and chosen port 
(e.g. 192.168.123.111:443)bbb.bbb.bbb.bbb - the same address as above but 
without chosen port (e.g. 192.168.123.111)
There is NO functional command that must be run on VM. Just ip -c addr show to 
see the address. The Network source of VM is the default one (Virtual network 
'default':NAT). Not bridge or macvtap device.

3) Please delete the first and second relays created on my ip 95.76.41.164. 
They won't ever work again.
If you have any other questions, please ask me.Please provide me an answer to 
know that you received and read my email.
Thank you and best regards!










_______________________________________________
network-health mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to