Recent content by Hamclock

After much back-and-forth, it turns out the problem was... ARP tables in a router I don't control! It turns out this problem was completely not Proxmox-related, but thanks for helping me troubleshoot and convince myself that that was really the case and I needed to lean on the data center a...

/etc/pve/kvm-networking.sh: No such file or directory And on vm 103 (it's a pain to get plain text off this machine):

~# pveversion -v proxmox-ve-2.6.32: 3.2-129 (running kernel: 2.6.32-30-pve) pve-manager: 3.2-4 (running version: 3.2-4/e24a91c1) pve-kernel-2.6.32-30-pve: 2.6.32-130 pve-kernel-2.6.32-29-pve: 2.6.32-126 lvm2: 2.02.98-pve4 clvm: 2.02.98-pve4 corosync-pve: 1.4.5-1 openais-pve: 1.1.4-3 libqb0...

Here's another problem: I can't even use the server's original IP. I spun up a stock Ubuntu 14.04 live image, pointed its network interface at vmbr0 (which was already configured when I first fired up Proxmox), and used the same settings as vmbr0 uses in the screenshot I posted above, and that...

They're quite sure that the gateway I should be using with 192.99.198.148/30 is 192.99.10.254. This is a rented server in a data center I don't have physical access to, so that's not an option. However, I'm using vmbr0 which is bridged to eth0, and on the hypervisor I can use that interface to...

I've been told explicitly that I should be using .10.254 as my gateway, not .198.254: It's a little strange that the gateway would be outside the address' subnet, but that's what they told me. Anyway, I tried setting up a new, clean VM running Ubuntu 14.04 Desktop and I seem to be having the...

I'm trying to put together a setup where I have a pfSense firewall as a VM on a Proxmox node, and all other VMs on that same node communicate with the outside world through that firewall VM. The firewall should be binding to all the IP addresses available to the hypervisor (that part is mostly...