Search results

Is something blocking http port 80 in your network?

Is your original vmbr0 and mac address linked/set by people of Hetzner ? You are now adding a "foreign" mac address (and ip) to the original vmbr0 config. Maybe this is a Hetzner policy for security reasons. Not sure, just my thoughts.

Do ANY of your public ip addresses reply to ping from your pc?

- read this and probably you will have to read Routed Configuration (Hetzner?) https://pve.proxmox.com/wiki/Network_Configuration#_default_configuration_using_a_bridge - maybe contact the datacenter helpdesk and ask your ip address questions?

Plug a cable in eth4 that is for management and configure VLANs on the vmbr2 interface. Or delete vmbr0 and add port eth5 to vmbr2 and configure VLANs on vmbr2. You can create a management VLAN and a "LAN" VLAN etc.

Native VLAN1 is untagged, that is correct. So unless you change the native VLAN1 to something else (VLAN99) that port cannot be set to tagged.

Maybe try setting your Sophos ip as DNS in /etc/resolv.conf

For systemd-boot : add this to your line in /etc/kernel/cmdline: ipv6.disable=1 then run: proxmox-boot-tool refresh restart PVE host But beware that a lot of messages in your PVE host log will appear about ipv6 and iptables. I disabled pve-firewall because I just run a simpel home lab.

see my comment in this post, ipv6 is completely disabled also in lx containers. I would like to do the same with another PVE host, but this one boots from systemd-boot instead of GRUB. I read some comments about strange firewall errors when disabling ipv6. Also someone mentioned that Proxmox...

So this will disable ipv6 on the PVE host itself. But how do I disable ipv6 in vm's and in lx containers? Because the vm's and lx containers still show ipv6 addresses....

Do you mean the Backup Server itself will break, or does it break and we cannot make vm backups to the PBS ? And what exactly does "break" mean, can you explain please..

If you are booting/using GRUB, try this (and run "update-grub" after editing) : - edit "/etc/default/grub" - this is without iommu enabled: GRUB_DEFAULT=0 GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR="Proxmox Virtual Environment" GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1 quiet"...

This only works in Debian lxc. Also give a "sysctl -p" command after adding the 'disable' lines in sysctl.conf. If you are using Ubuntu lxc these "disable" lines do not work. Still looking for a solution myself for my Ubuntu containers.

You cannot set a trunk port as untagged, only as tagged. That is, if you mean trunk = carrying multiple vlans over one port.

Why use two vmbr's ? vmbr0 and vmbr1 interfaces can be usefull when you virtualize pfSense/OPNsense, creating a LAN and a WAN. If you want to just use vm's, one vmbr will do. I assume Switch 1&2 are managed ? You can configure VLANs in those switches. For separating VLANs you must use port...

"VLAN to VLAN works." - if you mean VLAN10 to VLAN20 can "see" each other, is not the concept of vlans. They should be completely isolated/firewalled.

Not in your modem but in the ubuntu vm. Although I think ubuntu has no default firewall active out of the box like Debian.

add a (permanent) route from 192.168.1.0/24 to 192.168.5.0/24 on your laptop.

What are you trying to ssh and ping in vlan20? Is it a Linux vm? If so make sure PermitRootLogin = yes (/etc/ssh/sshd_config). And disable any firewall rule that blocks ping/ssh access.

You can experiment with the simulator: https://pbs.proxmox.com/docs/prune-simulator/