Hi
I stumbled accross the same issue as Wh0p5 : stucked with VirtualBox Whonix Gateway because no internet on host and therefore, no internet through NAT.
As Patrick stated it seems there is currently no official way to make Whonix Gateway work on bridge mode.
So, this is what I finally settled for… you’ll need a firewall, ideally an external one, with support for dynamic IPs lists. I use OpnSense but I’m sure there’s plenty of other software out there supporting this.
Create a new rule allowing all IPs in the following list to be accessed from the host : https[DOUBLEDOT]//www[DOT]dan[DOT]me[DOT]uk/torlist/?full
Configure an automatic refresh to ensure the nodes list keeps up to date - daily should be enough.
If you’re worried about your ISP or tierce parties knowing about you using Tor, all this traffic can be routed through a VPN, thus allowing for Tor-over-VPN configuration.
This is less than ideal (host actually can get limited access to the internet) but I guess it’s still a good compromise. Traffic is tightly restricted to the Tor network ; and the additional VPN fills up for IP leaks that could come from malicious nodes (by monitoring the traffic or accepting non-Tor connections).
This approach is adequate for my security profile, as I’m mostly looking to avoid any data leaking from my host without me knowing about it, while keeping my Tor traffic discrete. However this could be unsufficient for more elaborate OPSEC scenarios, and I would suggest anybody looking for more to switch to Qubes, who supports offline Dom0 and Whonix VMs.
Cheers