From a133649a11c0a36c8b77aad769dcbb6698ac70a5 Mon Sep 17 00:00:00 2001 From: Axon Date: Wed, 13 Apr 2016 17:01:53 +0000 Subject: [PATCH] Fix code block syntax --- security/qubes-firewall.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/security/qubes-firewall.md b/security/qubes-firewall.md index 2b515b81..980888ad 100644 --- a/security/qubes-firewall.md +++ b/security/qubes-firewall.md @@ -78,9 +78,9 @@ In order to allow networking between VM A and B follow those steps: * Start both VMs, and also open a terminal in the firewall VM * In the firewall VM's terminal enter the following iptables rule: - ~~~ - sudo iptables -I FORWARD 2 -s -d -j ACCEPT - ~~~ +~~~ +sudo iptables -I FORWARD 2 -s -d -j ACCEPT +~~~ * Now you should be able to reach the VM B from A -- test it using e.g. ping issues from VM A. Note however, that this doesn't allow you to reach A from @@ -95,11 +95,11 @@ In order to allow networking between VM A and B follow those steps: file present, so we likely will be creating it, unless we had some other custom rules defines earlier in this firewallvm): - ~~~ - [user@firewallvm ~]$ sudo bash - [root@firewallvm user]# echo "iptables -I FORWARD 2 -s 10.137.2.25 -d 10.137.2.6 -j ACCEPT" >> /rw/config/qubes_firewall_user_script - [root@firewallvm user]# chmod +x /rw/config/qubes_firewall_user_script - ~~~ +~~~ +[user@firewallvm ~]$ sudo bash +[root@firewallvm user]# echo "iptables -I FORWARD 2 -s 10.137.2.25 -d 10.137.2.6 -j ACCEPT" >> /rw/config/qubes_firewall_user_script +[root@firewallvm user]# chmod +x /rw/config/qubes_firewall_user_script +~~~ Port forwarding to a VM from the outside world --------------------------------------------------