Search results

You seem confused as to how zfs operates. Once you write to a block it becomes zfs's job to remember that data. It doesn't care if it is a zero or a one as long as that doesn't change outside of a write operation. By writing to the entire disk you have filled the thin provisioned device from...

Thank you sir. I appreciate you going to the extra effort. I am at a loss to explain what I am seeing. It is a 500 error generated on gitlab (custom 500 error page with logo).

Still not working. Tried on multiple browsers. I also tried searching for your username and can see two snippets. I can access the pve-virt-viewer item but get a 500 error when accessing proxmox-kickseed.yml.

@morph027 the linkage is broken for me. It is throwing a 500 error

I have actually got proxmox-deploy working. I struggled for awhile trying to figure out why networking didn't come up after provisioning was complete. I eventually mounted the vm's system disk manually and added a user password so I could get into the console. This was an Ubuntu 16 image and...

Why not stand up a pfsense kvm on each host and then use pfsense's internal HA mode to handle fail over ?

@Ovidiu , Of the adjectives that I would use to describe Rackspace, inexpensive isn't among them. It is easy to set this up but it does hamstring you a little unless you are provided out of band management such as Drac. I noticed an error in my statement above but the importantt part is...

It is pretty simple, first of all you don't need any bond interfaces and the internal network bridge (vmbr0 above) looks like this auto vmbr0 iface vmbr0 inet manual bridge_ports none bridge_stp off bridge_fd 0 keep in mind that with this setup you lose access to the...

Personally I am beginning to get frustrated, I have tried vagrant and had troubles. The create from ISO works but getting an ISO prepped to work with vagrant is proving a bit of a challenge. Create by cloning doesn't work because the current api refuses a linked clone (issue reported but...

Rereading your question at the beginning of this thread it occurs to me that I am envisioning an internal physical network being supported by the virtual machines on the network and protected by the firewall vm. You never mentioned that actually so I need to ask, is this the situation or did...

Needless to say, my internet demarc (fiber) plugs into port 2 on my switch. Proxmox hosts plug into ports 1,4,5, and 7 on the switch. The connection to the internet therefore rides on vlan 9. Internal traffic rides on vlan 1 and is untagged. Complicated maybe for a home environment but not too...

I think I am headed for an answer that you won't like. You either need multiple nics or multiple vlans. There must be some way to separate the internal and external traffic. This matches my layout as described earlier and detailed in my interfaces file.

This is a long shot but here goes, if you recently built this machine, have you double checked tightness on all connectors and verified all screws that might be serving as ground planes are tight?

From here we go down the rabbit hole looking for trouble. It is possible that your motherboard is an issue but I sort of doubt it. Power supply? What do your 3.3v and 5v rails look like? Any chance of swapping either powersupply or motherboard for testing purposes?

In your earlier post you indicated that you switched from the onboard nic to one that you purchased separately while troubleshooting. It is unlikely that either device is the culprit (two failures don't usually happen at the same time) . So what pieces remain that are common to both...

This is what I mean In this drawing BR0 is the external (internet) bridge. It is associated with eth0 and connected into your demarc. BR1 represents the internal network and it is associated with eth1. The only machine (virtual) connected to BR0 is the firewall/UTM device (such as...

Maybe it is just me but importing appliances seems to be something I would do very occasionally. What you are describing would be something that I would convert to a template after import to facilitate turning up fresh instances on demand.

I am glad to hear that. You probably want to chase down the ACL issue before taking this into production but all functions will work via the tunnel method.

@100percentjake It is meant to be run from your workstation. Let me know if you are running from a Windows box. I can provide instructions on how to do the equivalent with putty. It is still possible there is a an asymmetric route issue going on but tunneling in will get you going.

Have you tried doing something like this ssh -L 8006:10.110.30.221:8006 root@10.10.30.221 which will portforward port 8006 on the proxmox host to your local machine. Then you can access the web interface via https://localhost:8006 in your browser. If that fails try running : ss -lt |grep...