Search results

Hallo, ist es vielleicht möglich, dass die Firewall-Einstellungen im PVE die Pings etc. blockieren? [0] Man könnte ausprobieren in Tab "Optionen" der VM die Firewall für die VM auszuschalten [0] https://pve.proxmox.com/wiki/Firewall

Hi, no, it is not directly possible to send a command from the VM to the PVE via the qemu-ga. But you could use SSH on the VM to trigger a custom script on the PVE which shuts the VM down and boots it again. :)

Hi, This sounds very much like a networking issue. Could have many reasons, though... Do you have to "ping" for each container, or each IP address, or for the whole block once? Could also be some sort of (IPsec) tunnel, which needs to be established before a bidirectional communication is...

Hi, a thing that you could try is to create a section for the new NIC in /etc/network/interfaces yourself. After that, the PVE will probably show it in the web interface.

Hi, it is possible to change the ip addresses on your nodes without having to recreate the whole cluster: this older post [0] already answers your question :) (be cautious with the corosync config file [1]) [0] https://forum.proxmox.com/threads/change-cluster-nodes-ip-addresses.33406/ [1]...

If the cluster-wide firewall setting is "disabled", no other firewall options will have any effects -> No (PVE) firewall will be active

What do you mean by "the interfaces got renamed"? To check, if its really a networking issue, you could start trouble shooting by setting up a nginx/apache server and try to go to port 80 – if this works, its a MC server issue – if not, then probably a network/firewall issue. Besides the...

Hi, PVE implements its own firewall at cluster, node and VM level. [0] Try to add an ACCEPT rule in the "firewall" tab of the VM for your dest. port 25565. A way less secure option would be to turn the PVE firewall entirely off. I hope, this can solve your issue and you can start playing...

Hi, as far as I know, IPv6 is always preferred if it is possible. The only difference between the resolve.conf's is the IPv6 address. Try it with only IPv4 DNS servers on the PVE host, perhaps this helps.

Hi, First, it is not possible to "passthrough" only a single partition (at least it would not be easy and it would not be what you want). If this is a USB-HDD I would recommend passing through the whole USB device. Otherwise, you would have to follow your tutorial. In both of these cases you...

I don't quite understand your current problem... Is your only issue, that you need to reboot the hypervisor? If yes, try instead to set the bridge down and then up again. The post-up statement is only executed after the interface goes up—if it is already up, noting happens.

Cloud it be, that your rules are not quite right? Try letting the source port unconfigured. Otherwise a client connection to port 8080 would have to use port 8080 as its source port. :)

I would not say, that this is wrong, but a misunderstanding: The PVE uses KiB/MiB/GiB/TiB for 1024 based values and KB/MB/GB/TB for 1000 based values. see [0] So, 1.01 TB = 1.01 TB df -h uses 1024 based values (df -H uses 1000 based values) So, 938G = 938 GiB = 1.01 TB I hope, I could help...

As the firewall [0] logs directly to the system journal (unit pvefw-logger) it is possible to use any syslog daemon (e.g. syslogd) to send this to a specified syslog server. This should result in a near real-time logging of firewall events. [0]...

Is it possible, that the switch uses VLAN 2 as its default VLAN on this link? If this was the case, the switch would send any frames destined for VLAN 2 without any VLAN tag, which in turn "confuses" the node, because there is not default VLAN configured there. If this really is the problem...

Hi, If you don't allow incoming ICMP traffic, pings will be blocked. As you did not mention that you allowed ICMP traffic, I assume this is the problem. If, however, you are unable to connect via a allowed port, I'll have a closer look :)

The Ubuntu live CD was a good try :) From what I know, this CDs should include ZFS. However, another possibility would be to use the PVE Installer ISO, enter the debug mode and chroot into your "broken" installation.

This is perhaps because of the PVE Firewall [0]. Try deactivating at the VM level (of the pfSense firewall VM) Other question: Why don't you use multiple interfaces for the pfSense VM? So the firewall VM would not have to bother with VLANs. [0] https://pve.proxmox.com/wiki/Firewall

Yes, in your case you can safely ignore these "errors" :)

The most likely explanation is, that you either open a console or click on the "Console" tab of a VM by accident while doing other stuff.