[HOME] [DOWNLOAD] [DOCS] [NEWS] [SUPPORT] [TIPS] [ISSUES] [DONATE]

[Solved] Gateway Won't Connect - ASUS MB

HI,

Thank you for your work and your time to read this. I’ve been banging on this for a week. I’m not educated on this stuff but I’ve had a lot of fun learning. I’ve never studied the first 2 layers until now. Its hard for me to ask this question intelligently but here goes.

Whonix Gateway times out during whonix check. No TOR. Something about a directory
I do have internet connectivity
TOR browser package works fine on the host.
I am not in a restricted country and have never had ISP restrictions for any activity.

My network connections are set for NAT on adapter1 with adapter enabled and line connected. Currently on the default standard adapter type pcfastIII, though I briefly tried the Intel desktop one. Adapter2 is internal connected to Whonix, adapter is enabled, cable is connected, default pcfastIII adapter type also.

Images are the latest and verified
Virtual box is latest 4.3.16
Operating system Win7 64bit

I don’t know how yet to C&P between guest and host but if I ifconfig:
eth0 inet 10.0.2.15 gw 10.0.2.255
eth1 inet 192.168.0.10 gw 192.168.0.255
locl inet 127.0.0.1 gw 255.0.0.0

Here are the hosts adapter routes

[code]===========================================================================
Interface List
11…88 88 88 88 87 88 …Intel® 82579V Gigabit Network Connection
28…08 00 27 00 bc 2c …VirtualBox Host-Only Ethernet Adapter
1…Software Loopback Interface 1
12…00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
13…00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
14…00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2

IPv4 Route Table

Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.6 20
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
192.168.1.0 255.255.255.0 On-link 192.168.1.6 276
192.168.1.6 255.255.255.255 On-link 192.168.1.6 276
192.168.1.255 255.255.255.255 On-link 192.168.1.6 276
192.168.56.0 255.255.255.0 On-link 192.168.56.1 276
192.168.56.1 255.255.255.255 On-link 192.168.56.1 276
192.168.56.255 255.255.255.255 On-link 192.168.56.1 276
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 192.168.56.1 276
224.0.0.0 240.0.0.0 On-link 192.168.1.6 276
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 192.168.56.1 276
255.255.255.255 255.255.255.255 On-link 192.168.1.6 276

Persistent Routes:
Network Address Netmask Gateway Address Metric
0.0.0.0 0.0.0.0 192.168.0.10 Default

IPv6 Route Table

Active Routes:
If Metric Network Destination Gateway
13 58 ::/0 On-link
1 306 ::1/128 On-link
13 58 2001::/32 On-link
13 306 2001:0:9d38:90d7:8d2:d98:b7a0:1b89/128
On-link
28 276 fe80::/64 On-link
11 276 fe80::/64 On-link
13 306 fe80::/64 On-link
13 306 fe80::8d2:d98:b7a0:1b89/128
On-link
11 276 fe80::5de6:f913:97c5:6a6a/128
On-link
28 276 fe80::81a5:6a1f:3997:9745/128
On-link
1 306 ff00::/8 On-link
13 306 ff00::/8 On-link
28 276 ff00::/8 On-link
11 276 ff00::/8 On-link

Persistent Routes:
None[/code]

In my mind eth0 and eth1 on guest should be switched around but when I try to switch them in the vm I getDHCP errors during guest bootup

I had this working once but I did two things at once and when i try to duplicsate in several ways I cannot recreate. The two things I tried were: On the Vbox. I did a VBoxManage modifyvm “Whonix-Gateway” --natnet1 “192.168/16”. This is mentioned in vbox docs under advanced topics, fine tuning nat engine.

Another thing I did at the same time was disable network i control which is an ASUS motherboard Bios option that is supposed to do some packet shaping but has a reputation for slowing things down.

Suddenly Whonix check ran and then I did the couple recomended updates after a successful first run. They were suspiciously fast for going through TOR, full speed in fact. Then I went to Whonix workstation and updated TOR or Tor browser and halfway through things froze and never worked again.

Ive tried some reinstalls and rebuilds today, The only thing left would be for me to try setting up my host adapter to use 10’s instead of 192’s. not sure how that should be set to even try it though as my studies :slight_smile: of layer 1 and 2 are still a mere aquaintance.

Any help would be appreciated

Not sure what you mean by times out. Can you post the full output of whonixcheck please?

What happens if you re-run whonixcheck? Does that error persist?

Images are the latest and verified

eth1 inet 192.168.0.10 gw 192.168.0.255


Probably not latest version. Whonix 9 has been released. (https://www.whonix.org/blog/whonix-anonymous-9-released) Doesn’t use 192.168.0.10 anymore.
In my mind eth0 and eth1 on guest should be switched around but when I try to switch them in the vm I getDHCP errors during guest bootup
These changes are neither required nor recommended.
The two things I tried were: On the Vbox. I did a VBoxManage modifyvm "Whonix-Gateway" --natnet1 "192.168/16".
These changes are neither required nor recommended.
Another thing I did at the same time was disable network i control which is an ASUS motherboard Bios option that is supposed to do some packet shaping but has a reputation for slowing things down.
Sounds good if BIOS does not interfere with this.
They were suspiciously fast for going through TOR, full speed in fact.
Sometimes you get quite fast circuits. apt-get on Whonix-Gateway running through clearnet is very, very unlikely due to [url=https://www.whonix.org/wiki/Stream_Isolation]stream isolation and uwt[/url].
The only thing left would be for me to try setting up my host adapter to use 10's instead of 192's.
These changes are neither required nor recommended.

Thanks again for your time. You were of course right on the version number of whonix, my bad :frowning:

I got it working and its not a Whonix problem as far as I can tell. The newest VirtualBox versions have some driver incompatibilities. VBOX Win7 Thread Mine was not on the list but it appears many of these affect the lower layers of the network.

To fix mine I had to go into the adapter and disable my Agnitium Firewall Driver. I still need to research this to see what I’ve opened up but at least its working, right out of the box with default settings.

Of interest to people that run vpns on windows 7 there is a filter in the above link for a VPN filter by the name of Shrew Lightweight Filter, Cisco VPN, other firewalls of interest and some Virtualizers. Mine is not on the list… yet.

In short for similar problems, include sorting through your (local)adapter for third party additions.

Thanks again

[Imprint] [Privacy Policy] [Cookie Policy] [Terms of Use] [E-Sign Consent] [DMCA] [Investors] [Priority Support] [Professional Support]