On 08/16/13 07:41, Axon wrote:
On 08/16/13 07:15, Axon wrote:
On 08/16/13 06:33, Axon wrote:
On 08/16/13 04:05, Zrubecz Laszlo wrote:
On 16 August 2013 12:11, Axon <ax...@openmailbox.org> wrote:
So, given all of the information above and in the previous messages, I think I can confidently say:
It's not a hardware problem.
It's not an ISP problem.
It's not a NetVM problem.
It's not an AppVM problem.
It doesn't *seem* like a ProxyVM problem. (But what else could it be?!)
On 16 August 2013 19:06, Axon <ax...@openmailbox.org> wrote:
On 08/16/13 07:41, Axon wrote:
On 08/16/13 07:15, Axon wrote:
On 08/16/13 06:33, Axon wrote:
On 08/16/13 04:05, Zrubecz Laszlo wrote:
On 16 August 2013 12:11, Axon <ax...@openmailbox.org> wrote:<snip>
So, given all of the information above and in the previous messages, I think I can confidently say:
It's not a hardware problem.
It's not an ISP problem.
It's not a NetVM problem.
It's not an AppVM problem.
It doesn't *seem* like a ProxyVM problem. (But what else could it be?!)
Just a couple of minor points to help others with the same issue:
The file is actually qubes_setup_dnat_to_ns (at least on my system).
Also, I think you accidentally left out "sh." So, full command: "sudo sh qubes_setup_dnat_to_ns".
Lastly, running this command changed the destination IP address range to the range where my firewallvm lives (not the external DNS server IP addresses, which are in /etc/resolv.conf).
neither of Marek's workarounds solves this.
$%&#ing Fedora "updates"!
> Ok, missing /etc/sysconfig/iptables is the problem. Can you check what
> was the previous qubes-core-vm package version? Simply execute "grep
> qubes-core-vm /var/log/yum.log" and you should get all the package
> history.
[user@netvm ~]$ sudo grep -i qubes-core-vm /var/log/yum.log
Mar 25 16:18:27 Installed: qubes-core-vm-kernel-placeholder-1.0-2.fc20.x86_64
Sep 22 14:16:14 Installed: qubes-core-vm-2.1.41-1.fc20.x86_64
Sep 22 14:16:16 Installed: qubes-core-vm-systemd-2.1.41-1.fc20.x86_64
Oct 01 16:07:04 Updated: qubes-core-vm-2.1.66-1.fc20.x86_64
Oct 01 16:07:05 Updated: qubes-core-vm-systemd-2.1.66-1.fc20.x86_64
Here it is:
[user@netvm ~]$ ls -l /etc/sysconfig/ip*tables*
-rw------- 1 root root 1877 Oct 1 16:07 /etc/sysconfig/ip6tables-config
-r-------- 1 root root 206 Jul 17 10:16 /etc/sysconfig/ip6tables.qubes
-rw------- 1 root root 1862 Oct 1 16:07 /etc/sysconfig/iptables-config
-r-------- 1 root root 942 Jul 17 10:16 /etc/sysconfig/iptables.qubes
Thanks!
Pedro.
Now I have a couple questions:
I would like to know if there is any way to change the install menu to avoid the vms to startup automatically so I'll be able to finish the installation without errors as explained in https://groups.google.com/forum/#!topic/qubes-users/EcfV9pDhhLA and aply the script from https://groups.google.com/forum/#!msg/qubes-users/o8eahbAg3q0/oUPBOpIRSXkJ and then manually bring the vms up after.
If this is not possible and I have to do clean r2 installation and then update, I should sudo yum update --enablerepo=qubes-*-testin instead of general yum update?