My sys-net Qube sends traffic out my ethernet card like normal, but does not respond to qvm-run commands from dom0. I can “open console in Qube” which I suspect uses something else besides qrexec to talk to it.
I can use the network just fine, but I would like to be able to use neowutran’s fork of qvm-portfwd-nftables to open access to a Qube further down the chain, and by adding "echo"s all over the qvm-portfwd script I discovered that any attempts to qvm-run in my sys-net simply hang. I started with a “systemctl status” in the “open console in qube” xterm, but I was met with a “State: running” report and 0 failed units. I “systemctl restart qubes-qrexec-agent”'d but ‘qvm-run -p sys-net “echo balls”’ in dom0 still hangs. Spams the console, though!
As you can see, I have tried exactly one thing and suddenly I am all out of ideas. I simultaneously fear and anticipate that tracking this down will lead me to learn more than I ever wanted to know about qrexec. Where do I start??
Attached below is the screenshot of the console output from qvm-running at sys-net. I tried reading it, but gleaned no useful information and possibly lost brain cells in the process.
