Search results

Also a tip: try to avoid using 192.168.x.1 and/or 192.168.x.254 for a server. Many routers and switches use .1 or .254 as default network address = ip conflict.

If you can put your ISP router in Bridged mode, you can then create a VLAN100 UNTAGGED (internet) and connect it to the HP switch. From the HP switch you can plug in your Proxmox host and I would definitely use both network cards. This way you can install and run pf/OPNsense on the PVE host. Or...

I think I know what he means and what his goal is, but his diagram is missing details (at least the naming is wrong). Green WAN line = (UNTAGGED) WAN VLAN100 Black LAN line = TAGGED WAN + LAN, VLAN100 + VLAN1 Grey INTERNET line = UNTAGGED LAN, VLAN1 VLAN numbers are examples, use your own.

Your drawing : only PC 1,2,3 have internet access, without ANY proper firewall protection. pfSense and win10 will have NO internet access. Furthermore, with 3 different mac addresses using 1 internet connection, your ISP will probably shut your connection down.

If ens18 (virtualbox nic name) = enp0s8 (proxmox nic name), then change bridge-ports enp0s3 to enp0s8 And from Proxmox host, what is the output of # cat /etc/resolv.conf

pfSense is BSD based, not Linux. I see a lot of people set the OS type to Linux. I set it to “other”. This is not the solution to your boot problem, but I just wanted it to mention

... are you sure this is the right forum/thread for your question? This is Proxmox Backup Server not PVE host...

- why not use Synology HyperBackup tool on the NAS to backup the files? - I have PBS running on my NAS as a vm, in Synology Virtual Machine Manager (you need some extra RAM memory for this)

My question is: why do you need bonding? Are you planning to generate very heavy network traffic?

I use Proxmox Backup Server, and it is dead simple to restore vm/ct backups to PVE A and/or PVE B.

It depends on what your possibilities are, moneywise and hardware etc. You could save the vm/ct backups both on your PVE host AND on a NAS (or an external USB disk). That's not totally foolproof but it is a start. Personally I'm not a big fan of clustering. Especially in a simple home lab, with...

Can you explain exactly what you fixed in your switch? From your screenshot it looks correct.

And why do you delete the ip addresses in your posts and replace them with x.x.x.x ? If it is your local internal network......nobody is going to hack you.

Has VLAN33 got a DNS server configured and a way out to the internet (gateway) (in your main router perhaps)? I think not, that's why Proxmox cannot resolve debian.org through VLAN33. Why don't you set the gateway on vmbr0, to make things a bit easier for you to configure?

From Proxmox host what is the output of: # ip route # dig debian.org

Hm, I hope I understand your config..... First time your PVE host got an ip address from your dhcp server in a 192.168.100.0 subnet, second time you say it is in 19.168.0.0 subnet... How is this possible? What is your actual LAN subnet?

If WAN port on slave router is not a member of the regular LAN then you have double NAT active. It is not wrong, but double NAT gives more headache when you want to open ports etc.

vmbr0 has no Gateway. Put the Gateway on vmbr0 and not on a vlan.

Unless you have 3 different public ip addresses (I think you have just one), I would choose to do it this way : (TP-Link switch) Port1 = VLAN100 = UNTAGGED = PVID100 (WAN) Port2 = VLAN100 = UNTAGGED = PVID100 (WAN) Port3 = VLAN100 = UNTAGGED = PVID100 (WAN) Port4 = VLAN100 = UNTAGGED = PVID100...

It's not that weird at all. Consider the whole Topton box as an OPNsense router (nic1 + nic2) with a separate Proxmox host (nic0) in it.