gateway as proxy for tor

[Patrick]

@boistordu

• hexchat is on 9101
• tor browser seems on something else too
• swtdate is on another one than 9050 too
  etc

Stream Isolation

@boistordu

so obviously you just opened the range to communicate or maybe you configured it in a specific file?

Search Whonix source code.

Dev/git - Kicksecure

Also:

• Whonix Networking Implementation - Developer Documentation - Feedback Wanted!
• Whonix Networking Implementation Documentation

@boistordu

So is it possible to open a range in place of “Socksport 10.152.152.10:9101” and put 9000-9200 for example?

General Tor question as per Self Support First Policy for Whonix
And no, I am not aware of such as Tor feature.
Consider posting a feature request against Tor.
You be able have to auto generate such a config file with a script.

@boistordu

And more conceptual question, since without fill the file 50_user.conf with information it works fine, does that mean that because of filling this file, your configuration file got disabled or something like that?

Variables set in lexical lower configuration files will persist if they are not chaned in lexical higher configuration files.

Configuration Files

whonix-firewall/usr/bin/whonix-gateway-firewall at master · Whonix/whonix-firewall · GitHub

real:

source_config_folder() {
   shopt -s nullglob
   local i
   for i in /etc/whonix_firewall.d/*.conf /rw/config/whonix_firewall.d/*.conf; do
      bash_n_exit_code="0"
      bash_n_output="$(bash -n "$i" 2>&1)" || { bash_n_exit_code="$?" ; true; };
      if [ ! "$bash_n_exit_code" = "0" ]; then
         echo "Invalid config file: $i
   bash_n_exit_code: $bash_n_exit_code
   bash_n_output:
   $bash_n_output" >&2
         exit 1
      fi
      source "$i"
   done
}

simpler for illustration:

for i in /etc/whonix_firewall.d/*.conf ; do
   source "$i"
done