![]() For that you should stop all your VMs but at the same time you need a internet connecting while upgrading. Lets for example say you want to upgrade your PVE from one mayor version to another one. But such a setup without redundancy can cause problems. And all should use the sophos LAN as a gateway and DNS server. In such a setup you describe, in general you want all your hosts to be in your 172.16.16.0/24 subnet including your proxmox host itself. That basically means your PVE management (SSH,WebUI and so on) is outside of your firewall and everyone on the internet can connect to it to try to hack your server. I woudn't give your PVE host a IP on the vmbr1 if that bridge is used for WAN. I guess the main goal is to leave everything getting IPs in the range 172.16.16.x or should this be a network configuration within Sophos XG itself? The not so obvious part (for me) is how should I configure my network in order to being able to connect back to proxmox from this new network?Īll my VMs seems to grab an IP range from 172.16.16.x when sophos XG VM is up and running, but they get an IP from range 192.168.10.x when not. The problem is that from this windows machine, I can not longer connect back to 192.168.10.5, which seems obvious. ![]() I can successfully connect to 172.16.16.16 when connecting the LAN port to a windows machine, the machine is getting an IP assigned (172.16.16.17) and I can connect to the internet. Right now, my pve network configuration looks like this, listening at 192.168.10.5 I have a supermicro X8sil-f motherboard with dual NIC which I want to use in order to setup Sophos XG as my main router.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |