Windows Networking (without sys-net or QWT)

User Support
1

How can i give my Windows qube networking?

First of all: I do pentest. Actually i am at a clients site right now lol. Now i need a windows qube to run sharphound :(. Installing QWT is out of the question because i am dealing with sensitive data here.

There is a guest wifi that i am connected to via sys-net. Choosing sys-firewall as the windows qubes netvm works flawless.

However i need to get it into the corpo network. I am connected to it via an USB Ethernet dongle in a kali AppVM.

But how can i get windows into it without installing QWT? I tried setting my kali AppVM as the window qubes netvm and configuring the network manually, however it does not work.

The qubes cannot ping each other.

Has anybody done this before and could give me a hand?

2

QWT shouldn’t be needed for networking, but you may need to set up the network configuration manually in Windows:

In case you switch from sys-firewall to sys-whonix, you’ll need a static IP network configuration, DHCP won’t work for sys-whonix. Sometimes this may also happen if you keep using sys-firewall. In both cases, proceed as follows:

Check the IP address allocated to the qube - either from GUI Manager, or via qvm-ls -n WindowsNew from a dom0 terminal (E.g. 10.137.0.x with gateway 10.138.y.z).
In the Windows qube, open the Network manager and change the IPv4 configuration of the network interfacefrom “Automatic” to “Manual”.
    Enter the Address: 10.137.0.x in our example.
    Enter the Netmask: 255.255.255.0
    Enter the Gateway: 10.138.y.z in our example.
    Enter DNS: 10.139.1.1,10.139.1.2 (the Virtual DNS addresses used by Qubes.
Click “Apply”. You should now see “Connected”.

How to install Windows qubes in Qubes OS | Qubes OS

Can you first try to connect some non-Windows qube to your kali qube and check that network works in this qube?

3

Thanks apparatus!

I was able to solve the problem by doing this:

  1. Download Linux-Router in the network providing qube (kali)
  2. Set “provides network” for kali
  3. Set netvm of windows to kali
  4. On kali a new vifX0.0 interface will show up.
  5. On windows in cmd do ipconfig and note the gateway.
  6. On kali run: lnxrouter -i vifX0.0 -o eth0 -g ip_of_gateway_in_windows --catch-dns
  7. Gain domain dominance

Works like a charm, but you may have to restart your win qube after switching qubes network settings.

4

Was ip_of_gateway_in_windows in Windows qube different from vifX0.0 ip in kali?
I think setting “provides network” for kali should make forwarding from vifX0.0 to eth0 work by default. At least this works that way for e.g. sys-net based on debian/fedora.
Maybe it’s an issue with kali template.

5

Was ip_of_gateway_in_windows in Windows qube different from vifX0.0 ip in kali?

Yes, linux-router does set a 192.168.X.1 IP, and Qubes uses 10.X.X.X so one must set it manually.

I think setting “provides network” for kali should make forwarding from vifX0.0 to eth0 work by default.

I was under the same impression, however it did not work out of the box.