kzlz
June 20, 2025, 2:42am
1
I recently realized that I can boot a live USB from an ISO using a standalone template with ‘boot qube from DISC or block device.’
However, I am unable to provide network access to live usb.
How can I enable network access?
If I can do this, it would be convenient to combine Whonix and the live USB, so please let me know how.
otter2
June 20, 2025, 8:32am
2
TL;DR Set ip, gateway, netmask, and dns manually
A standalone is a type of qube that is created by cloning a template. Unlike templates, however, standalones do not supply their root filesystems to other qubes. Examples of situations in which standalones can be useful include: Qubes used for...
p.s.
Simply set your whonix network qube as the net qube for standalone in question
1 Like
kzlz
June 23, 2025, 2:28am
3
It works well with sys-firewall, but I can’t connect to the internet with sys-whonix. Why do you think that is?
otter2
June 23, 2025, 8:54am
4
Are you sure? Just FYI, ping doesn’t work over tor
Does it work with qubes-integrated vms?
It should work without any further modification
kzlz
June 23, 2025, 9:47am
5
That’s true. Other VMs are working fine.
unman
June 23, 2025, 11:11am
7
Absolutely not - absent some clever routing, many OS require the
netmask to be set properly, in order to reach upstream.
/24
would allow 10.137.0 addresses, which may be fine depending on what
upstream gateway is used.
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.
2 Likes
otter2
June 23, 2025, 1:39pm
8
opened 01:49PM - 05 Jun 25 UTC
C: Whonix
C: windows-vm
P: default
needs diagnosis
C: networking
affects-4.2
community template
[How to file a helpful issue](https://www.qubes-os.org/doc/issue-tracking/)
###… Qubes OS release
4.2.4
### Brief summary
A number of users on the Forum report that Windows HVM can no longet network through Whonix.
HVM that worked previously have stopped working.
### Steps to reproduce
Use Windows HVM with sys-whonix as netvm, networking enabled.
Update Whonix
### Expected behavior
Networking in the Windwos qube will continue to work.
### Actual behavior
Forum user jxadceno reports:
however suddenly after updating whonix-gateway all networking to the HVM is broken, showing "Unidentified network".
User dexter05 reports:
sys-whonix -> windows HVM (not working after last update, worked fine for years)
sys-whonix -> sys-vpn -> windows HVM (works fine, go figure)
The Windows error code is 10060. Winsock timeout error.
### Additional information
Forum thread is in User Support - "Windows HVM + sys-whonix networking suddenly broken"
Can confirm, for some reason parrot doesn’t connect even if netmask is less than 32
p.s. @kzlz :
1 Like
kzlz
June 23, 2025, 2:10pm
9
echo 1 | sudo tee $(find /proc/sys/net/ipv4 -name arp_ignore)
I changed the netmask to 24, and although I don’t fully understand it, I executed this command in sys-whonix, and the standalone was able to connect to the internet.
otter2
June 23, 2025, 5:31pm
10
Please don’t, this forum may be a good attack vector against qubes
Besides, even workarounds posted by core developers might have flaws
kzlz
June 24, 2025, 1:26am
11
Indeed. I have a lot to learn, so I often execute commands before fully understanding them, and I regret that… Was this command dangerous?
otter2
June 24, 2025, 2:58pm
12
Maybe? It makes sys-whonix arp policy less strict, may allow some spoofing attacks:
committed 10:33AM - 19 Dec 24 UTC
p.s. About arp_ignore
:
https://www.kernel.org/doc/Documentation/networking/ip-sysctl.txt