Documentation: network issues debug information

[adrelanos]

In #1067 it was a time consuming process to have @marmarek do "manual remote debugging". I.e. having Marek ask to run me a command, doing that, posting the results, etc. Since I am currently having a last Qubes R3 stable upgrade broke all networking (#1848), I was wondering if it would be helpful for advanced users / testers to have a documentation page that explains how to gather lots of debug output to simplify and speed up individual support request for all parties. Below I add some likely requested debug information that I gathered from #1067. Would such a documentation page be useful?

---

Which Qubes version are you using? (R3, R3.1 etc.)

Which Qubes suite are you using? (stable, testing, experimental)

On which TemplateVMs are the following of your VMs based on?

• sys-net
• sys-firewall
• an AppVM connected to sys-firewall

Run the following commands inside:

• sys-net
• sys-firewall
• an AppVM connected to sys-firewall

Commands to run:

• sudo systemctl list-units --failed
• sudo service iptables status
• cat /etc/resolv.conf
• sudo time iptables --list
• sudo time iptables --list -t nat
• sudo ifconfig
• ps aux
• ping 8.8.8.8
• ping sys-net from sys-firewall
• ping sys-firewall from AppVM

(Feel free to edit my post to add more commands etc.)

[marmarek]

I've heard that github support issue template. It's here: https://help.github.com/articles/creating-an-issue-template-for-your-repository/

Probably not worth for such detailed list network-specific. But maybe some initial questions (versions) should be there?

[adrelanos]

Seems useful but a separate enhancement.

If you think this network issues debug information page would not help anyone, we can close this issue.

On a second thought, I think a script / tool to gather information would be a lot more usable.

[marmarek]

Something like dracut already does in case of boot failure? It prepares a txt file with a lot of useful data (output of commands).

[adrelanos]

Yes.