Search results

I run my pfSense installation for my network as a virtual machine as well. I currently have 4 nodes in the cluster, which are all identical except for the node with pfSense. All nodes have four gigabit NICs that are LACP bonded to form what I have called the "Virtual Machine Trunk". They also...

Ich spreche nur Englisch, daher wurde dieser Beitrag mit Google Translate erstellt. Ich habe auch die englische Version unten aufgenommen. Ich führe meine pfSense-Installation für mein Netzwerk auch als virtuelle Maschine aus. Ich habe derzeit 4 Knoten im Cluster, die bis auf den Knoten mit...

1. I don't believe that you can. Each cluster would have a separate GUI. 2. I am sure you could put them on the same network, but I think it would be better to separate them out into their own network or VLAN. 3. I don't believe you can migrate VMs or containers between clusters. I looked as...

As far as I am aware if you create another bridge but do not assign it an interface / IP address and then connect the VMs to that bridge and setup that bridge on the pfsense VM as well. For my setup, I have pfsense running in a VM and have trunked 4-gigabit network ports together to a switch...

I wanted to post an update on this. I got a three mode cluster up and working and it is running very well. As for the desktop system I did manage to get it to pass through 2 GPUs to 2 different VMs once I added another GPU for PVE to use. However I did run out of PCIe lanes on the CPU and so I...

I am back at it trying to set up a new PVE cluster using the following hardware: 1 x Dell 2950 Gen 3 (2 onboard NICs, 2 Quad PCIe NICs, and 1 Dual PCIe NIC) 2 x Mid Tower PCs with Intel i3 and 16GB ram (1 onboard NIC, 4 Single PCIe NICs) 1 x Full Tower PC with Intel i7 and 24 GB ram (1 onboard...

I believe that this is possible as I set up something similar for another scenario. I had a need to redirect all the mail from a domain to another email address as I was taking the backend server offline. Under the WHO OBJECTS, I created an entry that listed the domain I wanted to redirect...

I am not sure what changed between my testing setup on Virtualbox and my production install on ProxmoxVE but everything is working now.

A follow up to this is that I can send email to a domain that is not managed by PMG such as a shaw email address. Is there something I have to do to have it work with domains that are passing through PMG?

I have setup PMG and currently, have a domain configured (techbehave.com) with GoDaddy with the following records. A -> @ -> Public IP Address A -> * -> Public IP Address MX -> mail.techbehave.com -> 10 MX -> mail.techbehave.com -> 20 I then have my PFSense firewall configured to port forward...

does removing the bridge fix the issue?

After creating the new bridge did you restart the node?

I don't have a tutorial per se, but I installed for my implementation an Ubuntu 16.04 Server then added Ngnix to it and also the let's encrypt software.

How are you getting these IPs on your network are you connecting the proxmox node to the modem directly or are you using a router or firewall in between?

The way that I have handled many web servers and using let's encrypt is to use a reverse proxy and have the certificate reside there and then use http and some self signed https between the proxy and the back end servers.

When I was designing the implementation I already had the NAS units in place, though they were serving a different purpose at the time. I did look a ceph but decided against it as it would require me to purchase more hardware. I originally started with 2 nodes each with a small SSD (250GB) for...

Have you tried starting it with hardware virtualization on now that it is enabled in the bios?

Your CPU(s) need to support hardware virtualization in order for KVM to work properly. You can check if your CPU(s) support this using: To check if your CPU is virtualization compatible, check for the vmx or svm tag in this command output: egrep '(vmx|svm)' /proc/cpuinfo You can also go to...

Your VNC is failing as the VM is not running, did you enable hardware virtualization in your BIOS? Looking at your log it seems the VM fails to start due to KVM virtualization error.

Here is my take on your situation, not sure these are "Best Practices" but from what I have learned through my years, this is what I would probably do given this information: Single Node: -Dual PSUs in the node -2 SSDs in RAID 1 for Proxmox (Host OS) -As many HDDs or SSDs that can fit in that...