Search results

Huh?

When configuring a firewall you typically don't use SOURCE port because applications on the client side will pick a random port. Selecting a DESTINATION port indicates what the client is talking to, which is where you configure your firewall rule.

Client machines use random ports to connect to a destination port. Remove the source port numbers.

That is not an rdp connection. Since the entry point is proxmox and not a direct connection to the console, it is more secure than opening up an rdp service to the web.

Opening up remote desktop for a windows box on a public IP address is asking to get hacked.

Why wouldn't it be? Why would the fact that it's a VM change anything? If you have a public service hosted on a public IP, it is at risk. Period.

Anything with a public address is subject to attack. It doesn't matter what hypervisor the VM is running on or if it is running on physical hardware. I would trust a website running under Linux moreso than windows.

I don't understand what your problem is. I don't know what it is you have configured

The only vmbr that needs an IP address is the one you run management network on

I'm trying to figure out WHAT you were asking....

What have I just read?

You can't pass your single public IP address to a VM and still have access to the host. You need to NAT in order for your VM to have internet access.

Is your VMBR0 on a public IP address or is it NATted behind a router? If it is public, you need NAT, or a router of some sort. If it is private ip address behind a router, why the F are you hiding your IP in your screenshot? In either case, it looks like it is the only device with an IP and...

create BRIDGES on the other nics. They do not need addresses on them, just create some VMBR devices with each one connected to an ETH device. Then use those bridges in your Sophos VM. You don't attach VMs directly to ETH devices, you attach them to VMBRs

I don't understand how openvswitch would negate the need for tags to be passed through the switch in the correct manner.

Is there a reason you put an IP on that vmbr? It's not needed for an internal only vswitch

NTFS isn't a file share protocol. It's a filesystem on a hard drive. The network share would be NFS or cifs/smb/samba

You would simply set up storage on another machine. Like NFS

By default, there is nothing that will restart the server without your intervention. I would start with power supply. Test it. Make sure its good

When it comes to zfs, you should never let hardware raid get between zfs and the disks. Letting zfs control "half" of your raid config makes no sense. Zfs needs direct access to hardware (disks) in order to be beneficial and operate in a proper manner