Search results

I'd suggest you remove the gateway from vmbr0.900

only vmbr0 needs a specific IP address, you can still create a bridge for your extra network interfaces if you like, just don't assign any ip addresses to them. You could still create a VM, attach it to vmbr2 and give the VM an IP of 192.168.31.42, that would work. Alternatively, you could bond...

just try giving vmbr0 a different IP address, does that work?

while you can get into advance configs with multiple routes and gateways, by default you can only have one gateway defined at the host level. That is not to say that your VM's have to use this gateway but again that's the usual state of affairs. So, say your VM's are using 172.16.50.0/24 (on...

It appears to me that enp9s0 already has the IP address 172.9.79.242 assigned? as you are accessing the GUI interface on that IP?

Isolated networks don't need a gateway, that limits them to only communicating with other devices in the same subnet. However, without VLANs, the other devices will 'see' the network packets, they just won't process them. With VLAN's the network is also divided logically and network packets on...

install something like tailscale on both your local client and on the windows VM, this should give you a VPN connection that you can use for remote desktop

I'd suggest you start a new topic of your own, give details of your setup and your environment and what you would like to accomplish

yes, it's possible and there are a variety of ways to accomplish this. Depends if you need read/write access and any form of user restrictions

Microsoft does not support Active Directory over NAT and work-arounds are not easy to accomplish. I would suggest you explore creating a new Domain on the private network and then explore creating a domain-trust relationship with the corporate domain.

that's because dhcp relies on broadcast frames and these are not routable or can go through NAT

you will only be able to run multi-scoped dhcp on physical devices if you have switches that support VLANs

Well, to really have a cluster with migration support, you really need two hosts with a seperate storage system. A distributed file system like ceph or gluster might work but you seem to need pretty decent hardware to get anything like decent performance with these. You could run the H700 in...

you would need to put in a rule to block incoming traffic on the wan interface

Just remember that pfsense will need to 'allow' the use of a 192.168.x.x network on the WAN interface (see Interfaces/WAN/reserved networks)

did you run your speed tests on a raid10 setup? afaik that would be the highest performing config at the expense of capacity

four ways you can control access 1. permissions on the directories and files 2. restrictions based on guest IP 3. host restrictions 4. encryption

what is your hardware setup? particularly storage devices... how do you see yourself using the system? home lab, media server, development, etc

In your original setup, you have defined two networks - the '.64' and the '.68' Did you think you needed a second network? why? Otherwise just put everything on the '.64' network and everything will work. If you still want a second network for your VM's and you want to reach them from your...

as vmbr1 is on a different subnet from your main lan, they will not be able to reach the internet as they won't be able to reach the main lan gateway. The solution is to a) use ip tables rules on the host to relay traffic between the VM network and the main LAN/internet - for example auto...