Kicksecure Template for sys-net (dvm)

[ghostsinthebaseband]

The entire reason people tried installing from an ISO (some acrobatics like, install from ISO in a Standalone or USB qube copy to cloned Debian Template) must have been because a Template cannot be connected to networking since this grants access to Dom0. But that option is discouraged and not currently possible with Kicksecure.

It appears as there is no safe way to accomplish this goal since a Standalone cannot be redefined as a Template in Dom0 terminal after has been created, correct?

Qubes Updater infinite lag (neverized) on Templates and associated issues

If you ping 127.0.0.1 on Kicksecure, you get nothing. ICMP requests are blocked. But if you check your sys-net template that dvms, you will get a response. What is the trade off between blocking probes of your stack (to prevent OS filtering and tor bridge blocks) and still having functional networking? What are the best ways to block hostile probing? What is the safe way to make Kicksecure the default dvm? As a Standalone it cannot be made a template for sys-net dvm and a cloned template canno…

[ghostsinthebaseband]

Attempting to address the issue on the firewall level

Monroe coin bounty: how to make other VMs disconnect when the vpn software inside the VM disconnects?

I also want to block ICMP but qvm-firewall sys-net del proto=icmp accept (or sys-firewall) returns with x not in list reset Disable ping also does nothing

This seems to work

user@dom0:~ > qvm-firewall --raw sys-net add action=drop proto=icmp